- From: Lisa Dusseault <lisa@osafoundation.org>
- Date: Fri, 30 Apr 2004 14:44:05 -0700
- To: Jamie Lokier <jamie@shareable.org>
- Cc: HTTP working group <ietf-http-wg@w3.org>, Justin Chapweske <justin@chapweske.com>, Jeffrey Mogul <Jeff.Mogul@hp.com>
Sure, it's a big fat bug. Just saying that I'm not the only one who assumed that every HTTP message with a body had a Content-Type. lisa On Apr 30, 2004, at 2:39 PM, Jamie Lokier wrote: > 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:44:29 UTC