If this is PHP and you are using sessions, I would guess that your sessions are blocking. With sessions enabled, each PHP client has a write lock on the sessions file and concurrent requests are blocked to wait for the session to be available for an exclusive lock. As soon as you are done making changes to a session, close it for writing and other requests will be handled. See this page for detby zmre - Nginx Mailing List - English
Folks, please accept my apologies. The request I was making was redirecting to a location that didn't include the fcgi_buffer* parameters. When I moved those over, my problem stopped. Sorry to have bothered you. > upstream sent too big header while reading response headerby zmre - Nginx Mailing List - English
Hello, nginx is currently giving me this error: upstream sent too big header while reading response header and returning a 502 Bad Gateway message to the browser. With debugging turned on, I can see that my PHP application (SilverStripe) is adding two large headers (X-Include-JS and X-Include-CSS) to the HTTP response of around 3,000 characters each and the first one of these isby zmre - Nginx Mailing List - English