Bug #415
mod_proxy stalls on status "304 Not Modified"
| Status: | New | Start: | ||
| Priority: | Normal | Due date: | ||
| Assigned to: | jan | % Done: | 0% |
|
| Category: | mod_proxy | |||
| Target version: | - | |||
| Pending: | No |
Resolution: | ||
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
History
12/14/2005 01:15 PM - Anonymous
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
12/14/2005 01:27 PM - Anonymous
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