Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

http/1.1 question

0 views
Skip to first unread message

Panagiotis Malakoudis

unread,
Dec 31, 1999, 3:00:00 AM12/31/99
to
Hello everyone,

I was just browsing RFC 2616 and I have a couple of newbie questions.
First of all, at what level is http/1.1 implemented in squid?
With what protocol does squid talk client side and with what server side? i
see persistent connection in the cache manager. Are these connection from
1.0 or 1.1?
What would happen if squid receives a 100 Continue response? Can squid
reassemble transfer-coding chunks?
Interesting faq stuff wouldn't you say?
Sorry for the novice level of my inquiry but we all have to start from
somewhere :-)

Panagiotis S. Malakoudis

Systems Administrator
SPACE HELLAS S.A.


Henrik Nordstrom

unread,
Jan 1, 2000, 3:00:00 AM1/1/00
to
Panagiotis Malakoudis wrote:
>
> Hello everyone,
>
> I was just browsing RFC 2616 and I have a couple of newbie questions.
> First of all, at what level is http/1.1 implemented in squid?

HTTP/1.0 with partial support for features from HTTP/1.1. More and more
are being added and eventually Squid may become HTTP/1.1 but not yet.


Squid supports:
* Persistent connections
* Partial ETag validation support
* Partial byte ranges support
* RFC2068 Cache-Control (not yet up to date wrt RFC2616)
* and a couple of other minor things

Not yet supported:
* Storage of partial objects (for full byte range support)
* Storage of Vary objects
* Chunked transfer encoding (there exists a patch for this, but I don't
know the state of that)
* Extended request methods (although the methods for WebDAV will be
understood by Squid-2.3)

--
Henrik Nordstrom
Squid Hacker


0 new messages