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. -- JamieReceived on Friday, 30 April 2004 17:39:57 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:38:23 GMT