- From: Ian Hickson <ian@hixie.ch>
- Date: Fri, 3 Apr 2009 07:55:44 +0000 (UTC)
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: Adrien de Croy <adrien@qbik.com>, Shane McCarron <shane@aptest.com>, Adam Barth <w3c@adambarth.com>, "Roy T. Fielding" <fielding@gbiv.com>, HTTP Working Group <ietf-http-wg@w3.org>
On Fri, 3 Apr 2009, Julian Reschke wrote: > Ian Hickson wrote: > > ... > > > It's the thing that actually gets the resource. It's free to do whatever > > > it likes with that content. > > > > No, HTTP says of the Content-Type header "its value indicates what > > additional content codings have been applied to the entity-body, and thus > > what decoding mechanisms must be applied in order to obtain the media-type > > referenced by the Content-Type header field". > > No it doesn't. It says this about Content-*Encoding* > (<http://greenbytes.de/tech/webdav/rfc2616.html#rfc.section.7.2.1.p.3>). My apologies, I meant to quote the following: "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." -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Friday, 3 April 2009 07:56:22 UTC