Re: Squid Problem with HTTP/1.1?

Squid changes the version of the message because it is a 1.0 device; it
doesn't fully support 1.1. Remember that the message version is hop-by-hop,
not end-to-end, so it has to do this.

That having been said, there are some weird interactions with some older Web
servers (which may include apache 1.2.4) and POST - they might (wrongly)
expect an extra CRLF at the end of the POST under certain conditions.

Look in the squid and apache FAQs for this issue, IIRC there's a config
option in recent Squids to fix this.

Cheers,

On Thu, May 18, 2000 at 09:22:39AM +0200, Martin Schönhöfer wrote:
>
> Hi
>
> I'm rather confused about Squid.....
> I'm working with Squid 2.2 Stable3 and Linux SuSE 6.2 and was very happy
> about this proxy - everything was fine.
>
> Now I'm trying to make a (HTTP/1.1) PUT to an Apache 1.2.4 webserver and it
> seems like the proxy changing the request to HTTP/1.0 and I can't transfer
> anything to the remote server. I get no error code, the request is also in
> the Apache logs.
>
> I try everthing to configure in the squid.conf - the cache stuff,
> http_access control - the Apache is getting the HTTP/1.0 PUT and can't
> handle with. I don't know what the Squid doing with my request.
>
> When I'm making HTTP PUT without any proxy between it works very well and
> the PUT is still in HTTP/1.1 in the webserver log.
>
> Is it a problem with Squid, with the Apache configuration - I don't know
>
>
> Regards
>
> Martin
>
> ++++++++++++++++++++++++++++++++++++++++++++
> Martin Schoenhoefer
> Support
> como Softwareentwicklung GmbH
> Fon: (040)/853318-50
> Fax: (040)/853318-99
> Mobil:(0171)/2027078
> Email: mschoenhoefer@comosoft.de
> Web: www.comosoft.de
> ++++++++++++++++++++++++++++++++++++++++++++

-- 
Mark Nottingham, Senior Developer
Akamai Technologies (San Mateo, CA)