That definitely explains the behavior I was seeing. But to me, any way to bypass the rate limiter seems like a security hole. Is there any way to change the phase/order of these two directives, or to otherwise cause rewritten requests to be rate limited?by zildjohn01 - Nginx Mailing List - English
I'm attempting to rate limit requests, and I'm unable to make the limit_req directive have any effect. I've trimmed it down to a minimal test case. Here's my complete nginx.conf (with only the server_name changed to protect the innocent): ---------------------------------------------------------------------- worker_processes 2; events { worker_connections 8192; } http { #keepaliveby zildjohn01 - Nginx Mailing List - English
Thanks, that helped point me to the issue. It turns out the problem was that I didn't pass --pep3333-input to uWSGI, so it was converting all CRLFs to LFs in the request body, so CONTENT_LENGTH didn't match the data length. Passing that flag to uWSGI made it pass the raw stream to my app and solved the problem.by zildjohn01 - Nginx Mailing List - English
I've come across an incredibly weird problem with POST responses using nginx 1.0.1 and uWSGI 0.9.7.2 on CentOS 5.6. uWSGI successfully sends the response body to nginx, but nginx seems to ignore it if both (1) the request method is POST, and (2) the response length is less than 4052 bytes. The issue doesn't occur when serving directly using `uwsgi --http`, so I'm pretty sure the problem is someby zildjohn01 - Nginx Mailing List - English