You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Martin Kraemer <Ma...@Fujitsu-Siemens.com> on 2001/11/08 12:57:28 UTC
Re: daedalus is running 2.0.28-dev [Connection: headers?]
The "hangs" I observed are a squid/ICS problem. That's what I found out
by bypassing squid and using a different proxy. However, I don't know
what actually causes squid to hang in this request only. Tcpdump
shows that it gets the response all right. Dunno. It's definitely
the combo of
client <--> squid <--> ICS proxy <--> www.apache.org
which causes squid to hang. Apache seems to be abolutely correct wrt RFC2616.
Martin
--
<Ma...@Fujitsu-Siemens.com> | Fujitsu Siemens
Fon: +49-89-636-46021, FAX: +49-89-636-47655 | 81730 Munich, Germany
Re: daedalus is running 2.0.28-dev [Connection: headers?]
Posted by "Roy T. Fielding" <fi...@ebuilt.com>.
On Thu, Nov 08, 2001 at 12:57:28PM +0100, Martin Kraemer wrote:
> The "hangs" I observed are a squid/ICS problem. That's what I found out
> by bypassing squid and using a different proxy. However, I don't know
> what actually causes squid to hang in this request only. Tcpdump
> shows that it gets the response all right. Dunno. It's definitely
> the combo of
> client <--> squid <--> ICS proxy <--> www.apache.org
> which causes squid to hang. Apache seems to be abolutely correct wrt RFC2616.
Is the client sending the non-standard proxy-keepalive option on the request?
That can cause proxy chains to hang if one of them makes the mistake of
honoring it.
....Roy