- From: Jamie Lokier <jamie@shareable.org>
- Date: Fri, 30 Apr 2004 22:39:44 +0100
- To: Lisa Dusseault <lisa@osafoundation.org>
- Cc: Jeffrey Mogul <Jeff.Mogul@hp.com>, HTTP working group <ietf-http-wg@w3.org>, Justin Chapweske <justin@chapweske.com>
Lisa Dusseault wrote: > I know of server implementations that do not expect to see a message > body if the Content-Type header is missing and they interpret the > body, if sent, as the next request. That's a big fat bug. They should check the Transfer-Encoding and Content-Length headers: if either exist, there's a body. Transfer-Encoding has precedence. If neither exist, there's a body if Content-Type is multipart/byteranges. See "4.4 Message Length" in RFC2616. -- Jamie
Received on Friday, 30 April 2004 17:39:57 UTC