RE: [squid-users] Upstream Proxy problem

On Mon, 2004-12-20 at 10:52 +0000, Martyn Bright wrote:

> > >> 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.

I hope this hasn't already been ansered... but this is blantantly false.
Its perfectly legal for an HTTP/1.0 proxy to add a Via header, and the
via header _record_ the clients http version.

Rob