Request body of PUT with no Content-Type is processed incorrectly by CP3 (CP2 does it right) - cherrypy-devel

Message from discussion Request body of PUT with no Content-Type is processed incorrectly by CP3 (CP2 does it right)

Sylvain Hellegouarch

More options Feb 19, 2:54 pm

From: Sylvain Hellegouarch <s...@defuze.org>

Date: Tue, 19 Feb 2008 19:54:42 +0000

Local: Tues, Feb 19 2008 2:54 pm

Subject: Re: [cherrypy-devel] Re: Request body of PUT with no Content-Type is processed incorrectly by CP3 (CP2 does it right)

  Reply to author
  |
  Forward
  | Print
  | View thread
  | Show original
  | Report this message
  | Find messages by this author
  

> Sounds good to me. RFC 2616 says:

> Any HTTP/1.1 message containing an entity-body SHOULD include a
> Content-Type header field defining the media type of that body. If
> and only if the media type is not given by a Content-Type field, the
> recipient MAY attempt to guess the media type via inspection of its
> content and/or the name extension(s) of the URI used to identify the
> resource. If the media type remains unknown, the recipient SHOULD
> treat it as type "application/octet-stream".

> ...which I read as: let the app decide since we don't want to get into
> sniffing.

Indeed. However Chris, note that in the IETF language, a SHOULD is a
very strong requirement. They seldom use MUST but SHOULD means "we know
there are some cases where it won't be suitable but those should be rare
enough". I would invite you Chris to get the habit of sending the
content-type (you could actually hit some intermediairies that would get
you into trouble as well without that header).

- Sylvain

Reply to author Forward