Ignore:
Timestamp:
Dec 21, 2007, 4:30:59 PM (12 years ago)
Author:
fielding@…
Message:

Regenerate HTML after the following changes applied to XML drafts:

Resolve #1: HTTP Version should be case sensitive
Resolve #2: 'unsafe' characters
Resolve #3: Chunk Size Definition
Resolve #4: Message Length
Resolve #5: Via is a MUST
Resolve #6: Fragments allowed in Location
Resolve #8: Media type registrations, by updating to RFC 4288
Resolve #8: Media type registrations, by updating to RFC 4288
Resolve #9: Trailer
Resolve #11: URI includes query
Resolve #12: Invalidation after Update or Delete
Resolve #17: Revise description of the POST method
Resolve #18: Cache validators in 206 responses
Resolve #49: Connection header text
Resolve #14: Clarification regarding quoting of charset values
Resolve #47: inconsistency in date format explanation
Resolve #48: Date reference typo
Resolve #48: remove unnecessary reference to RFC1123

for consistency with draft-lafon

Resolve #16: Remove 'identity' token references
Resolve #15: No close on 1xx responses
(editorial) fix typo of varriant
Resolve #10: Safe Methods vs Redirection
Resolve #45: RFC977 reference
Resolve #42: RFC2606 compliance
Resolve #46: references to RFC1700

File:
1 edited

