Antwort: Re: Antwort: Re: Antwort: [Mod_gzip] mod_gzip without apache..?

[mod_gzip@lists.over.net]

Hi Eyck,


>> > Would you just gzip everything that goes through?
>> You would content-negotiate for the "Accept-Encoding" header.
>> In my situation all clients support gzip encoding.

In this case your clienst MUST NOT include Microsoft
Internet Explorer, or the users must be denied access
to the Internet Options.

> But still, this would be just compressing everything when
> Accept-Encoding says it supports deflate or gzip. Right?

If you use gzip to compress, then check for gzip.

>> Add "Content-Encoding", if Content-Encoding is the way you
>> want to do it.
> And where would I put original Content-Encoding?

Good question.

RFC2616 tells us that the "Content-Encoding:" header
contains a _list_ of encodings that have been applied
in the order they appear in this header, and consequent-
ly must be resolved by the client in reverse order.

So HTTP/1.1 supports having more than one Content-
Encoding ... in theory, that is.
Kevin Kiley told me that his experiments with browsers
showed him not a single one browser that supported more
than one content encoding at a time.

Regards, Michael