httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 47095] Problems with pipelined HEAD requests...
Date Tue, 05 May 2009 17:11:47 GMT

Eric Covener <> changed:

           What    |Removed                     |Added
             Status|REOPENED                    |RESOLVED
         Resolution|                            |INVALID

--- Comment #19 from Eric Covener <>  2009-05-05 10:11:42 PST ---
(In reply to comment #18)
> Sorry I didn't get back until sooner.  This is the exact same behavior that
> Opera exhibits, and if you examine the TCP activity, you'll see that Apache
> never responds to the last TCP ack, which is why Safari (and Opera) never
> continue with the requests until after teardown.

If you're talking about the ACK in frame 344, what kind of response is expected
from Apache? 

he ACK in frame 344 is the ACK from the client of the last byte of the response
to the only outstanding HEAD request.

After Apache sends the full response, and the client has ackowledged it, no
subsequent request is issued until A) after KeepAliveTimeout elapses and B)
Apache has sent a FIN to terminate the connection.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message