Legend:

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

    r62 r92  
    558558      </dl>
    559559      <p id="rfc.section.2.1.p.4">HTTP character sets are identified by case-insensitive tokens. The complete set of tokens is defined by the IANA Character
    560          Set registry <a href="#RFC1700" id="rfc.xref.RFC1700.1"><cite title="Assigned Numbers">[RFC1700]</cite></a>.
     560         Set registry (&lt;<a href="http://www.iana.org/assignments/character-sets">http://www.iana.org/assignments/character-sets</a>&gt;).
    561561      </p>
    562562      <div id="rfc.figure.u.1"></div><pre class="inline"><span id="rfc.iref.g.1"></span>    charset = token
    563563</pre><p id="rfc.section.2.1.p.6">Although HTTP allows an arbitrary token to be used as a charset value, any token that has a predefined value within the IANA
    564          Character Set registry <a href="#RFC1700" id="rfc.xref.RFC1700.2"><cite title="Assigned Numbers">[RFC1700]</cite></a>  <em class="bcp14">MUST</em> represent the character set defined by that registry. Applications <em class="bcp14">SHOULD</em> limit their use of character sets to those defined by the IANA registry.
    565       </p>
    566       <p id="rfc.section.2.1.p.7">Implementors should be aware of IETF character set requirements <a href="#RFC2279" id="rfc.xref.RFC2279.1"><cite title="UTF-8, a transformation format of ISO 10646">[RFC2279]</cite></a>  <a href="#RFC2277" id="rfc.xref.RFC2277.1"><cite title="IETF Policy on Character Sets and Languages">[RFC2277]</cite></a>.
     564         Character Set registry <em class="bcp14">MUST</em> represent the character set defined by that registry. Applications <em class="bcp14">SHOULD</em> limit their use of character sets to those defined by the IANA registry.
     565      </p>
     566      <p id="rfc.section.2.1.p.7">HTTP uses charset in two contexts: within an Accept-Charset request header (in which the charset value is an unquoted token)
     567         and as the value of a parameter in a Content-type header (within a request or response), in which case the parameter value
     568         of the charset parameter may be quoted.
     569      </p>
     570      <p id="rfc.section.2.1.p.8">Implementors should be aware of IETF character set requirements <a href="#RFC2279" id="rfc.xref.RFC2279.1"><cite title="UTF-8, a transformation format of ISO 10646">[RFC2279]</cite></a>  <a href="#RFC2277" id="rfc.xref.RFC2277.1"><cite title="IETF Policy on Character Sets and Languages">[RFC2277]</cite></a>.
    567571      </p>
    568572      <h3 id="rfc.section.2.1.1"><a href="#rfc.section.2.1.1">2.1.1</a>&nbsp;<a id="missing.charset" href="#missing.charset">Missing Charset</a></h3>
     
    621625      </p>
    622626      <h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a>&nbsp;<a id="media.types" href="#media.types">Media Types</a></h2>
    623       <p id="rfc.section.2.3.p.1">HTTP uses Internet Media Types <a href="#RFC1590" id="rfc.xref.RFC1590.1"><cite title="Media Type Registration Procedure">[RFC1590]</cite></a> in the Content-Type (<a href="#header.content-type" id="rfc.xref.header.content-type.1" title="Content-Type">Section&nbsp;5.9</a>) and Accept (<a href="#header.accept" id="rfc.xref.header.accept.1" title="Accept">Section&nbsp;5.1</a>) header fields in order to provide open and extensible data typing and type negotiation.
     627      <p id="rfc.section.2.3.p.1">HTTP uses Internet Media Types <a href="#RFC4288" id="rfc.xref.RFC4288.1"><cite title="Media Type Specifications and Registration Procedures">[RFC4288]</cite></a> in the Content-Type (<a href="#header.content-type" id="rfc.xref.header.content-type.1" title="Content-Type">Section&nbsp;5.9</a>) and Accept (<a href="#header.accept" id="rfc.xref.header.accept.1" title="Accept">Section&nbsp;5.1</a>) header fields in order to provide open and extensible data typing and type negotiation.
    624628      </p>
    625629      <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span>    media-type     = type "/" subtype *( ";" parameter )
     
    638642         implementations <em class="bcp14">SHOULD</em> only use media type parameters when they are required by that type/subtype definition.
    639643      </p>
    640       <p id="rfc.section.2.3.p.7">Media-type values are registered with the Internet Assigned Number Authority (IANA <a href="#RFC1700" id="rfc.xref.RFC1700.3"><cite title="Assigned Numbers">[RFC1700]</cite></a>). The media type registration process is outlined in RFC 1590 <a href="#RFC1590" id="rfc.xref.RFC1590.2"><cite title="Media Type Registration Procedure">[RFC1590]</cite></a>. Use of non-registered media types is discouraged.
     644      <p id="rfc.section.2.3.p.7">Media-type values are registered with the Internet Assigned Number Authority (IANA). The media type registration process is
     645         outlined in RFC 4288 <a href="#RFC4288" id="rfc.xref.RFC4288.2"><cite title="Media Type Specifications and Registration Procedures">[RFC4288]</cite></a>. Use of non-registered media types is discouraged.
    641646      </p>
    642647      <h3 id="rfc.section.2.3.1"><a href="#rfc.section.2.3.1">2.3.1</a>&nbsp;<a id="canonicalization.and.text.defaults" href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></h3>
     
    11631168      <h1 id="rfc.references"><a href="#rfc.section.9" id="rfc.section.9">9.</a> References
    11641169      </h1>
    1165       <table summary="References">                                                 
     1170      <table summary="References">                                               
    11661171         <tr>
    11671172            <td class="reference"><b id="Part1">[Part1]</b></td>
     
    11901195         </tr>
    11911196         <tr>
    1192             <td class="reference"><b id="RFC1590">[RFC1590]</b></td>
    1193             <td class="top"><a title="USC/Information Sciences Institute">Postel, J.</a>, “<a href="http://tools.ietf.org/html/rfc1590">Media Type Registration Procedure</a>”, RFC&nbsp;1590, November&nbsp;1996.
    1194             </td>
    1195          </tr>
    1196          <tr>
    1197             <td class="reference"><b id="RFC1700">[RFC1700]</b></td>
    1198             <td class="top"><a title="USC/Information Sciences Institute">Reynolds, J.</a> and <a title="USC/Information Sciences Institute">J. Postel</a>, “<a href="http://tools.ietf.org/html/rfc1700">Assigned Numbers</a>”, STD&nbsp;2, RFC&nbsp;1700, October&nbsp;1994.
    1199             </td>
    1200          </tr>
    1201          <tr>
    12021197            <td class="reference"><b id="RFC1766">[RFC1766]</b></td>
    12031198            <td class="top"><a title="UNINETT">Alvestrand, H.</a>, “<a href="http://tools.ietf.org/html/rfc1766">Tags for the Identification of Languages</a>”, RFC&nbsp;1766, March&nbsp;1995.
     
    12821277            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
    12831278            <td class="top"><a title="University of California, Irvine">Fielding, R.</a>, <a title="W3C">Gettys, J.</a>, <a title="Compaq Computer Corporation">Mogul, J.</a>, <a title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a title="Xerox Corporation">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, and <a title="W3C">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
     1279            </td>
     1280         </tr>
     1281         <tr>
     1282            <td class="reference"><b id="RFC4288">[RFC4288]</b></td>
     1283            <td class="top"><a title="Sun Microsystems">Freed, N.</a> and <a>J. Klensin</a>, “<a href="http://tools.ietf.org/html/rfc4288">Media Type Specifications and Registration Procedures</a>”, BCP&nbsp;13, RFC&nbsp;4288, December&nbsp;2005.
    12841284            </td>
    12851285         </tr>
     
    13391339      </p>
    13401340      <h2 id="rfc.section.A.4"><a href="#rfc.section.A.4">A.4</a>&nbsp;<a id="no.content-transfer-encoding" href="#no.content-transfer-encoding">No Content-Transfer-Encoding</a></h2>
    1341       <p id="rfc.section.A.4.p.1">HTTP does not use the Content-Transfer-Encoding (CTE) field of RFC 2045. Proxies and gateways from MIME-compliant protocols
    1342          to HTTP <em class="bcp14">MUST</em> remove any non-identity CTE ("quoted-printable" or "base64") encoding prior to delivering the response message to an HTTP
    1343          client.
     1341      <p id="rfc.section.A.4.p.1">HTTP does not use the Content-Transfer-Encoding field of RFC 2045. Proxies and gateways from MIME-compliant protocols to HTTP <em class="bcp14">MUST</em> remove any Content-Transfer-Encoding prior to delivering the response message to an HTTP client.
    13441342      </p>
    13451343      <p id="rfc.section.A.4.p.2">Proxies and gateways from HTTP to MIME-compliant protocols are responsible for ensuring that the message is in the correct
     
    15641562            </li>
    15651563            <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind">
    1566                   <li class="indline1"><em>RFC1590</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1590.1">2.3</a>, <a class="iref" href="#rfc.xref.RFC1590.2">2.3</a>, <a class="iref" href="#RFC1590"><b>9</b></a></li>
    1567                   <li class="indline1"><em>RFC1700</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1700.1">2.1</a>, <a class="iref" href="#rfc.xref.RFC1700.2">2.1</a>, <a class="iref" href="#rfc.xref.RFC1700.3">2.3</a>, <a class="iref" href="#RFC1700"><b>9</b></a></li>
    15681564                  <li class="indline1"><em>RFC1766</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1766.1">2.5</a>, <a class="iref" href="#RFC1766"><b>9</b></a></li>
    15691565                  <li class="indline1"><em>RFC1806</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1806.1">7.2</a>, <a class="iref" href="#RFC1806"><b>9</b></a>, <a class="iref" href="#rfc.xref.RFC1806.2">B.1</a></li>
     
    15891585                  <li class="indline1"><em>RFC2279</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2279.1">2.1</a>, <a class="iref" href="#RFC2279"><b>9</b></a></li>
    15901586                  <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">§</a>, <a class="iref" href="#RFC2616"><b>9</b></a></li>
     1587                  <li class="indline1"><em>RFC4288</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC4288.1">2.3</a>, <a class="iref" href="#rfc.xref.RFC4288.2">2.3</a>, <a class="iref" href="#RFC4288"><b>9</b></a></li>
    15911588                  <li class="indline1"><em>RFC822</em>&nbsp;&nbsp;<a class="iref" href="#RFC822"><b>9</b></a>, <a class="iref" href="#rfc.xref.RFC822.1">A</a></li>
    15921589               </ul>
Note: See TracChangeset for help on using the changeset viewer.