> >> 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) > Henrik Nordstrom wrote: > 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. > I've just noticed this in the header being sent from squid to the Upstream proxy:-
POST http://de4.autotrader.co.uk/DealerEditv4/services/DealerEdit HTTP/1.0 User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 1.1.4322.573) Content-Type: text/xml; charset=utf-8 SOAPAction: "" Content-Length: 1966 Expect: 100-continue Host: de4.autotrader.co.uk Via: 1.1 jfc:3128 (squid/2.5.STABLE6) X-Forwarded-For: 192.168.0.10 Cache-Control: max-age=259200 A trawl of the net suggests that an HTTP/1.0 proxy should not be adding the Via: statement, let alone adding 1.1 to it. The input to squid that generates this is:- POST http://de4.autotrader.co.uk/DealerEditv4/services/DealerEdit HTTP/1.1 User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 1.1.4322.573) Content-Type: text/xml; charset=utf-8 SOAPAction: "" Content-Length: 1966 Expect: 100-continue Proxy-Connection: Keep-Alive Host: de4.autotrader.co.uk Perhaps that is why the proxy is sending 1.1 messages back. Also, another oddity, as you can see above squid is announcing that it is squid/2.5.STABLE6 although actually the version installed is from a squid 2.5 STABLE5 rpm
