* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Changeset 663


Ignore:
Timestamp:
2009-08-06 04:21:43 (5 years ago)
Author:
julian.reschke@gmx.de
Message:

take out note about content-sniffing as discussed in HTTPbis Working Group meeting (related to #155)

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p3-payload.html

    r662 r663  
    155155  border-style: none none inset none; 
    156156  border-width: 1px; 
     157} 
     158table.left { 
     159  margin-right: auto; 
     160} 
     161table.right { 
     162  margin-left: auto; 
     163} 
     164table.center { 
     165  margin-left: auto; 
     166  margin-right: auto; 
    157167} 
    158168caption { 
     
    385395      <link rel="Appendix" title="D Collected ABNF" href="#rfc.section.D"> 
    386396      <link rel="Appendix" title="E Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.E"> 
    387       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.445, 2009-08-01 14:05:14, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 
     397      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.447, 2009-08-04 19:54:03, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/"> 
    388398      <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"> 
    389399      <meta name="DC.Creator" content="Fielding, R."> 
     
    397407      <meta name="DC.Creator" content="Reschke, J. F."> 
    398408      <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-latest"> 
    399       <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-08"> 
     409      <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-08-06"> 
    400410      <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 
    401411      <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 3 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 3 defines HTTP message content, metadata, and content negotiation."> 
     
    428438         </tr> 
    429439         <tr> 
    430             <td class="header left">Expires: February 2, 2010</td> 
     440            <td class="header left">Expires: February 7, 2010</td> 
    431441            <td class="header right">HP</td> 
    432442         </tr> 
     
    481491         <tr> 
    482492            <td class="header left"></td> 
    483             <td class="header right">August 1, 2009</td> 
     493            <td class="header right">August 6, 2009</td> 
    484494         </tr> 
    485495      </table> 
     
    505515      <p>The list of Internet-Draft Shadow Directories can be accessed at &lt;<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>&gt;. 
    506516      </p> 
    507       <p>This Internet-Draft will expire in February 2, 2010.</p> 
     517      <p>This Internet-Draft will expire in February 7, 2010.</p> 
    508518      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 
    509519      <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p> 
     
    902912         compression, that are a property of the requested resource. There is no default encoding. 
    903913      </p> 
    904       <p id="rfc.section.3.2.1.p.5">Note that neither the interpretation of the data type of a message nor the behaviors caused by it are defined by HTTP; this 
    905          potentially includes examination of the content to override any indicated type ("sniffing")<span id="rfc.iref.c.3"></span>. 
    906       </p> 
    907914      <h3 id="rfc.section.3.2.2"><a href="#rfc.section.3.2.2">3.2.2</a>&nbsp;<a id="entity.length" href="#entity.length">Entity Length</a></h3> 
    908915      <p id="rfc.section.3.2.2.p.1">The entity-length of a message is the length of the message-body before any transfer-codings have been applied. <a href="p1-messaging.html#message.length" title="Message Length">Section 2.7.4</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> defines how the transfer-length of a message-body is determined. 
     
    10571064</pre><p id="rfc.section.5.1.p.18">would cause the following values to be associated:</p> 
    10581065      <div id="rfc.table.u.1"> 
    1059          <table class="tt full" cellpadding="3" cellspacing="0"> 
     1066         <table class="tt full left" cellpadding="3" cellspacing="0"> 
    10601067            <thead> 
    10611068               <tr> 
     
    12201227         </p>  
    12211228      </div> 
    1222       <div id="rfc.iref.c.4"></div> 
     1229      <div id="rfc.iref.c.3"></div> 
    12231230      <div id="rfc.iref.h.5"></div> 
    12241231      <h2 id="rfc.section.5.5"><a href="#rfc.section.5.5">5.5</a>&nbsp;<a id="header.content-encoding" href="#header.content-encoding">Content-Encoding</a></h2> 
     
    12431250      <p id="rfc.section.5.5.p.8">If multiple encodings have been applied to an entity, the content codings <em class="bcp14">MUST</em> be listed in the order in which they were applied. Additional information about the encoding parameters <em class="bcp14">MAY</em> be provided by other entity-header fields not defined by this specification. 
    12441251      </p> 
    1245       <div id="rfc.iref.c.5"></div> 
     1252      <div id="rfc.iref.c.4"></div> 
    12461253      <div id="rfc.iref.h.6"></div> 
    12471254      <h2 id="rfc.section.5.6"><a href="#rfc.section.5.6">5.6</a>&nbsp;<a id="header.content-language" href="#header.content-language">Content-Language</a></h2> 
     
    12691276      <p id="rfc.section.5.6.p.9">Content-Language <em class="bcp14">MAY</em> be applied to any media type -- it is not limited to textual documents. 
    12701277      </p> 
    1271       <div id="rfc.iref.c.6"></div> 
     1278      <div id="rfc.iref.c.5"></div> 
    12721279      <div id="rfc.iref.h.7"></div> 
    12731280      <h2 id="rfc.section.5.7"><a href="#rfc.section.5.7">5.7</a>&nbsp;<a id="header.content-location" href="#header.content-location">Content-Location</a></h2> 
     
    12911298      <p id="rfc.section.5.7.p.6">If the Content-Location is a relative URI, the relative URI is interpreted relative to the request-target.</p> 
    12921299      <p id="rfc.section.5.7.p.7">The meaning of the Content-Location header in requests is undefined; servers are free to ignore it in those cases.</p> 
    1293       <div id="rfc.iref.c.7"></div> 
     1300      <div id="rfc.iref.c.6"></div> 
    12941301      <div id="rfc.iref.h.8"></div> 
    12951302      <h2 id="rfc.section.5.8"><a href="#rfc.section.5.8">5.8</a>&nbsp;<a id="header.content-md5" href="#header.content-md5">Content-MD5</a></h2> 
     
    13291336         </p>  
    13301337      </div> 
    1331       <div id="rfc.iref.c.8"></div> 
     1338      <div id="rfc.iref.c.7"></div> 
    13321339      <div id="rfc.iref.h.9"></div> 
    13331340      <h2 id="rfc.section.5.9"><a href="#rfc.section.5.9">5.9</a>&nbsp;<a id="header.content-type" href="#header.content-type">Content-Type</a></h2> 
     
    13481355      <div id="rfc.table.1"> 
    13491356         <div id="iana.header.registration.table"></div> 
    1350          <table class="tt full" cellpadding="3" cellspacing="0"> 
     1357         <table class="tt full left" cellpadding="3" cellspacing="0"> 
    13511358            <thead> 
    13521359               <tr> 
     
    17171724      </p> 
    17181725      <div id="rfc.iref.h.11"></div> 
    1719       <div id="rfc.iref.c.9"></div> 
     1726      <div id="rfc.iref.c.8"></div> 
    17201727      <h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a>&nbsp;<a id="content-disposition" href="#content-disposition">Content-Disposition</a></h2> 
    17211728      <p id="rfc.section.B.1.p.1">The Content-Disposition response-header field has been proposed as a means for the origin server to suggest a default filename 
     
    17551762      <p id="rfc.section.C.1.p.4">A content-coding of "identity" was introduced, to solve problems discovered in caching. (<a href="#content.codings" title="Content Codings">Section&nbsp;2.2</a>) 
    17561763      </p> 
    1757       <p id="rfc.section.C.1.p.5">The Alternates<span id="rfc.iref.a.5"></span><span id="rfc.iref.h.12"></span>, Content-Version<span id="rfc.iref.c.10"></span><span id="rfc.iref.h.13"></span>, Derived-From<span id="rfc.iref.d.2"></span><span id="rfc.iref.h.14"></span>, Link<span id="rfc.iref.l.1"></span><span id="rfc.iref.h.15"></span>, URI<span id="rfc.iref.u.1"></span><span id="rfc.iref.h.16"></span>, Public<span id="rfc.iref.p.1"></span><span id="rfc.iref.h.17"></span> and Content-Base<span id="rfc.iref.c.11"></span><span id="rfc.iref.h.18"></span> header fields were defined in previous versions of this specification, but not commonly implemented. See <a href="http://tools.ietf.org/html/rfc2068#section-19.6.2">Section 19.6.2</a> of <a href="#RFC2068" id="rfc.xref.RFC2068.5"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>. 
     1764      <p id="rfc.section.C.1.p.5">The Alternates<span id="rfc.iref.a.5"></span><span id="rfc.iref.h.12"></span>, Content-Version<span id="rfc.iref.c.9"></span><span id="rfc.iref.h.13"></span>, Derived-From<span id="rfc.iref.d.2"></span><span id="rfc.iref.h.14"></span>, Link<span id="rfc.iref.l.1"></span><span id="rfc.iref.h.15"></span>, URI<span id="rfc.iref.u.1"></span><span id="rfc.iref.h.16"></span>, Public<span id="rfc.iref.p.1"></span><span id="rfc.iref.h.17"></span> and Content-Base<span id="rfc.iref.c.10"></span><span id="rfc.iref.h.18"></span> header fields were defined in previous versions of this specification, but not commonly implemented. See <a href="http://tools.ietf.org/html/rfc2068#section-19.6.2">Section 19.6.2</a> of <a href="#RFC2068" id="rfc.xref.RFC2068.5"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>. 
    17581765      </p> 
    17591766      <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2> 
     
    19671974      <ul> 
    19681975         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/13">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/13</a>&gt;: "Updated reference for language tags" 
     1976         </li> 
     1977         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/155">http://tools.ietf.org/wg/httpbis/trac/ticket/155</a>&gt;: "Content Sniffing" 
    19691978         </li> 
    19701979      </ul> 
     
    19891998                  <li class="indline1">compress&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.2">2.2</a></li> 
    19901999                  <li class="indline1">content negotiation&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.1">1.1</a></li> 
    1991                   <li class="indline1">Content Type Sniffing&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.3">3.2.1</a></li> 
    1992                   <li class="indline1">Content-Base header&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.11"><b>C.1</b></a></li> 
    1993                   <li class="indline1">Content-Disposition header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.content-disposition.1">6.1</a>, <a class="iref" href="#rfc.xref.content-disposition.2">7.2</a>, <a class="iref" href="#rfc.iref.c.9"><b>B.1</b></a>, <a class="iref" href="#rfc.extref.c.32">B.1</a>, <a class="iref" href="#rfc.extref.c.50">D</a></li> 
    1994                   <li class="indline1">Content-Encoding header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-encoding.1">2.2</a>, <a class="iref" href="#rfc.xref.header.content-encoding.2">3.1</a>, <a class="iref" href="#rfc.iref.c.4"><b>5.5</b></a>, <a class="iref" href="#rfc.xref.header.content-encoding.3">5.5</a>, <a class="iref" href="#rfc.xref.header.content-encoding.4">6.1</a></li> 
    1995                   <li class="indline1">Content-Language header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-language.1">3.1</a>, <a class="iref" href="#rfc.iref.c.5"><b>5.6</b></a>, <a class="iref" href="#rfc.xref.header.content-language.2">6.1</a></li> 
    1996                   <li class="indline1">Content-Location header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-location.1">3.1</a>, <a class="iref" href="#rfc.iref.c.6"><b>5.7</b></a>, <a class="iref" href="#rfc.xref.header.content-location.2">6.1</a></li> 
    1997                   <li class="indline1">Content-MD5 header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-md5.1">3.1</a>, <a class="iref" href="#rfc.iref.c.7"><b>5.8</b></a>, <a class="iref" href="#rfc.xref.header.content-md5.2">6.1</a></li> 
    1998                   <li class="indline1">Content-Type header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-type.1">2.3</a>, <a class="iref" href="#rfc.xref.header.content-type.2">3.1</a>, <a class="iref" href="#rfc.iref.c.8"><b>5.9</b></a>, <a class="iref" href="#rfc.xref.header.content-type.3">6.1</a></li> 
    1999                   <li class="indline1">Content-Version header&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.10"><b>C.1</b></a></li> 
     2000                  <li class="indline1">Content-Base header&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.10"><b>C.1</b></a></li> 
     2001                  <li class="indline1">Content-Disposition header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.content-disposition.1">6.1</a>, <a class="iref" href="#rfc.xref.content-disposition.2">7.2</a>, <a class="iref" href="#rfc.iref.c.8"><b>B.1</b></a>, <a class="iref" href="#rfc.extref.c.32">B.1</a>, <a class="iref" href="#rfc.extref.c.50">D</a></li> 
     2002                  <li class="indline1">Content-Encoding header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-encoding.1">2.2</a>, <a class="iref" href="#rfc.xref.header.content-encoding.2">3.1</a>, <a class="iref" href="#rfc.iref.c.3"><b>5.5</b></a>, <a class="iref" href="#rfc.xref.header.content-encoding.3">5.5</a>, <a class="iref" href="#rfc.xref.header.content-encoding.4">6.1</a></li> 
     2003                  <li class="indline1">Content-Language header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-language.1">3.1</a>, <a class="iref" href="#rfc.iref.c.4"><b>5.6</b></a>, <a class="iref" href="#rfc.xref.header.content-language.2">6.1</a></li> 
     2004                  <li class="indline1">Content-Location header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-location.1">3.1</a>, <a class="iref" href="#rfc.iref.c.5"><b>5.7</b></a>, <a class="iref" href="#rfc.xref.header.content-location.2">6.1</a></li> 
     2005                  <li class="indline1">Content-MD5 header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-md5.1">3.1</a>, <a class="iref" href="#rfc.iref.c.6"><b>5.8</b></a>, <a class="iref" href="#rfc.xref.header.content-md5.2">6.1</a></li> 
     2006                  <li class="indline1">Content-Type header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.content-type.1">2.3</a>, <a class="iref" href="#rfc.xref.header.content-type.2">3.1</a>, <a class="iref" href="#rfc.iref.c.7"><b>5.9</b></a>, <a class="iref" href="#rfc.xref.header.content-type.3">6.1</a></li> 
     2007                  <li class="indline1">Content-Version header&nbsp;&nbsp;<a class="iref" href="#rfc.iref.c.9"><b>C.1</b></a></li> 
    20002008               </ul> 
    20012009            </li> 
  • draft-ietf-httpbis/latest/p3-payload.xml

    r662 r663  
    782782   compression, that are a property of the requested resource.  There is 
    783783   no default encoding. 
    784 </t> 
    785 <t> 
    786    Note that neither the interpretation of the data type of a message nor 
    787    the behaviors caused by it are defined by HTTP; this 
    788    potentially includes examination of the content to override any 
    789    indicated type ("sniffing")<iref item="Content Type Sniffing"/>.  
    790784</t> 
    791785</section> 
     
    30333027      "Updated reference for language tags" 
    30343028    </t> 
     3029    <t> 
     3030      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/155"/>: 
     3031      "Content Sniffing" 
     3032    </t> 
    30353033  </list> 
    30363034</t> 
Note: See TracChangeset for help on using the changeset viewer.