Nginx

nginx fails to detect end of a seemingly valid fastcgi session

Bug #1447404 reported by Mike Bell
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Nginx
Incomplete
Undecided
Unassigned
nginx (Ubuntu)
Expired
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?

Revision history for this message
Mike Bell (mike-bell+ubuntu) wrote :
Revision history for this message
Thomas Ward (teward) wrote :

Which NGINX version are you seeing this under?

Revision history for this message
Mike Bell (mike-bell+ubuntu) wrote :

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

Thomas Ward (teward)
Changed in nginx:
status: New → Incomplete
Changed in nginx (Ubuntu):
status: New → Incomplete
Revision history for this message
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  
Everyone can see this information.
Subscribing...

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.