On Fri, 17 Dec 2004, Martyn Bright wrote:
>> HTTP/1.1 100 Continue message to Squid. This is forbidden by the HTTP
>> specifications as Squid is HTTP/1.0.
>
> Where is that then, the message that comes back says
>
>> A packet arriving from the upstream proxy contains this:-
>>
>> HTTP/1.0 100 Continue
>> Date: Thu, 16 Dec 2004 18:58:28 GMT
>> Via: 1.1 cache0 (NetCache NetApp/5.3.1R2)
And HTTP forbids this message to be sent to Squid (MUST NOT) as Squid is a
HTTP/1.0 client (RFC 2616 8.2.3 Use of the 100 (Continue) Status, last
point)
The upstream proxy is certainly malfunctioning here. It is possible the
malfunction maybe (but just maybe, in fact quite unlikely) is in turn
caused by a malfunction at the web server.
>> To which the squid server adds:-
>>
>> X-Cache: MISS from jfc
>> Proxy-Connection: close
Which is correct according to the HTTP/1.0 specificatios, but which
unfortunately terminates this request immediately.
Regards
Henrik
Received on Fri Dec 17 2004 - 05:22:15 MST
This archive was generated by hypermail pre-2.1.9 : Sat Jan 01 2005 - 12:00:02 MST