Antwort: RE: [Mod_gzip] Request Handling

[Robert Collins]

--=-rV4BQi9lxP4cgcn8VsEI
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Sat, 2003-10-11 at 10:42, TOKILEY@aol.com wrote:

> As if this all wasn't complicated enough... it's actually SUPPOSED
> to be legal to do something like this...
>=20
> Transfer-encoding: chunked, gzip

This isn't legal. RFC 2616 14.41 specifies the list is in order of
application to the message, and  3.6 says
" Whenever a transfer-coding is applied to a message-body, the set of
   transfer-codings MUST include "chunked", unless the message is
   terminated by closing the connection. When the "chunked" transfer-
   coding is used, it MUST be the last transfer-coding applied to the
   message-body. The "chunked" transfer-coding MUST NOT be applied more
   than once to a message-body. These rules allow the recipient to
   determine the transfer-length of the message (section 4.4)."

So you can NEVER have=20
transfer-encoding: chunked, gzip
but you can have
transfer-encoding: gzip, chunked

This doesn't change the comment about browser support - but does impact
the mod_gzip requirements.

Rob
--=20
GPG key available at: <http://members.aardvark.net.au/lifeless/keys.txt>.

--=-rV4BQi9lxP4cgcn8VsEI
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQA/h29DI5+kQ8LJcoIRAs5FAJ4p9xACOFplsTn9lOYwfuNKLYSFUwCfdLvi
0Cqg6md07az50GLurRNz5i8=
=iOAR
-----END PGP SIGNATURE-----

--=-rV4BQi9lxP4cgcn8VsEI--