> Furthermore, we can read in HTTP/1.1 specification > that "A server MUST NOT > send > transfer-codings to an HTTP/1.0 client".
I once did an socket implementation against Anonymizer. This is well established proxy service that services $100K+ government and private contracts. Their server always sent chunked content despite all headers. I'm pretty sure that there are other well established servers that send chunked content despite the rfc. Guessing that it might have something to do with wanting to control content compression. All the browsers can handle it, and that's probably all apple is concerned with - even though they're overriding an rfc spec req. Chris --- Jérôme Charron <[EMAIL PROTECTED]> wrote: > > http://www.apple.com for example answer with > chunked content also if > > you request with a http 1.0 header. > > > Stefan, > > I don't see any "Transfer-Encoding: chunked" header > in responses from > www.apple.com > Furthermore, we can read in HTTP/1.1 specification > that "A server MUST NOT > send > transfer-codings to an HTTP/1.0 client". > > Jérôme > > -- > http://motrech.free.fr/ > http://www.frutch.org/ >
