Re: Apache cannot handle multiple encoding types per document (fwd)

["Roy T. Fielding" <fi...@avron.ICS.UCI.EDU>]

> HTTP/1.0 does not support multiple content-encodings.

Yes.

> HTTP/1.1 suggests an implementation of multiple content-encodings which
> is broken; the ordering of the encodings is not defined. I'm sure I
> mentioned this on http-wg, but I can't remeber the outcome. Roy?

No (at least I can't find it in the archives -- its possible that you just
sent it to me and I lost it, since I lost personal mail a couple times
this year).

HTTP header fields *of the same name* are ordered upon receipt.
What the spec is supposed to say is that the order of header
fields with different names is not significant, but that got separated
into separate sections at some point which makes it seem like a
contradiction (yes, I'll fix it).  The reason for all this is that
it allows implementations to load the header fields into a hash table
before attempting a semantic interpretation (i.e., the message parser
is independent of the semantic interpreter).

......Roy