Bug #415
closedmod_proxy stalls on status "304 Not Modified"
Description
The content-delivery from proxy->client "stalls" for X seconds in case that the "If-Modified-Since" value provided by a client results in a "304 Not Modified"-response on the destination server AND that server does not include "Connection: close" and/or "Content-Length" in its 304-reply.
-- conny
Files
Updated by Anonymous over 18 years ago
Microsoft IIS6 on Win2k3 pre-SP1 sometimes (we have not settled exacly when) replies with the following:
HTTP/1.1 304 Not Modified Date: Wed, 14 Dec 2005 01:01:07 GMT Etag: "f9cc7f7ad4ffc51:19ee"
...and does not close the connection. This apparently causes lighttpd to wait until a server timeout before forwarding the reply to the client. Rendering of the webpage will appear to "hang" if the requested object happens to be an image in a complex webpage layout.
-- conny
Updated by Anonymous over 18 years ago
Microsoft IIS6 on Win2k3 with SP1, on the other hand, always seems to include the "Connection: close" header:
HTTP/1.1 304 Not Modified Date: Wed, 14 Dec 2005 11:02:39 GMT Etag: "f9cc7f7ad4ffc51:1a4d" Connection: close
In that case lighttpd delivers the reply without further ado.
-- conny
Updated by gstrauss about 8 years ago
Submitted pull request https://github.com/lighttpd/lighttpd1.4/pull/39 to unconditionally set Connection: close with proxied HTTP/1.0 request. The client request headers Connection and Proxy-Connection were already being filtered.
Updated by stbuehler about 8 years ago
- Description updated (diff)
- Status changed from New to Duplicate
- Assignee deleted (
jan)
Also available in: Atom