Re: [squid-users] 411 error with squid2.5.STABLE1

I cannot give a timeframe at this time on when Suqid will become
HTTP/1.1 compliant.

Chances are that Squid-3 will be at least conditionally HTTP/1.1
compliant, but no promise unless someone actively sponsors such
effort.

Squid since many versions back supports HTTP/1.0 persistent
connections via the Keep-Alive connection header, slightly different
from HTTP/1.1 persistent connections where it is the default.

Have removed the misleading HTTP/1.1 references from the persistent
connection references in the FAQ.

Regards
Henrik

On Tuesday 17 December 2002 22.45, Kesava Neeli wrote:
> Hi..
>
> Hmm.. I saw the FAQ entry 19.1 and thought that Squid 2 version is
> HTTP1.1 compliant.. Any idea when it would be HTTP1.1 compliant??
>
> 19.1 What are the new features?
>
> HTTP/1.1 persistent connections.
> Lower VM usage; in-transit objects are not held fully in memory.
> Totally independent swap directories.
> Customizable error texts.
> FTP supported internally; no more ftpget.
> Asynchronous disk operations (optional, requires pthreads library).
> Internal icons for FTP and gopher directories.
> snprintf() used everywhere instead of sprintf().
> SNMP.
> URN support
> Routing requests based on AS numbers.
> Cache Digests
> ...and many more!
>
> -----Original Message-----
> From: Henrik Nordstrom [mailto:hno@squid-cache.org]
> Sent: Tuesday, December 17, 2002 12:33 PM
> To: Kesava Neeli
> Cc: 'squid-users@squid-cache.org'
> Subject: Re: [squid-users] 411 error with squid2.5.STABLE1
>
>
> A POST MUST have a Content-Length.
>
> And where in the documentation did you find any claims that Squid
> is HTTP/1.1? Squid is HTTP/1.0.
>
> Regards
> Henrik
Received on Tue Dec 17 2002 - 17:58:49 MST