nginx fails to detect end of a seemingly valid fastcgi session

Bug #1447404 reported by Mike Bell on 2015-04-23
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Nginx
Undecided
Unassigned
nginx (Ubuntu)
Undecided
Unassigned

Bug Description

My cursory inspection of the .pcap seems to suggest that this is valid fastcgi, but nginx hangs for fastcgi_read_timeout seconds (despite the response having been sent within milliseconds) and then logs "upstream timed out (110: Connection timed out) while reading upstream", meanwhile the client gets an error. Is this actually an nginx bug or is there something subtle about the protocol that I've missed?

Mike Bell (mike-bell+ubuntu) wrote :
Thomas Ward (teward) wrote :

Which NGINX version are you seeing this under?

Mike Bell (mike-bell+ubuntu) wrote :

Apologies. Tested on 1.4.6 (Ubuntu) and 1.6.2 (Ubuntu)

Thomas Ward (teward) on 2015-12-21
Changed in nginx:
status: New → Incomplete
Changed in nginx (Ubuntu):
status: New → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for nginx (Ubuntu) because there has been no activity for 60 days.]

Changed in nginx (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments