W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2009

Re: Content Sniffing impact on HTTPbis - #155

From: Henrik Nordstrom <henrik@henriknordstrom.net>
Date: Sat, 13 Jun 2009 02:06:16 +0200
To: Julian Reschke <julian.reschke@gmx.de>
Cc: Mark Nottingham <mnot@mnot.net>, Adam Barth <w3c@adambarth.com>, "William A. Rowe, Jr." <wrowe@rowe-clan.net>, Mark Baker <distobj@acm.org>, Bjoern Hoehrmann <derhoermi@gmx.net>, Roy Fielding <fielding@gbiv.com>, HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <1244851576.9699.45.camel@localhost.localdomain>
sön 2009-06-07 klockan 16:01 +0200 skrev Julian Reschke:

>     Content-Type specifies the media type of the underlying data.  Any
>     HTTP/1.1 message containing an entity-body SHOULD include a Content-
>     Type header field defining the media type of that body, unless that
>     information is unknown.  If the Content-Type header field is not
>     present, it indicates that the sender does not know the media type of
>     the data; recipients MAY either assume that it is "application/
>     octet-stream" ([RFC2046], Section 4.5.1) or examine the content to
>     determine its type.

Just a minor change to better reflect reality earlier HTTP specs:

instead of "examine the content to" simply say "heuristically" without
going into what means is used for determining the unknown type as it may
include other factors as well beyond the actual content transmitter
(i.e. URI details, context etc)

Received on Saturday, 13 June 2009 00:07:04 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:43:19 UTC