Changes between Version 1 and Version 2 of Ticket #2110, comment 3


Ignore:
Timestamp:
12/17/20 07:50:01 (3 years ago)
Author:
shuliakovsky@…

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #2110, comment 3

    v1 v2  
    22> Could you please clarify what makes you think that the observed behaviour is a bug in nginx?
    33
    4   I'm completely understanding that it's sounds like "the bullets flew out from my side and problem on your side" but when problem is happened, I mean NGINX begins report 499, It begins report it on every requests, independent of requests number per second. Even when there is no request more than hour and I send only one via proxy it will report 499, until I execute "nginx -s reload"
     4  I'm completely understanding that it's sounds like "the bullets flew out from my side and problem on your side" but when problem is happened, I mean NGINX begins report 499, It begins report it on each request, independent of requests number per second. Even when there is no request more than hour and I send only one via proxy it will report 499, until I execute "nginx -s reload"
    55And right after executing command "nginx -s reload" everything begins work properly without 499 status code (it changes to 200)
    66Also numbers of requests right now lover than 1 per second, so according my configuration delays does not happening, if I clear understand how limit_req works.