I tried turning proxy_buffering off and that took that message away. However, I am seeing more of "upstream prematurely closed connection while sending to client" errors. Am I correct in thinking that the upstream cuts off the connection longer because it synchronously interacts with the client? Is there a way to simply ignore this warning in the logging to save io? The reason is that Iby josephlim - How to...
Hi Valentin, Thank you for clarifying that, however now that makes me wonder about this: if we set our timeout value to 30s and did not set our requests value, does this mean that the default requests value of 100 restriction is imposed or does nginx only respect the timeout value explicitly declared? Thank you again in advanceby josephlim - Nginx Mailing List - English
Hi all, I was curious to see if anyone used both keepalive_requests and keepalive_timeout at the same time and knew the expected behaviour? I was hoping that nginx would do whichever conditions were met first. Thank you very much in advance.by josephlim - Nginx Mailing List - English
Hi guys, I was wondering what happens when multiple workers access the ngx.shared.dict in the http lua module ? Are there conflicts/locking that could potentially impact performance of nginx? We are talking about 32 workers in my use case. Thank you in advanceby josephlim - Nginx Mailing List - English