Ignore:
Timestamp:
14/06/14 11:20:37 (6 years ago)
Author:
julian.reschke@…
Message:

update to latest version of rfc2629.xslt, regen all HTML

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/25/p2-semantics.html

    r2495 r2726  
    77var buttonsAdded = false;
    88
    9 function init() {
     9function initFeedback() {
    1010  var fb = document.createElement("div");
    1111  fb.className = "feedback noprint";
     
    144144  page-break-after: avoid;
    145145}
    146 h3, h4, h5, h6 {
     146h3 {
    147147  font-size: 110%;
     148  page-break-after: avoid;
     149}
     150h4, h5, h6 {
    148151  page-break-after: avoid;
    149152}
     
    205208table.tt {
    206209  vertical-align: top;
     210  border-color: gray;
     211}
     212table.tt th {
     213  border-color: gray;
     214}
     215table.tt td {
     216  border-color: gray;
     217}
     218table.all {
     219  border-style: solid;
     220  border-width: 2px;
    207221}
    208222table.full {
    209   border-style: outset;
    210   border-width: 1px;
    211 }
    212 table.headers {
    213   border-style: outset;
    214   border-width: 1px;
     223  border-style: solid;
     224  border-width: 2px;
    215225}
    216226table.tt td {
    217227  vertical-align: top;
    218228}
     229table.all td {
     230  border-style: solid;
     231  border-width: 1px;
     232}
    219233table.full td {
    220   border-style: inset;
     234  border-style: none solid;
    221235  border-width: 1px;
    222236}
     
    224238  vertical-align: top;
    225239}
     240table.all th {
     241  border-style: solid;
     242  border-width: 1px;
     243}
    226244table.full th {
    227   border-style: inset;
    228   border-width: 1px;
     245  border-style: solid;
     246  border-width: 1px 1px 2px 1px;
    229247}
    230248table.headers th {
    231   border-style: none none inset none;
    232   border-width: 1px;
     249  border-style: none none solid none;
     250  border-width: 2px;
    233251}
    234252table.left {
     
    485503      <link href="p1-messaging.html" rel="prev">
    486504      <link href="p4-conditional.html" rel="next">
    487       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.607, 2013/10/15 13:23:22, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     505      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.640, 2014/06/13 12:42:58, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    488506      <link rel="schema.dct" href="http://purl.org/dc/terms/">
    489507      <meta name="dct.creator" content="Fielding, R.">
     
    495513      <meta name="description" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation.">
    496514   </head>
    497    <body onload="init();">
     515   <body onload="initFeedback();">
    498516      <table class="header">
    499517         <tbody>
     
    507525            </tr>
    508526            <tr>
    509                <td class="left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
     527               <td class="left">Obsoletes: <a href="https://tools.ietf.org/html/rfc2616">2616</a> (if approved)
    510528               </td>
    511529               <td class="right">J. Reschke, Editor</td>
    512530            </tr>
    513531            <tr>
    514                <td class="left">Updates: <a href="http://tools.ietf.org/html/rfc2817">2817</a> (if approved)
     532               <td class="left">Updates: <a href="https://tools.ietf.org/html/rfc2817">2817</a> (if approved)
    515533               </td>
    516534               <td class="right">greenbytes</td>
     
    579597         <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#representations">Representations</a><ul>
    580598               <li><a href="#rfc.section.3.1">3.1</a>&nbsp;&nbsp;&nbsp;<a href="#representation.metadata">Representation Metadata</a><ul>
    581                      <li><a href="#rfc.section.3.1.1">3.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#data.type">Processing Representation Data</a><ul>
    582                            <li><a href="#rfc.section.3.1.1.1">3.1.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#media.type">Media Type</a></li>
    583                            <li><a href="#rfc.section.3.1.1.2">3.1.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#charset">Charset</a></li>
    584                            <li><a href="#rfc.section.3.1.1.3">3.1.1.3</a>&nbsp;&nbsp;&nbsp;<a href="#canonicalization.and.text.defaults">Canonicalization and Text Defaults</a></li>
    585                            <li><a href="#rfc.section.3.1.1.4">3.1.1.4</a>&nbsp;&nbsp;&nbsp;<a href="#multipart.types">Multipart Types</a></li>
    586                            <li><a href="#rfc.section.3.1.1.5">3.1.1.5</a>&nbsp;&nbsp;&nbsp;<a href="#header.content-type">Content-Type</a></li>
    587                         </ul>
    588                      </li>
    589                      <li><a href="#rfc.section.3.1.2">3.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#data.encoding">Encoding for Compression or Integrity</a><ul>
    590                            <li><a href="#rfc.section.3.1.2.1">3.1.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#content.codings">Content Codings</a></li>
    591                            <li><a href="#rfc.section.3.1.2.2">3.1.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.content-encoding">Content-Encoding</a></li>
    592                         </ul>
    593                      </li>
    594                      <li><a href="#rfc.section.3.1.3">3.1.3</a>&nbsp;&nbsp;&nbsp;<a href="#audience.language">Audience Language</a><ul>
    595                            <li><a href="#rfc.section.3.1.3.1">3.1.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#language.tags">Language Tags</a></li>
    596                            <li><a href="#rfc.section.3.1.3.2">3.1.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.content-language">Content-Language</a></li>
    597                         </ul>
    598                      </li>
    599                      <li><a href="#rfc.section.3.1.4">3.1.4</a>&nbsp;&nbsp;&nbsp;<a href="#identification">Identification</a><ul>
    600                            <li><a href="#rfc.section.3.1.4.1">3.1.4.1</a>&nbsp;&nbsp;&nbsp;<a href="#identifying.payload">Identifying a Representation</a></li>
    601                            <li><a href="#rfc.section.3.1.4.2">3.1.4.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.content-location">Content-Location</a></li>
    602                         </ul>
    603                      </li>
     599                     <li><a href="#rfc.section.3.1.1">3.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#data.type">Processing Representation Data</a></li>
     600                     <li><a href="#rfc.section.3.1.2">3.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#data.encoding">Encoding for Compression or Integrity</a></li>
     601                     <li><a href="#rfc.section.3.1.3">3.1.3</a>&nbsp;&nbsp;&nbsp;<a href="#audience.language">Audience Language</a></li>
     602                     <li><a href="#rfc.section.3.1.4">3.1.4</a>&nbsp;&nbsp;&nbsp;<a href="#identification">Identification</a></li>
    604603                  </ul>
    605604               </li>
     
    715714         <li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#response.header.fields">Response Header Fields</a><ul>
    716715               <li><a href="#rfc.section.7.1">7.1</a>&nbsp;&nbsp;&nbsp;<a href="#response.control.data">Control Data</a><ul>
    717                      <li><a href="#rfc.section.7.1.1">7.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#origination.date">Origination Date</a><ul>
    718                            <li><a href="#rfc.section.7.1.1.1">7.1.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#http.date">Date/Time Formats</a></li>
    719                            <li><a href="#rfc.section.7.1.1.2">7.1.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.date">Date</a></li>
    720                         </ul>
    721                      </li>
     716                     <li><a href="#rfc.section.7.1.1">7.1.1</a>&nbsp;&nbsp;&nbsp;<a href="#origination.date">Origination Date</a></li>
    722717                     <li><a href="#rfc.section.7.1.2">7.1.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.location">Location</a></li>
    723718                     <li><a href="#rfc.section.7.1.3">7.1.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.retry-after">Retry-After</a></li>
     
    774769            </ul>
    775770         </li>
    776          <li><a href="#rfc.authors">Authors' Addresses</a></li>
    777771         <li><a href="#rfc.section.A">A.</a>&nbsp;&nbsp;&nbsp;<a href="#differences.between.http.and.mime">Differences between HTTP and MIME</a><ul>
    778772               <li><a href="#rfc.section.A.1">A.1</a>&nbsp;&nbsp;&nbsp;<a href="#mime-version">MIME-Version</a></li>
     
    793787         </li>
    794788         <li><a href="#rfc.index">Index</a></li>
     789         <li><a href="#rfc.authors">Authors' Addresses</a></li>
    795790      </ul>
    796791      <div id="introduction">
     
    959954                  <h4 id="rfc.section.3.1.1.4"><a href="#rfc.section.3.1.1.4">3.1.1.4</a>&nbsp;<a href="#multipart.types">Multipart Types</a></h4>
    960955                  <p id="rfc.section.3.1.1.4.p.1">MIME provides for a number of "multipart" types — encapsulations of one or more representations within a single message body.
    961                      All multipart types share a common syntax, as defined in <a href="http://tools.ietf.org/html/rfc2046#section-5.1.1">Section 5.1.1</a> of <a href="#RFC2046" id="rfc.xref.RFC2046.2"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>, and include a boundary parameter as part of the media type value. The message body is itself a protocol element; a sender <em class="bcp14">MUST</em> generate only CRLF to represent line breaks between body parts.
     956                     All multipart types share a common syntax, as defined in <a href="https://tools.ietf.org/html/rfc2046#section-5.1.1">Section 5.1.1</a> of <a href="#RFC2046" id="rfc.xref.RFC2046.2"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>, and include a boundary parameter as part of the media type value. The message body is itself a protocol element; a sender <em class="bcp14">MUST</em> generate only CRLF to represent line breaks between body parts.
    962957                  </p>
    963958                  <p id="rfc.section.3.1.1.4.p.2">HTTP message framing does not use the multipart boundary as an indicator of message body length, though it might be used by
     
    978973                  <div id="rfc.figure.u.6"></div><pre class="text">  Content-Type: text/html; charset=ISO-8859-4
    979974</pre><p id="rfc.section.3.1.1.5.p.5">A sender that generates a message containing a payload body <em class="bcp14">SHOULD</em> generate a Content-Type header field in that message unless the intended media type of the enclosed representation is unknown
    980                      to the sender. If a Content-Type header field is not present, the recipient <em class="bcp14">MAY</em> either assume a media type of "application/octet-stream" (<a href="#RFC2046" id="rfc.xref.RFC2046.3"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>, <a href="http://tools.ietf.org/html/rfc2046#section-4.5.1">Section 4.5.1</a>) or examine the data to determine its type.
     975                     to the sender. If a Content-Type header field is not present, the recipient <em class="bcp14">MAY</em> either assume a media type of "application/octet-stream" (<a href="#RFC2046" id="rfc.xref.RFC2046.3"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a>, <a href="https://tools.ietf.org/html/rfc2046#section-4.5.1">Section 4.5.1</a>) or examine the data to determine its type.
    981976                  </p>
    982977                  <p id="rfc.section.3.1.1.5.p.6">In practice, resource owners do not always properly configure their origin server to provide the correct Content-Type for
     
    10561051                  <p id="rfc.section.3.1.3.1.p.2">HTTP uses language tags within the <a href="#header.accept-language" class="smpl">Accept-Language</a> and <a href="#header.content-language" class="smpl">Content-Language</a> header fields. <a href="#header.accept-language" class="smpl">Accept-Language</a> uses the broader language-range production defined in <a href="#header.accept-language" id="rfc.xref.header.accept-language.1" title="Accept-Language">Section&nbsp;5.3.5</a>, whereas <a href="#header.content-language" class="smpl">Content-Language</a> uses the language-tag production defined below.
    10571052                  </p>
    1058                   <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.12"></span>  <a href="#language.tags" class="smpl">language-tag</a> = &lt;Language-Tag, defined in <a href="#RFC5646" id="rfc.xref.RFC5646.2"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a>, <a href="http://tools.ietf.org/html/rfc5646#section-2.1">Section 2.1</a>&gt;
     1053                  <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.12"></span>  <a href="#language.tags" class="smpl">language-tag</a> = &lt;Language-Tag, defined in <a href="#RFC5646" id="rfc.xref.RFC5646.2"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a>, <a href="https://tools.ietf.org/html/rfc5646#section-2.1">Section 2.1</a>&gt;
    10591054</pre><p id="rfc.section.3.1.3.1.p.4">A language tag is a sequence of one or more case-insensitive subtags, each separated by a hyphen character ("-", %x2D). In
    10601055                     most cases, a language tag consists of a primary language subtag that identifies a broad family of related languages (e.g.,
     
    11341129                  <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.14"></span>  <a href="#header.content-location" class="smpl">Content-Location</a> = <a href="#imported.abnf" class="smpl">absolute-URI</a> / <a href="#imported.abnf" class="smpl">partial-URI</a>
    11351130</pre><p id="rfc.section.3.1.4.2.p.3">The Content-Location value is not a replacement for the effective Request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.12"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>). It is representation metadata. It has the same syntax and semantics as the header field of the same name defined for MIME
    1136                      body parts in <a href="http://tools.ietf.org/html/rfc2557#section-4">Section 4</a> of <a href="#RFC2557" id="rfc.xref.RFC2557.1"><cite title="MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)">[RFC2557]</cite></a>. However, its appearance in an HTTP message has some special implications for HTTP recipients.
     1131                     body parts in <a href="https://tools.ietf.org/html/rfc2557#section-4">Section 4</a> of <a href="#RFC2557" id="rfc.xref.RFC2557.1"><cite title="MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)">[RFC2557]</cite></a>. However, its appearance in an HTTP message has some special implications for HTTP recipients.
    11371132                  </p>
    11381133                  <p id="rfc.section.3.1.4.2.p.4">If Content-Location is included in a <a href="#status.2xx" class="smpl">2xx (Successful)</a> response message and its value refers (after conversion to absolute form) to a URI that is the same as the effective request
     
    17591754            <div id="header.expect">
    17601755               <div id="rfc.iref.e.1"></div>
    1761                <div id="rfc.iref.40"></div>
     1756               <div id="rfc.iref.1.1"></div>
    17621757               <h3 id="rfc.section.5.1.1"><a href="#rfc.section.5.1.1">5.1.1</a>&nbsp;<a href="#header.expect">Expect</a></h3>
    17631758               <p id="rfc.section.5.1.1.p.1">The "Expect" header field in a request indicates a certain set of behaviors (expectations) that need to be supported by the
     
    21072102               <div id="rfc.figure.u.33"></div><pre class="inline"><span id="rfc.iref.g.28"></span><span id="rfc.iref.g.29"></span>  <a href="#header.accept-language" class="smpl">Accept-Language</a> = 1#( <a href="#header.accept-language" class="smpl">language-range</a> [ <a href="#quality.values" class="smpl">weight</a> ] )
    21082103  <a href="#header.accept-language" class="smpl">language-range</a>  =
    2109             &lt;language-range, defined in <a href="#RFC4647" id="rfc.xref.RFC4647.1"><cite title="Matching of Language Tags">[RFC4647]</cite></a>, <a href="http://tools.ietf.org/html/rfc4647#section-2.1">Section 2.1</a>&gt;
     2104            &lt;language-range, defined in <a href="#RFC4647" id="rfc.xref.RFC4647.1"><cite title="Matching of Language Tags">[RFC4647]</cite></a>, <a href="https://tools.ietf.org/html/rfc4647#section-2.1">Section 2.1</a>&gt;
    21102105</pre><p id="rfc.section.5.3.5.p.3">Each language-range can be given an associated quality value representing an estimate of the user's preference for the languages
    21112106                  specified by that range, as defined in <a href="#quality.values" title="Quality Values">Section&nbsp;5.3.1</a>. For example,
     
    21222117                  for tags that are assigned equal quality values (no value is the same as q=1). However, this behavior cannot be relied upon.
    21232118                  For consistency and to maximize interoperability, many user agents assign each language tag a unique quality value while also
    2124                   listing them in order of decreasing quality. Additional discussion of language priority lists can be found in <a href="http://tools.ietf.org/html/rfc4647#section-2.3">Section 2.3</a> of <a href="#RFC4647" id="rfc.xref.RFC4647.2"><cite title="Matching of Language Tags">[RFC4647]</cite></a>.
    2125                </p>
    2126                <p id="rfc.section.5.3.5.p.8">For matching, <a href="http://tools.ietf.org/html/rfc4647#section-3">Section 3</a> of <a href="#RFC4647" id="rfc.xref.RFC4647.3"><cite title="Matching of Language Tags">[RFC4647]</cite></a> defines several matching schemes. Implementations can offer the most appropriate matching scheme for their requirements. The
    2127                   "Basic Filtering" scheme (<a href="#RFC4647" id="rfc.xref.RFC4647.4"><cite title="Matching of Language Tags">[RFC4647]</cite></a>, <a href="http://tools.ietf.org/html/rfc4647#section-3.3.1">Section 3.3.1</a>) is identical to the matching scheme that was previously defined for HTTP in <a href="http://tools.ietf.org/html/rfc2616#section-14.4">Section 14.4</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
     2119                  listing them in order of decreasing quality. Additional discussion of language priority lists can be found in <a href="https://tools.ietf.org/html/rfc4647#section-2.3">Section 2.3</a> of <a href="#RFC4647" id="rfc.xref.RFC4647.2"><cite title="Matching of Language Tags">[RFC4647]</cite></a>.
     2120               </p>
     2121               <p id="rfc.section.5.3.5.p.8">For matching, <a href="https://tools.ietf.org/html/rfc4647#section-3">Section 3</a> of <a href="#RFC4647" id="rfc.xref.RFC4647.3"><cite title="Matching of Language Tags">[RFC4647]</cite></a> defines several matching schemes. Implementations can offer the most appropriate matching scheme for their requirements. The
     2122                  "Basic Filtering" scheme (<a href="#RFC4647" id="rfc.xref.RFC4647.4"><cite title="Matching of Language Tags">[RFC4647]</cite></a>, <a href="https://tools.ietf.org/html/rfc4647#section-3.3.1">Section 3.3.1</a>) is identical to the matching scheme that was previously defined for HTTP in <a href="https://tools.ietf.org/html/rfc2616#section-14.4">Section 14.4</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
    21282123               </p>
    21292124               <p id="rfc.section.5.3.5.p.9">It might be contrary to the privacy expectations of the user to send an Accept-Language header field with the complete linguistic
     
    22002195               <h3 id="rfc.section.5.5.1"><a href="#rfc.section.5.5.1">5.5.1</a>&nbsp;<a href="#header.from">From</a></h3>
    22012196               <p id="rfc.section.5.5.1.p.1">The "From" header field contains an Internet email address for a human user who controls the requesting user agent. The address
    2202                   ought to be machine-usable, as defined by "mailbox" in <a href="http://tools.ietf.org/html/rfc5322#section-3.4">Section 3.4</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.1"><cite title="Internet Message Format">[RFC5322]</cite></a>:
     2197                  ought to be machine-usable, as defined by "mailbox" in <a href="https://tools.ietf.org/html/rfc5322#section-3.4">Section 3.4</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.1"><cite title="Internet Message Format">[RFC5322]</cite></a>:
    22032198               </p>
    22042199               <div id="rfc.figure.u.35"></div><pre class="inline"><span id="rfc.iref.g.30"></span>  <a href="#header.from" class="smpl">From</a>    = <a href="#header.from" class="smpl">mailbox</a>
    22052200 
    2206   <a href="#header.from" class="smpl">mailbox</a> = &lt;mailbox, defined in <a href="#RFC5322" id="rfc.xref.RFC5322.2"><cite title="Internet Message Format">[RFC5322]</cite></a>, <a href="http://tools.ietf.org/html/rfc5322#section-3.4">Section 3.4</a>&gt;
     2201  <a href="#header.from" class="smpl">mailbox</a> = &lt;mailbox, defined in <a href="#RFC5322" id="rfc.xref.RFC5322.2"><cite title="Internet Message Format">[RFC5322]</cite></a>, <a href="https://tools.ietf.org/html/rfc5322#section-3.4">Section 3.4</a>&gt;
    22072202</pre><p id="rfc.section.5.5.1.p.3">An example is:</p>
    22082203               <div id="rfc.figure.u.36"></div><pre class="text">  From: webmaster@example.org
     
    25342529         <div id="status.1xx">
    25352530            <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a>&nbsp;<a href="#status.1xx">Informational 1xx</a></h2>
    2536             <div id="rfc.iref.67"></div>
     2531            <div id="rfc.iref.1.2"></div>
    25372532            <div id="rfc.iref.s.3"></div>
    25382533            <p id="rfc.section.6.2.p.1">The <dfn>1xx (Informational)</dfn> class of status code indicates an interim response for communicating connection status or request progress prior to completing
     
    25482543            </p>
    25492544            <div id="status.100">
    2550                <div id="rfc.iref.68"></div>
     2545               <div id="rfc.iref.1.3"></div>
    25512546               <h3 id="rfc.section.6.2.1"><a href="#rfc.section.6.2.1">6.2.1</a>&nbsp;<a href="#status.100">100 Continue</a></h3>
    25522547               <p id="rfc.section.6.2.1.p.1">The <dfn>100 (Continue)</dfn> status code indicates that the initial part of a request has been received and has not yet been rejected by the server. The
     
    25592554            </div>
    25602555            <div id="status.101">
    2561                <div id="rfc.iref.68"></div>
     2556               <div id="rfc.iref.1.4"></div>
    25622557               <h3 id="rfc.section.6.2.2"><a href="#rfc.section.6.2.2">6.2.2</a>&nbsp;<a href="#status.101">101 Switching Protocols</a></h3>
    25632558               <p id="rfc.section.6.2.2.p.1">The <dfn>101 (Switching Protocols)</dfn> status code indicates that the server understands and is willing to comply with the client's request, via the <a href="p1-messaging.html#header.upgrade" class="smpl">Upgrade</a> header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 6.7</a> of <a href="#Part1" id="rfc.xref.Part1.23"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>), for a change in the application protocol being used on this connection. The server <em class="bcp14">MUST</em> generate an Upgrade header field in the response that indicates which protocol(s) will be switched to immediately after the
     
    25722567         <div id="status.2xx">
    25732568            <h2 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3</a>&nbsp;<a href="#status.2xx">Successful 2xx</a></h2>
    2574             <div id="rfc.iref.68"></div>
     2569            <div id="rfc.iref.2.1"></div>
    25752570            <div id="rfc.iref.s.4"></div>
    25762571            <p id="rfc.section.6.3.p.1">The <dfn>2xx (Successful)</dfn> class of status code indicates that the client's request was successfully received, understood, and accepted.
    25772572            </p>
    25782573            <div id="status.200">
    2579                <div id="rfc.iref.69"></div>
     2574               <div id="rfc.iref.2.2"></div>
    25802575               <h3 id="rfc.section.6.3.1"><a href="#rfc.section.6.3.1">6.3.1</a>&nbsp;<a href="#status.200">200 OK</a></h3>
    25812576               <p id="rfc.section.6.3.1.p.1">The <dfn>200 (OK)</dfn> status code indicates that the request has succeeded. The payload sent in a 200 response depends on the request method. For
     
    26052600            </div>
    26062601            <div id="status.201">
    2607                <div id="rfc.iref.69"></div>
     2602               <div id="rfc.iref.2.3"></div>
    26082603               <h3 id="rfc.section.6.3.2"><a href="#rfc.section.6.3.2">6.3.2</a>&nbsp;<a href="#status.201">201 Created</a></h3>
    26092604               <p id="rfc.section.6.3.2.p.1">The <dfn>201 (Created)</dfn> status code indicates that the request has been fulfilled and has resulted in one or more new resources being created. The
     
    26142609            </div>
    26152610            <div id="status.202">
    2616                <div id="rfc.iref.69"></div>
     2611               <div id="rfc.iref.2.4"></div>
    26172612               <h3 id="rfc.section.6.3.3"><a href="#rfc.section.6.3.3">6.3.3</a>&nbsp;<a href="#status.202">202 Accepted</a></h3>
    26182613               <p id="rfc.section.6.3.3.p.1">The <dfn>202 (Accepted)</dfn> status code indicates that the request has been accepted for processing, but the processing has not been completed. The request
     
    26282623            </div>
    26292624            <div id="status.203">
    2630                <div id="rfc.iref.69"></div>
     2625               <div id="rfc.iref.2.5"></div>
    26312626               <h3 id="rfc.section.6.3.4"><a href="#rfc.section.6.3.4">6.3.4</a>&nbsp;<a href="#status.203">203 Non-Authoritative Information</a></h3>
    26322627               <p id="rfc.section.6.3.4.p.1">The <dfn>203 (Non-Authoritative Information)</dfn> status code indicates that the request was successful but the enclosed payload has been modified from that of the origin server's <a href="#status.200" class="smpl">200 (OK)</a> response by a transforming proxy (<a href="p1-messaging.html#message.transformations" title="Transformations">Section 5.7.2</a> of <a href="#Part1" id="rfc.xref.Part1.24"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>). This status code allows the proxy to notify recipients when a transformation has been applied, since that knowledge might
     
    26412636            </div>
    26422637            <div id="status.204">
    2643                <div id="rfc.iref.69"></div>
     2638               <div id="rfc.iref.2.6"></div>
    26442639               <h3 id="rfc.section.6.3.5"><a href="#rfc.section.6.3.5">6.3.5</a>&nbsp;<a href="#status.204">204 No Content</a></h3>
    26452640               <p id="rfc.section.6.3.5.p.1">The <dfn>204 (No Content)</dfn> status code indicates that the server has successfully fulfilled the request and that there is no additional content to send
     
    26642659            </div>
    26652660            <div id="status.205">
    2666                <div id="rfc.iref.69"></div>
     2661               <div id="rfc.iref.2.7"></div>
    26672662               <h3 id="rfc.section.6.3.6"><a href="#rfc.section.6.3.6">6.3.6</a>&nbsp;<a href="#status.205">205 Reset Content</a></h3>
    26682663               <p id="rfc.section.6.3.6.p.1">The <dfn>205 (Reset Content)</dfn> status code indicates that the server has fulfilled the request and desires that the user agent reset the "document view",
     
    26802675         <div id="status.3xx">
    26812676            <h2 id="rfc.section.6.4"><a href="#rfc.section.6.4">6.4</a>&nbsp;<a href="#status.3xx">Redirection 3xx</a></h2>
    2682             <div id="rfc.iref.69"></div>
     2677            <div id="rfc.iref.3.1"></div>
    26832678            <div id="rfc.iref.s.5"></div>
    26842679            <p id="rfc.section.6.4.p.1">The <dfn>3xx (Redirection)</dfn> class of status code indicates that further action needs to be taken by the user agent in order to fulfill the request. If
     
    27062701            </ol>
    27072702            <div class="note" id="rfc.section.6.4.p.3">
    2708                <p><b>Note:</b> In HTTP/1.0, the status codes <a href="#status.301" class="smpl">301 (Moved Permanently)</a> and <a href="#status.302" class="smpl">302 (Found)</a> were defined for the first type of redirect (<a href="#RFC1945" id="rfc.xref.RFC1945.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.0">[RFC1945]</cite></a>, <a href="http://tools.ietf.org/html/rfc1945#section-9.3">Section 9.3</a>). Early user agents split on whether the method applied to the redirect target would be the same as the original request
     2703               <p><b>Note:</b> In HTTP/1.0, the status codes <a href="#status.301" class="smpl">301 (Moved Permanently)</a> and <a href="#status.302" class="smpl">302 (Found)</a> were defined for the first type of redirect (<a href="#RFC1945" id="rfc.xref.RFC1945.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.0">[RFC1945]</cite></a>, <a href="https://tools.ietf.org/html/rfc1945#section-9.3">Section 9.3</a>). Early user agents split on whether the method applied to the redirect target would be the same as the original request
    27092704                  or would be rewritten as GET. Although HTTP originally defined the former semantics for <a href="#status.301" class="smpl">301</a> and <a href="#status.302" class="smpl">302</a> (to match its original implementation at CERN), and defined <a href="#status.303" class="smpl">303 (See Other)</a> to match the latter semantics, prevailing practice gradually converged on the latter semantics for <a href="#status.301" class="smpl">301</a> and <a href="#status.302" class="smpl">302</a> as well. The first revision of HTTP/1.1 added <a href="#status.307" class="smpl">307 (Temporary Redirect)</a> to indicate the former semantics without being impacted by divergent practice. Over 10 years later, most user agents still
    27102705                  do method rewriting for <a href="#status.301" class="smpl">301</a> and <a href="#status.302" class="smpl">302</a>; therefore, this specification makes that behavior conformant when the original request is POST.
     
    27142709            </p>
    27152710            <div class="note" id="rfc.section.6.4.p.5">
    2716                <p><b>Note:</b> An earlier version of this specification recommended a maximum of five redirections (<a href="#RFC2068" id="rfc.xref.RFC2068.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>, <a href="http://tools.ietf.org/html/rfc2068#section-10.3">Section 10.3</a>). Content developers need to be aware that some clients might implement such a fixed limitation.
     2711               <p><b>Note:</b> An earlier version of this specification recommended a maximum of five redirections (<a href="#RFC2068" id="rfc.xref.RFC2068.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>, <a href="https://tools.ietf.org/html/rfc2068#section-10.3">Section 10.3</a>). Content developers need to be aware that some clients might implement such a fixed limitation.
    27172712               </p>
    27182713            </div>
    27192714            <div id="status.300">
    2720                <div id="rfc.iref.70"></div>
     2715               <div id="rfc.iref.3.2"></div>
    27212716               <h3 id="rfc.section.6.4.1"><a href="#rfc.section.6.4.1">6.4.1</a>&nbsp;<a href="#status.300">300 Multiple Choices</a></h3>
    27222717               <p id="rfc.section.6.4.1.p.1">The <dfn>300 (Multiple Choices)</dfn> status code indicates that the <a href="#resources" class="smpl">target resource</a> has more than one representation, each with its own more specific identifier, and information about the alternatives is being
     
    27432738            </div>
    27442739            <div id="status.301">
    2745                <div id="rfc.iref.70"></div>
     2740               <div id="rfc.iref.3.3"></div>
    27462741               <h3 id="rfc.section.6.4.2"><a href="#rfc.section.6.4.2">6.4.2</a>&nbsp;<a href="#status.301">301 Moved Permanently</a></h3>
    27472742               <p id="rfc.section.6.4.2.p.1">The <dfn>301 (Moved Permanently)</dfn> status code indicates that the <a href="#resources" class="smpl">target resource</a> has been assigned a new permanent URI and any future references to this resource ought to use one of the enclosed URIs. Clients
     
    27612756            </div>
    27622757            <div id="status.302">
    2763                <div id="rfc.iref.70"></div>
     2758               <div id="rfc.iref.3.4"></div>
    27642759               <h3 id="rfc.section.6.4.3"><a href="#rfc.section.6.4.3">6.4.3</a>&nbsp;<a href="#status.302">302 Found</a></h3>
    27652760               <p id="rfc.section.6.4.3.p.1">The <dfn>302 (Found)</dfn> status code indicates that the target resource resides temporarily under a different URI. Since the redirection might be altered
     
    27752770            </div>
    27762771            <div id="status.303">
    2777                <div id="rfc.iref.70"></div>
     2772               <div id="rfc.iref.3.5"></div>
    27782773               <h3 id="rfc.section.6.4.4"><a href="#rfc.section.6.4.4">6.4.4</a>&nbsp;<a href="#status.303">303 See Other</a></h3>
    27792774               <p id="rfc.section.6.4.4.p.1">The <dfn>303 (See Other)</dfn> status code indicates that the server is redirecting the user agent to a different resource, as indicated by a URI in the <a href="#header.location" class="smpl">Location</a> header field, that is intended to provide an indirect response to the original request. In order to satisfy the original request,
     
    27962791            </div>
    27972792            <div id="status.305">
    2798                <div id="rfc.iref.70"></div>
     2793               <div id="rfc.iref.3.6"></div>
    27992794               <h3 id="rfc.section.6.4.5"><a href="#rfc.section.6.4.5">6.4.5</a>&nbsp;<a href="#status.305">305 Use Proxy</a></h3>
    28002795               <p id="rfc.section.6.4.5.p.1">The <dfn>305 (Use Proxy)</dfn> status code was defined in a previous version of this specification and is now deprecated (<a href="#changes.from.rfc.2616" title="Changes from RFC 2616">Appendix&nbsp;B</a>).
     
    28022797            </div>
    28032798            <div id="status.306">
    2804                <div id="rfc.iref.70"></div>
     2799               <div id="rfc.iref.3.7"></div>
    28052800               <h3 id="rfc.section.6.4.6"><a href="#rfc.section.6.4.6">6.4.6</a>&nbsp;<a href="#status.306">306 (Unused)</a></h3>
    28062801               <p id="rfc.section.6.4.6.p.1">The 306 status code was defined in a previous version of this specification, is no longer used, and the code is reserved.</p>
    28072802            </div>
    28082803            <div id="status.307">
    2809                <div id="rfc.iref.70"></div>
     2804               <div id="rfc.iref.3.8"></div>
    28102805               <h3 id="rfc.section.6.4.7"><a href="#rfc.section.6.4.7">6.4.7</a>&nbsp;<a href="#status.307">307 Temporary Redirect</a></h3>
    28112806               <p id="rfc.section.6.4.7.p.1">The <dfn>307 (Temporary Redirect)</dfn> status code indicates that the <a href="#resources" class="smpl">target resource</a> resides temporarily under a different URI and the user agent <em class="bcp14">MUST NOT</em> change the request method if it performs an automatic redirection to that URI. Since the redirection can change over time,
     
    28252820         <div id="status.4xx">
    28262821            <h2 id="rfc.section.6.5"><a href="#rfc.section.6.5">6.5</a>&nbsp;<a href="#status.4xx">Client Error 4xx</a></h2>
    2827             <div id="rfc.iref.70"></div>
     2822            <div id="rfc.iref.4.1"></div>
    28282823            <div id="rfc.iref.s.6"></div>
    28292824            <p id="rfc.section.6.5.p.1">The <dfn>4xx (Client Error)</dfn> class of status code indicates that the client seems to have erred. Except when responding to a HEAD request, the server <em class="bcp14">SHOULD</em> send a representation containing an explanation of the error situation, and whether it is a temporary or permanent condition.
     
    28312826            </p>
    28322827            <div id="status.400">
    2833                <div id="rfc.iref.71"></div>
     2828               <div id="rfc.iref.4.2"></div>
    28342829               <h3 id="rfc.section.6.5.1"><a href="#rfc.section.6.5.1">6.5.1</a>&nbsp;<a href="#status.400">400 Bad Request</a></h3>
    28352830               <p id="rfc.section.6.5.1.p.1">The <dfn>400 (Bad Request)</dfn> status code indicates that the server cannot or will not process the request due to something which is perceived to be a client
     
    28382833            </div>
    28392834            <div id="status.402">
    2840                <div id="rfc.iref.71"></div>
     2835               <div id="rfc.iref.4.3"></div>
    28412836               <h3 id="rfc.section.6.5.2"><a href="#rfc.section.6.5.2">6.5.2</a>&nbsp;<a href="#status.402">402 Payment Required</a></h3>
    28422837               <p id="rfc.section.6.5.2.p.1">The <dfn>402 (Payment Required)</dfn> status code is reserved for future use.
     
    28442839            </div>
    28452840            <div id="status.403">
    2846                <div id="rfc.iref.71"></div>
     2841               <div id="rfc.iref.4.4"></div>
    28472842               <h3 id="rfc.section.6.5.3"><a href="#rfc.section.6.5.3">6.5.3</a>&nbsp;<a href="#status.403">403 Forbidden</a></h3>
    28482843               <p id="rfc.section.6.5.3.p.1">The <dfn>403 (Forbidden)</dfn> status code indicates that the server understood the request but refuses to authorize it. A server that wishes to make public
     
    28552850            </div>
    28562851            <div id="status.404">
    2857                <div id="rfc.iref.71"></div>
     2852               <div id="rfc.iref.4.5"></div>
    28582853               <h3 id="rfc.section.6.5.4"><a href="#rfc.section.6.5.4">6.5.4</a>&nbsp;<a href="#status.404">404 Not Found</a></h3>
    28592854               <p id="rfc.section.6.5.4.p.1">The <dfn>404 (Not Found)</dfn> status code indicates that the origin server did not find a current representation for the <a href="#resources" class="smpl">target resource</a> or is not willing to disclose that one exists. A 404 status code does not indicate whether this lack of representation is
     
    28662861            </div>
    28672862            <div id="status.405">
    2868                <div id="rfc.iref.71"></div>
     2863               <div id="rfc.iref.4.6"></div>
    28692864               <h3 id="rfc.section.6.5.5"><a href="#rfc.section.6.5.5">6.5.5</a>&nbsp;<a href="#status.405">405 Method Not Allowed</a></h3>
    28702865               <p id="rfc.section.6.5.5.p.1">The <dfn>405 (Method Not Allowed)</dfn> status code indicates that the method received in the request-line is known by the origin server but not supported by the <a href="#resources" class="smpl">target resource</a>. The origin server <em class="bcp14">MUST</em> generate an <a href="#header.allow" class="smpl">Allow</a> header field in a 405 response containing a list of the target resource's currently supported methods.
     
    28752870            </div>
    28762871            <div id="status.406">
    2877                <div id="rfc.iref.71"></div>
     2872               <div id="rfc.iref.4.7"></div>
    28782873               <h3 id="rfc.section.6.5.6"><a href="#rfc.section.6.5.6">6.5.6</a>&nbsp;<a href="#status.406">406 Not Acceptable</a></h3>
    28792874               <p id="rfc.section.6.5.6.p.1">The <dfn>406 (Not Acceptable)</dfn> status code indicates that the <a href="#resources" class="smpl">target resource</a> does not have a current representation that would be acceptable to the user agent, according to the <a href="#proactive.negotiation" class="smpl">proactive negotiation</a> header fields received in the request (<a href="#request.conneg" title="Content Negotiation">Section&nbsp;5.3</a>), and the server is unwilling to supply a default representation.
     
    28852880            </div>
    28862881            <div id="status.408">
    2887                <div id="rfc.iref.71"></div>
     2882               <div id="rfc.iref.4.8"></div>
    28882883               <h3 id="rfc.section.6.5.7"><a href="#rfc.section.6.5.7">6.5.7</a>&nbsp;<a href="#status.408">408 Request Timeout</a></h3>
    28892884               <p id="rfc.section.6.5.7.p.1">The <dfn>408 (Request Timeout)</dfn> status code indicates that the server did not receive a complete request message within the time that it was prepared to wait.
     
    28932888            </div>
    28942889            <div id="status.409">
    2895                <div id="rfc.iref.71"></div>
     2890               <div id="rfc.iref.4.9"></div>
    28962891               <h3 id="rfc.section.6.5.8"><a href="#rfc.section.6.5.8">6.5.8</a>&nbsp;<a href="#status.409">409 Conflict</a></h3>
    28972892               <p id="rfc.section.6.5.8.p.1">The <dfn>409 (Conflict)</dfn> status code indicates that the request could not be completed due to a conflict with the current state of the target resource.
     
    29052900            </div>
    29062901            <div id="status.410">
    2907                <div id="rfc.iref.71"></div>
     2902               <div id="rfc.iref.4.10"></div>
    29082903               <h3 id="rfc.section.6.5.9"><a href="#rfc.section.6.5.9">6.5.9</a>&nbsp;<a href="#status.410">410 Gone</a></h3>
    29092904               <p id="rfc.section.6.5.9.p.1">The <dfn>410 (Gone)</dfn> status code indicates that access to the <a href="#resources" class="smpl">target resource</a> is no longer available at the origin server and that this condition is likely to be permanent. If the origin server does not
     
    29212916            </div>
    29222917            <div id="status.411">
    2923                <div id="rfc.iref.71"></div>
     2918               <div id="rfc.iref.4.11"></div>
    29242919               <h3 id="rfc.section.6.5.10"><a href="#rfc.section.6.5.10">6.5.10</a>&nbsp;<a href="#status.411">411 Length Required</a></h3>
    29252920               <p id="rfc.section.6.5.10.p.1">The <dfn>411 (Length Required)</dfn> status code indicates that the server refuses to accept the request without a defined <a href="p1-messaging.html#header.content-length" class="smpl">Content-Length</a> (<a href="p1-messaging.html#header.content-length" title="Content-Length">Section 3.3.2</a> of <a href="#Part1" id="rfc.xref.Part1.26"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>). The client <em class="bcp14">MAY</em> repeat the request if it adds a valid Content-Length header field containing the length of the message body in the request
     
    29282923            </div>
    29292924            <div id="status.413">
    2930                <div id="rfc.iref.71"></div>
     2925               <div id="rfc.iref.4.12"></div>
    29312926               <h3 id="rfc.section.6.5.11"><a href="#rfc.section.6.5.11">6.5.11</a>&nbsp;<a href="#status.413">413 Payload Too Large</a></h3>
    29322927               <p id="rfc.section.6.5.11.p.1">The <dfn>413 (Payload Too Large)</dfn> status code indicates that the server is refusing to process a request because the request payload is larger than the server
     
    29372932            </div>
    29382933            <div id="status.414">
    2939                <div id="rfc.iref.71"></div>
     2934               <div id="rfc.iref.4.13"></div>
    29402935               <h3 id="rfc.section.6.5.12"><a href="#rfc.section.6.5.12">6.5.12</a>&nbsp;<a href="#status.414">414 URI Too Long</a></h3>
    29412936               <p id="rfc.section.6.5.12.p.1">The <dfn>414 (URI Too Long)</dfn> status code indicates that the server is refusing to service the request because the request-target (<a href="p1-messaging.html#request-target" title="Request Target">Section 5.3</a> of <a href="#Part1" id="rfc.xref.Part1.27"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) is longer than the server is willing to interpret. This rare condition is only likely to occur when a client has improperly
     
    29492944            </div>
    29502945            <div id="status.415">
    2951                <div id="rfc.iref.71"></div>
     2946               <div id="rfc.iref.4.14"></div>
    29522947               <h3 id="rfc.section.6.5.13"><a href="#rfc.section.6.5.13">6.5.13</a>&nbsp;<a href="#status.415">415 Unsupported Media Type</a></h3>
    29532948               <p id="rfc.section.6.5.13.p.1">The <dfn>415 (Unsupported Media Type)</dfn> status code indicates that the origin server is refusing to service the request because the payload is in a format not supported
     
    29562951            </div>
    29572952            <div id="status.417">
    2958                <div id="rfc.iref.71"></div>
     2953               <div id="rfc.iref.4.15"></div>
    29592954               <h3 id="rfc.section.6.5.14"><a href="#rfc.section.6.5.14">6.5.14</a>&nbsp;<a href="#status.417">417 Expectation Failed</a></h3>
    29602955               <p id="rfc.section.6.5.14.p.1">The <dfn>417 (Expectation Failed)</dfn> status code indicates that the expectation given in the request's <a href="#header.expect" class="smpl">Expect</a> header field (<a href="#header.expect" id="rfc.xref.header.expect.3" title="Expect">Section&nbsp;5.1.1</a>) could not be met by at least one of the inbound servers.
     
    29622957            </div>
    29632958            <div id="status.426">
    2964                <div id="rfc.iref.71"></div>
     2959               <div id="rfc.iref.4.16"></div>
    29652960               <h3 id="rfc.section.6.5.15"><a href="#rfc.section.6.5.15">6.5.15</a>&nbsp;<a href="#status.426">426 Upgrade Required</a></h3>
    29662961               <p id="rfc.section.6.5.15.p.1">The <dfn>426 (Upgrade Required)</dfn> status code indicates that the server refuses to perform the request using the current protocol but might be willing to do
     
    29792974         <div id="status.5xx">
    29802975            <h2 id="rfc.section.6.6"><a href="#rfc.section.6.6">6.6</a>&nbsp;<a href="#status.5xx">Server Error 5xx</a></h2>
    2981             <div id="rfc.iref.71"></div>
     2976            <div id="rfc.iref.5.1"></div>
    29822977            <div id="rfc.iref.s.7"></div>
    29832978            <p id="rfc.section.6.6.p.1">The <dfn>5xx (Server Error)</dfn> class of status code indicates that the server is aware that it has erred or is incapable of performing the requested method.
     
    29862981            </p>
    29872982            <div id="status.500">
    2988                <div id="rfc.iref.72"></div>
     2983               <div id="rfc.iref.5.2"></div>
    29892984               <h3 id="rfc.section.6.6.1"><a href="#rfc.section.6.6.1">6.6.1</a>&nbsp;<a href="#status.500">500 Internal Server Error</a></h3>
    29902985               <p id="rfc.section.6.6.1.p.1">The <dfn>500 (Internal Server Error)</dfn> status code indicates that the server encountered an unexpected condition that prevented it from fulfilling the request.
     
    29922987            </div>
    29932988            <div id="status.501">
    2994                <div id="rfc.iref.72"></div>
     2989               <div id="rfc.iref.5.3"></div>
    29952990               <h3 id="rfc.section.6.6.2"><a href="#rfc.section.6.6.2">6.6.2</a>&nbsp;<a href="#status.501">501 Not Implemented</a></h3>
    29962991               <p id="rfc.section.6.6.2.p.1">The <dfn>501 (Not Implemented)</dfn> status code indicates that the server does not support the functionality required to fulfill the request. This is the appropriate
     
    30022997            </div>
    30032998            <div id="status.502">
    3004                <div id="rfc.iref.72"></div>
     2999               <div id="rfc.iref.5.4"></div>
    30053000               <h3 id="rfc.section.6.6.3"><a href="#rfc.section.6.6.3">6.6.3</a>&nbsp;<a href="#status.502">502 Bad Gateway</a></h3>
    30063001               <p id="rfc.section.6.6.3.p.1">The <dfn>502 (Bad Gateway)</dfn> status code indicates that the server, while acting as a gateway or proxy, received an invalid response from an inbound server
     
    30093004            </div>
    30103005            <div id="status.503">
    3011                <div id="rfc.iref.72"></div>
     3006               <div id="rfc.iref.5.5"></div>
    30123007               <h3 id="rfc.section.6.6.4"><a href="#rfc.section.6.6.4">6.6.4</a>&nbsp;<a href="#status.503">503 Service Unavailable</a></h3>
    30133008               <p id="rfc.section.6.6.4.p.1">The <dfn>503 (Service Unavailable)</dfn> status code indicates that the server is currently unable to handle the request due to a temporary overload or scheduled maintenance,
     
    30213016            </div>
    30223017            <div id="status.504">
    3023                <div id="rfc.iref.72"></div>
     3018               <div id="rfc.iref.5.6"></div>
    30243019               <h3 id="rfc.section.6.6.5"><a href="#rfc.section.6.6.5">6.6.5</a>&nbsp;<a href="#status.504">504 Gateway Timeout</a></h3>
    30253020               <p id="rfc.section.6.6.5.p.1">The <dfn>504 (Gateway Timeout)</dfn> status code indicates that the server, while acting as a gateway or proxy, did not receive a timely response from an upstream
     
    30283023            </div>
    30293024            <div id="status.505">
    3030                <div id="rfc.iref.72"></div>
     3025               <div id="rfc.iref.5.7"></div>
    30313026               <h3 id="rfc.section.6.6.6"><a href="#rfc.section.6.6.6">6.6.6</a>&nbsp;<a href="#status.505">505 HTTP Version Not Supported</a></h3>
    30323027               <p id="rfc.section.6.6.6.p.1">The <dfn>505 (HTTP Version Not Supported)</dfn> status code indicates that the server does not support, or refuses to support, the major version of HTTP that was used in
     
    31213116                  <div id="rfc.figure.u.46"></div><pre class="inline"><span id="rfc.iref.g.36"></span><span id="rfc.iref.g.37"></span><span id="rfc.iref.g.38"></span><span id="rfc.iref.g.39"></span><span id="rfc.iref.g.40"></span><span id="rfc.iref.g.41"></span><span id="rfc.iref.g.42"></span><span id="rfc.iref.g.43"></span><span id="rfc.iref.g.44"></span><span id="rfc.iref.g.45"></span><span id="rfc.iref.g.46"></span><span id="rfc.iref.g.47"></span>  <a href="#preferred.date.format" class="smpl">IMF-fixdate</a>  = <a href="#preferred.date.format" class="smpl">day-name</a> "," <a href="#imported.abnf" class="smpl">SP</a> date1 <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">GMT</a>
    31223117  ; fixed length/zone subset of the format defined in
    3123   ; <a href="http://tools.ietf.org/html/rfc5322#section-3.3">Section 3.3</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.4"><cite title="Internet Message Format">[RFC5322]</cite></a>
     3118  ; <a href="https://tools.ietf.org/html/rfc5322#section-3.3">Section 3.3</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.4"><cite title="Internet Message Format">[RFC5322]</cite></a>
    31243119 
    31253120  <a href="#preferred.date.format" class="smpl">day-name</a>     = %x4D.6F.6E ; "Mon", case-sensitive
     
    31753170  <a href="#obsolete.date.formats" class="smpl">date3</a>        = <a href="#preferred.date.format" class="smpl">month</a> <a href="#imported.abnf" class="smpl">SP</a> ( 2<a href="#imported.abnf" class="smpl">DIGIT</a> / ( <a href="#imported.abnf" class="smpl">SP</a> 1<a href="#imported.abnf" class="smpl">DIGIT</a> ))
    31763171               ; e.g., Jun  2
    3177 </pre><p id="rfc.section.7.1.1.1.p.13">HTTP-date is case sensitive. A sender <em class="bcp14">MUST NOT</em> generate additional whitespace in an HTTP-date beyond that specifically included as SP in the grammar. The semantics of <a href="#preferred.date.format" class="smpl">day-name</a>, <a href="#preferred.date.format" class="smpl">day</a>, <a href="#preferred.date.format" class="smpl">month</a>, <a href="#preferred.date.format" class="smpl">year</a>, and <a href="#preferred.date.format" class="smpl">time-of-day</a> are the same as those defined for the Internet Message Format constructs with the corresponding name (<a href="#RFC5322" id="rfc.xref.RFC5322.5"><cite title="Internet Message Format">[RFC5322]</cite></a>, <a href="http://tools.ietf.org/html/rfc5322#section-3.3">Section 3.3</a>).
     3172</pre><p id="rfc.section.7.1.1.1.p.13">HTTP-date is case sensitive. A sender <em class="bcp14">MUST NOT</em> generate additional whitespace in an HTTP-date beyond that specifically included as SP in the grammar. The semantics of <a href="#preferred.date.format" class="smpl">day-name</a>, <a href="#preferred.date.format" class="smpl">day</a>, <a href="#preferred.date.format" class="smpl">month</a>, <a href="#preferred.date.format" class="smpl">year</a>, and <a href="#preferred.date.format" class="smpl">time-of-day</a> are the same as those defined for the Internet Message Format constructs with the corresponding name (<a href="#RFC5322" id="rfc.xref.RFC5322.5"><cite title="Internet Message Format">[RFC5322]</cite></a>, <a href="https://tools.ietf.org/html/rfc5322#section-3.3">Section 3.3</a>).
    31783173                  </p>
    31793174                  <p id="rfc.section.7.1.1.1.p.14">Recipients of a timestamp value in rfc850-date format, which uses a two-digit year, <em class="bcp14">MUST</em> interpret a timestamp that appears to be more than 50 years in the future as representing the most recent year in the past
     
    31943189                  <h4 id="rfc.section.7.1.1.2"><a href="#rfc.section.7.1.1.2">7.1.1.2</a>&nbsp;<a href="#header.date">Date</a></h4>
    31953190                  <p id="rfc.section.7.1.1.2.p.1">The "Date" header field represents the date and time at which the message was originated, having the same semantics as the
    3196                      Origination Date Field (orig-date) defined in <a href="http://tools.ietf.org/html/rfc5322#section-3.6.1">Section 3.6.1</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.6"><cite title="Internet Message Format">[RFC5322]</cite></a>. The field value is an HTTP-date, as defined in <a href="#http.date" title="Date/Time Formats">Section&nbsp;7.1.1.1</a>.
     3191                     Origination Date Field (orig-date) defined in <a href="https://tools.ietf.org/html/rfc5322#section-3.6.1">Section 3.6.1</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.6"><cite title="Internet Message Format">[RFC5322]</cite></a>. The field value is an HTTP-date, as defined in <a href="#http.date" title="Date/Time Formats">Section&nbsp;7.1.1.1</a>.
    31973192                  </p>
    31983193                  <div id="rfc.figure.u.50"></div><pre class="inline"><span id="rfc.iref.g.51"></span>  <a href="#header.date" class="smpl">Date</a> = <a href="#http.date" class="smpl">HTTP-date</a>
     
    32223217               </p>
    32233218               <div id="rfc.figure.u.52"></div><pre class="inline"><span id="rfc.iref.g.52"></span>  <a href="#header.location" class="smpl">Location</a> = <a href="#imported.abnf" class="smpl">URI-reference</a>
    3224 </pre><p id="rfc.section.7.1.2.p.3">The field value consists of a single URI-reference. When it has the form of a relative reference (<a href="#RFC3986" id="rfc.xref.RFC3986.2"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-4.2">Section 4.2</a>), the final value is computed by resolving it against the effective request URI (<a href="#RFC3986" id="rfc.xref.RFC3986.3"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-5">Section 5</a>).
     3219</pre><p id="rfc.section.7.1.2.p.3">The field value consists of a single URI-reference. When it has the form of a relative reference (<a href="#RFC3986" id="rfc.xref.RFC3986.2"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="https://tools.ietf.org/html/rfc3986#section-4.2">Section 4.2</a>), the final value is computed by resolving it against the effective request URI (<a href="#RFC3986" id="rfc.xref.RFC3986.3"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="https://tools.ietf.org/html/rfc3986#section-5">Section 5</a>).
    32253220               </p>
    32263221               <p id="rfc.section.7.1.2.p.4">For <a href="#status.201" class="smpl">201 (Created)</a> responses, the Location value refers to the primary resource created by the request. For <a href="#status.3xx" class="smpl">3xx (Redirection)</a> responses, the Location value refers to the preferred target resource for automatically redirecting the request.
     
    34533448                  <li>Pointer to specification text</li>
    34543449               </ul>
    3455                <p id="rfc.section.8.1.1.p.2">Values to be added to this name space require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
     3450               <p id="rfc.section.8.1.1.p.2">Values to be added to this name space require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="https://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
    34563451               </p>
    34573452            </div>
     
    35593554            <p id="rfc.section.8.2.p.1">The HTTP Status Code Registry defines the name space for the response status-code token (<a href="#status.codes" title="Response Status Codes">Section&nbsp;6</a>). The status code registry is maintained at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt;.
    35603555            </p>
    3561             <p id="rfc.section.8.2.p.2">This Section replaces the registration procedure for HTTP Status Codes previously defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.1"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>.
     3556            <p id="rfc.section.8.2.p.2">This Section replaces the registration procedure for HTTP Status Codes previously defined in <a href="https://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.1"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>.
    35623557            </p>
    35633558            <div id="status.code.registry.procedure">
     
    35703565                  <li>Pointer to specification text</li>
    35713566               </ul>
    3572                <p id="rfc.section.8.2.1.p.2">Values to be added to the HTTP status code name space require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.2"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
     3567               <p id="rfc.section.8.2.1.p.2">Values to be added to the HTTP status code name space require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.2"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="https://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
    35733568               </p>
    35743569            </div>
     
    40964091               <p id="rfc.section.8.4.1.p.2">Names of content codings <em class="bcp14">MUST NOT</em> overlap with names of transfer codings (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 4</a> of <a href="#Part1" id="rfc.xref.Part1.40"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>), unless the encoding transformation is identical (as is the case for the compression codings defined in <a href="p1-messaging.html#compression.codings" title="Compression Codings">Section 4.2</a> of <a href="#Part1" id="rfc.xref.Part1.41"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>).
    40974092               </p>
    4098                <p id="rfc.section.8.4.1.p.3">Values to be added to this name space require IETF Review (see <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.3"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>), and <em class="bcp14">MUST</em> conform to the purpose of content coding defined in this section.
     4093               <p id="rfc.section.8.4.1.p.3">Values to be added to this name space require IETF Review (see <a href="https://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a> of <a href="#RFC5226" id="rfc.xref.RFC5226.3"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>), and <em class="bcp14">MUST</em> conform to the purpose of content coding defined in this section.
    40994094               </p>
    41004095            </div>
     
    42324227         <tr>
    42334228            <td class="reference"><b id="Part1">[Part1]</b></td>
    4234             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-25">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-25 (work in progress), November&nbsp;2013.
     4229            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-25">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-25 (work in progress), November&nbsp;2013.
    42354230            </td>
    42364231         </tr>
    42374232         <tr>
    42384233            <td class="reference"><b id="Part4">[Part4]</b></td>
    4239             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-25">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-25 (work in progress), November&nbsp;2013.
     4234            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-25">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-25 (work in progress), November&nbsp;2013.
    42404235            </td>
    42414236         </tr>
    42424237         <tr>
    42434238            <td class="reference"><b id="Part5">[Part5]</b></td>
    4244             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-25">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-25 (work in progress), November&nbsp;2013.
     4239            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p5-range-25">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-25 (work in progress), November&nbsp;2013.
    42454240            </td>
    42464241         </tr>
    42474242         <tr>
    42484243            <td class="reference"><b id="Part6">[Part6]</b></td>
    4249             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-25">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-25 (work in progress), November&nbsp;2013.
     4244            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-25">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-25 (work in progress), November&nbsp;2013.
    42504245            </td>
    42514246         </tr>
    42524247         <tr>
    42534248            <td class="reference"><b id="Part7">[Part7]</b></td>
    4254             <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-25">Hypertext Transfer Protocol (HTTP/1.1): Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-25 (work in progress), November&nbsp;2013.
     4249            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-25">Hypertext Transfer Protocol (HTTP/1.1): Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-25 (work in progress), November&nbsp;2013.
    42554250            </td>
    42564251         </tr>
    42574252         <tr>
    42584253            <td class="reference"><b id="RFC2045">[RFC2045]</b></td>
    4259             <td class="top"><a href="mailto:ned@innosoft.com" title="Innosoft International, Inc.">Freed, N.</a> and <a href="mailto:nsb@nsb.fv.com" title="First Virtual Holdings">N. Borenstein</a>, “<a href="http://tools.ietf.org/html/rfc2045">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</a>”, RFC&nbsp;2045, November&nbsp;1996.
     4254            <td class="top"><a href="mailto:ned@innosoft.com" title="Innosoft International, Inc.">Freed, N.</a> and <a href="mailto:nsb@nsb.fv.com" title="First Virtual Holdings">N. Borenstein</a>, “<a href="https://tools.ietf.org/html/rfc2045">Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies</a>”, RFC&nbsp;2045, November&nbsp;1996.
    42604255            </td>
    42614256         </tr>
    42624257         <tr>
    42634258            <td class="reference"><b id="RFC2046">[RFC2046]</b></td>
    4264             <td class="top"><a href="mailto:ned@innosoft.com" title="Innosoft International, Inc.">Freed, N.</a> and <a href="mailto:nsb@nsb.fv.com" title="First Virtual Holdings">N. Borenstein</a>, “<a href="http://tools.ietf.org/html/rfc2046">Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</a>”, RFC&nbsp;2046, November&nbsp;1996.
     4259            <td class="top"><a href="mailto:ned@innosoft.com" title="Innosoft International, Inc.">Freed, N.</a> and <a href="mailto:nsb@nsb.fv.com" title="First Virtual Holdings">N. Borenstein</a>, “<a href="https://tools.ietf.org/html/rfc2046">Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types</a>”, RFC&nbsp;2046, November&nbsp;1996.
    42654260            </td>
    42664261         </tr>
    42674262         <tr>
    42684263            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
    4269             <td class="top"><a href="mailto:sob@harvard.edu" title="Harvard University">Bradner, S.</a>, “<a href="http://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP&nbsp;14, RFC&nbsp;2119, March&nbsp;1997.
     4264            <td class="top"><a href="mailto:sob@harvard.edu" title="Harvard University">Bradner, S.</a>, “<a href="https://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP&nbsp;14, RFC&nbsp;2119, March&nbsp;1997.
    42704265            </td>
    42714266         </tr>
    42724267         <tr>
    42734268            <td class="reference"><b id="RFC3986">[RFC3986]</b></td>
    4274             <td class="top"><a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R.</a>, and <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">L. Masinter</a>, “<a href="http://tools.ietf.org/html/rfc3986">Uniform Resource Identifier (URI): Generic Syntax</a>”, STD&nbsp;66, RFC&nbsp;3986, January&nbsp;2005.
     4269            <td class="top"><a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R.</a>, and <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">L. Masinter</a>, “<a href="https://tools.ietf.org/html/rfc3986">Uniform Resource Identifier (URI): Generic Syntax</a>”, STD&nbsp;66, RFC&nbsp;3986, January&nbsp;2005.
    42754270            </td>
    42764271         </tr>
    42774272         <tr>
    42784273            <td class="reference"><b id="RFC4647">[RFC4647]</b></td>
    4279             <td class="top"><a href="mailto:addison@inter-locale.com" title="Yahoo! Inc.">Phillips, A., Ed.</a> and <a href="mailto:mark.davis@macchiato.com" title="Google">M. Davis, Ed.</a>, “<a href="http://tools.ietf.org/html/rfc4647">Matching of Language Tags</a>”, BCP&nbsp;47, RFC&nbsp;4647, September&nbsp;2006.
     4274            <td class="top"><a href="mailto:addison@inter-locale.com" title="Yahoo! Inc.">Phillips, A., Ed.</a> and <a href="mailto:mark.davis@macchiato.com" title="Google">M. Davis, Ed.</a>, “<a href="https://tools.ietf.org/html/rfc4647">Matching of Language Tags</a>”, BCP&nbsp;47, RFC&nbsp;4647, September&nbsp;2006.
    42804275            </td>
    42814276         </tr>
    42824277         <tr>
    42834278            <td class="reference"><b id="RFC5234">[RFC5234]</b></td>
    4284             <td class="top"><a href="mailto:dcrocker@bbiw.net" title="Brandenburg InternetWorking">Crocker, D., Ed.</a> and <a href="mailto:paul.overell@thus.net" title="THUS plc.">P. Overell</a>, “<a href="http://tools.ietf.org/html/rfc5234">Augmented BNF for Syntax Specifications: ABNF</a>”, STD&nbsp;68, RFC&nbsp;5234, January&nbsp;2008.
     4279            <td class="top"><a href="mailto:dcrocker@bbiw.net" title="Brandenburg InternetWorking">Crocker, D., Ed.</a> and <a href="mailto:paul.overell@thus.net" title="THUS plc.">P. Overell</a>, “<a href="https://tools.ietf.org/html/rfc5234">Augmented BNF for Syntax Specifications: ABNF</a>”, STD&nbsp;68, RFC&nbsp;5234, January&nbsp;2008.
    42854280            </td>
    42864281         </tr>
    42874282         <tr>
    42884283            <td class="reference"><b id="RFC5646">[RFC5646]</b></td>
    4289             <td class="top"><a href="mailto:addison@inter-locale.com" title="Lab126">Phillips, A., Ed.</a> and <a href="mailto:mark.davis@google.com" title="Google">M. Davis, Ed.</a>, “<a href="http://tools.ietf.org/html/rfc5646">Tags for Identifying Languages</a>”, BCP&nbsp;47, RFC&nbsp;5646, September&nbsp;2009.
     4284            <td class="top"><a href="mailto:addison@inter-locale.com" title="Lab126">Phillips, A., Ed.</a> and <a href="mailto:mark.davis@google.com" title="Google">M. Davis, Ed.</a>, “<a href="https://tools.ietf.org/html/rfc5646">Tags for Identifying Languages</a>”, BCP&nbsp;47, RFC&nbsp;5646, September&nbsp;2009.
    42904285            </td>
    42914286         </tr>
    42924287         <tr>
    42934288            <td class="reference"><b id="RFC6365">[RFC6365]</b></td>
    4294             <td class="top">Hoffman, P. and J. Klensin, “<a href="http://tools.ietf.org/html/rfc6365">Terminology Used in Internationalization in the IETF</a>”, BCP&nbsp;166, RFC&nbsp;6365, September&nbsp;2011.
     4289            <td class="top">Hoffman, P. and J. Klensin, “<a href="https://tools.ietf.org/html/rfc6365">Terminology Used in Internationalization in the IETF</a>”, BCP&nbsp;166, RFC&nbsp;6365, September&nbsp;2011.
    42954290            </td>
    42964291         </tr>
     
    43014296         <tr>
    43024297            <td class="reference"><b id="BCP13">[BCP13]</b></td>
    4303             <td class="top"><a href="mailto:ned+ietf@mrochek.com" title="Oracle">Freed, N.</a>, <a href="mailto:john+ietf@jck.com">Klensin, J.</a>, and <a href="mailto:tony+mtsuffix@maillennium.att.com" title="AT&amp;T Laboratories">T. Hansen</a>, “<a href="http://tools.ietf.org/html/rfc6838">Media Type Specifications and Registration Procedures</a>”, BCP&nbsp;13, RFC&nbsp;6838, January&nbsp;2013.
     4298            <td class="top"><a href="mailto:ned+ietf@mrochek.com" title="Oracle">Freed, N.</a>, <a href="mailto:john+ietf@jck.com">Klensin, J.</a>, and <a href="mailto:tony+mtsuffix@maillennium.att.com" title="AT&amp;T Laboratories">T. Hansen</a>, “<a href="https://tools.ietf.org/html/rfc6838">Media Type Specifications and Registration Procedures</a>”, BCP&nbsp;13, RFC&nbsp;6838, January&nbsp;2013.
    43044299            </td>
    43054300         </tr>
    43064301         <tr>
    43074302            <td class="reference"><b id="BCP178">[BCP178]</b></td>
    4308             <td class="top">Saint-Andre, P., Crocker, D., and M. Nottingham, “<a href="http://tools.ietf.org/html/rfc6648">Deprecating the "X-" Prefix and Similar Constructs in Application Protocols</a>”, BCP&nbsp;178, RFC&nbsp;6648, June&nbsp;2012.
     4303            <td class="top">Saint-Andre, P., Crocker, D., and M. Nottingham, “<a href="https://tools.ietf.org/html/rfc6648">Deprecating the "X-" Prefix and Similar Constructs in Application Protocols</a>”, BCP&nbsp;178, RFC&nbsp;6648, June&nbsp;2012.
    43094304            </td>
    43104305         </tr>
    43114306         <tr>
    43124307            <td class="reference"><b id="BCP90">[BCP90]</b></td>
    4313             <td class="top"><a href="mailto:GK-IETF@ninebynine.org" title="Nine by Nine">Klyne, G.</a>, <a href="mailto:mnot@pobox.com" title="BEA Systems">Nottingham, M.</a>, and <a href="mailto:JeffMogul@acm.org" title="HP Labs">J. Mogul</a>, “<a href="http://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP&nbsp;90, RFC&nbsp;3864, September&nbsp;2004.
     4308            <td class="top"><a href="mailto:GK-IETF@ninebynine.org" title="Nine by Nine">Klyne, G.</a>, <a href="mailto:mnot@pobox.com" title="BEA Systems">Nottingham, M.</a>, and <a href="mailto:JeffMogul@acm.org" title="HP Labs">J. Mogul</a>, “<a href="https://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP&nbsp;90, RFC&nbsp;3864, September&nbsp;2004.
    43144309            </td>
    43154310         </tr>
     
    43214316         <tr>
    43224317            <td class="reference"><b id="RFC1945">[RFC1945]</b></td>
    4323             <td class="top"><a href="mailto:timbl@w3.org" title="MIT, Laboratory for Computer Science">Berners-Lee, T.</a>, <a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.</a>, and <a href="mailto:frystyk@w3.org" title="W3 Consortium, MIT Laboratory for Computer Science">H. Nielsen</a>, “<a href="http://tools.ietf.org/html/rfc1945">Hypertext Transfer Protocol -- HTTP/1.0</a>”, RFC&nbsp;1945, May&nbsp;1996.
     4318            <td class="top"><a href="mailto:timbl@w3.org" title="MIT, Laboratory for Computer Science">Berners-Lee, T.</a>, <a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.</a>, and <a href="mailto:frystyk@w3.org" title="W3 Consortium, MIT Laboratory for Computer Science">H. Nielsen</a>, “<a href="https://tools.ietf.org/html/rfc1945">Hypertext Transfer Protocol -- HTTP/1.0</a>”, RFC&nbsp;1945, May&nbsp;1996.
    43244319            </td>
    43254320         </tr>
    43264321         <tr>
    43274322            <td class="reference"><b id="RFC2049">[RFC2049]</b></td>
    4328             <td class="top"><a href="mailto:ned@innosoft.com" title="Innosoft International, Inc.">Freed, N.</a> and <a href="mailto:nsb@nsb.fv.com" title="First Virtual Holdings">N. Borenstein</a>, “<a href="http://tools.ietf.org/html/rfc2049">Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples</a>”, RFC&nbsp;2049, November&nbsp;1996.
     4323            <td class="top"><a href="mailto:ned@innosoft.com" title="Innosoft International, Inc.">Freed, N.</a> and <a href="mailto:nsb@nsb.fv.com" title="First Virtual Holdings">N. Borenstein</a>, “<a href="https://tools.ietf.org/html/rfc2049">Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples</a>”, RFC&nbsp;2049, November&nbsp;1996.
    43294324            </td>
    43304325         </tr>
    43314326         <tr>
    43324327            <td class="reference"><b id="RFC2068">[RFC2068]</b></td>
    4333             <td class="top"><a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="MIT Laboratory for Computer Science">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com" title="Digital Equipment Corporation, Western Research Laboratory">Mogul, J.</a>, <a href="mailto:frystyk@w3.org" title="MIT Laboratory for Computer Science">Nielsen, H.</a>, and <a href="mailto:timbl@w3.org" title="MIT Laboratory for Computer Science">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2068">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2068, January&nbsp;1997.
     4328            <td class="top"><a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="MIT Laboratory for Computer Science">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com" title="Digital Equipment Corporation, Western Research Laboratory">Mogul, J.</a>, <a href="mailto:frystyk@w3.org" title="MIT Laboratory for Computer Science">Nielsen, H.</a>, and <a href="mailto:timbl@w3.org" title="MIT Laboratory for Computer Science">T. Berners-Lee</a>, “<a href="https://tools.ietf.org/html/rfc2068">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2068, January&nbsp;1997.
    43344329            </td>
    43354330         </tr>
    43364331         <tr>
    43374332            <td class="reference"><b id="RFC2295">[RFC2295]</b></td>
    4338             <td class="top"><a href="mailto:koen@win.tue.nl" title="Technische Universiteit Eindhoven">Holtman, K.</a> and <a href="mailto:mutz@hpl.hp.com" title="Hewlett-Packard Company">A. Mutz</a>, “<a href="http://tools.ietf.org/html/rfc2295">Transparent Content Negotiation in HTTP</a>”, RFC&nbsp;2295, March&nbsp;1998.
     4333            <td class="top"><a href="mailto:koen@win.tue.nl" title="Technische Universiteit Eindhoven">Holtman, K.</a> and <a href="mailto:mutz@hpl.hp.com" title="Hewlett-Packard Company">A. Mutz</a>, “<a href="https://tools.ietf.org/html/rfc2295">Transparent Content Negotiation in HTTP</a>”, RFC&nbsp;2295, March&nbsp;1998.
    43394334            </td>
    43404335         </tr>
    43414336         <tr>
    43424337            <td class="reference"><b id="RFC2388">[RFC2388]</b></td>
    4343             <td class="top"><a href="mailto:masinter@parc.xerox.com" title="Xerox Palo Alto Research Center">Masinter, L.</a>, “<a href="http://tools.ietf.org/html/rfc2388">Returning Values from Forms: multipart/form-data</a>”, RFC&nbsp;2388, August&nbsp;1998.
     4338            <td class="top"><a href="mailto:masinter@parc.xerox.com" title="Xerox Palo Alto Research Center">Masinter, L.</a>, “<a href="https://tools.ietf.org/html/rfc2388">Returning Values from Forms: multipart/form-data</a>”, RFC&nbsp;2388, August&nbsp;1998.
    43444339            </td>
    43454340         </tr>
    43464341         <tr>
    43474342            <td class="reference"><b id="RFC2557">[RFC2557]</b></td>
    4348             <td class="top"><a href="mailto:jpalme@dsv.su.se" title="Stockholm University and KTH">Palme, F.</a>, <a href="mailto:alexhop@microsoft.com" title="Microsoft Corporation">Hopmann, A.</a>, <a href="mailto:Shelness@lotus.com" title="Lotus Development Corporation">Shelness, N.</a>, and <a href="mailto:stef@nma.com">E. Stefferud</a>, “<a href="http://tools.ietf.org/html/rfc2557">MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)</a>”, RFC&nbsp;2557, March&nbsp;1999.
     4343            <td class="top"><a href="mailto:jpalme@dsv.su.se" title="Stockholm University and KTH">Palme, F.</a>, <a href="mailto:alexhop@microsoft.com" title="Microsoft Corporation">Hopmann, A.</a>, <a href="mailto:Shelness@lotus.com" title="Lotus Development Corporation">Shelness, N.</a>, and <a href="mailto:stef@nma.com">E. Stefferud</a>, “<a href="https://tools.ietf.org/html/rfc2557">MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)</a>”, RFC&nbsp;2557, March&nbsp;1999.
    43494344            </td>
    43504345         </tr>
    43514346         <tr>
    43524347            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
    4353             <td class="top"><a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="W3C">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com" title="Compaq Computer Corporation">Mogul, J.</a>, <a href="mailto:frystyk@w3.org" title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a href="mailto:masinter@parc.xerox.com" title="Xerox Corporation">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, and <a href="mailto:timbl@w3.org" 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.
     4348            <td class="top"><a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="W3C">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com" title="Compaq Computer Corporation">Mogul, J.</a>, <a href="mailto:frystyk@w3.org" title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a href="mailto:masinter@parc.xerox.com" title="Xerox Corporation">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, and <a href="mailto:timbl@w3.org" title="W3C">T. Berners-Lee</a>, “<a href="https://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
    43544349            </td>
    43554350         </tr>
    43564351         <tr>
    43574352            <td class="reference"><b id="RFC2774">[RFC2774]</b></td>
    4358             <td class="top"><a href="mailto:frystyk@w3.org">Frystyk, H.</a>, <a href="mailto:paulle@microsoft.com">Leach, P.</a>, and <a href="mailto:lawrence@agranat.com">S. Lawrence</a>, “<a href="http://tools.ietf.org/html/rfc2774">An HTTP Extension Framework</a>”, RFC&nbsp;2774, February&nbsp;2000.
     4353            <td class="top"><a href="mailto:frystyk@w3.org">Frystyk, H.</a>, <a href="mailto:paulle@microsoft.com">Leach, P.</a>, and <a href="mailto:lawrence@agranat.com">S. Lawrence</a>, “<a href="https://tools.ietf.org/html/rfc2774">An HTTP Extension Framework</a>”, RFC&nbsp;2774, February&nbsp;2000.
    43594354            </td>
    43604355         </tr>
    43614356         <tr>
    43624357            <td class="reference"><b id="RFC2817">[RFC2817]</b></td>
    4363             <td class="top"><a href="mailto:rohit@4K-associates.com" title="4K Associates / UC Irvine">Khare, R.</a> and <a href="mailto:lawrence@agranat.com" title="Agranat Systems, Inc.">S. Lawrence</a>, “<a href="http://tools.ietf.org/html/rfc2817">Upgrading to TLS Within HTTP/1.1</a>”, RFC&nbsp;2817, May&nbsp;2000.
     4358            <td class="top"><a href="mailto:rohit@4K-associates.com" title="4K Associates / UC Irvine">Khare, R.</a> and <a href="mailto:lawrence@agranat.com" title="Agranat Systems, Inc.">S. Lawrence</a>, “<a href="https://tools.ietf.org/html/rfc2817">Upgrading to TLS Within HTTP/1.1</a>”, RFC&nbsp;2817, May&nbsp;2000.
    43644359            </td>
    43654360         </tr>
    43664361         <tr>
    43674362            <td class="reference"><b id="RFC2978">[RFC2978]</b></td>
    4368             <td class="top">Freed, N. and J. Postel, “<a href="http://tools.ietf.org/html/rfc2978">IANA Charset Registration Procedures</a>”, BCP&nbsp;19, RFC&nbsp;2978, October&nbsp;2000.
     4363            <td class="top">Freed, N. and J. Postel, “<a href="https://tools.ietf.org/html/rfc2978">IANA Charset Registration Procedures</a>”, BCP&nbsp;19, RFC&nbsp;2978, October&nbsp;2000.
    43694364            </td>
    43704365         </tr>
    43714366         <tr>
    43724367            <td class="reference"><b id="RFC5226">[RFC5226]</b></td>
    4373             <td class="top"><a href="mailto:narten@us.ibm.com" title="IBM">Narten, T.</a> and <a href="mailto:Harald@Alvestrand.no" title="Google">H. Alvestrand</a>, “<a href="http://tools.ietf.org/html/rfc5226">Guidelines for Writing an IANA Considerations Section in RFCs</a>”, BCP&nbsp;26, RFC&nbsp;5226, May&nbsp;2008.
     4368            <td class="top"><a href="mailto:narten@us.ibm.com" title="IBM">Narten, T.</a> and <a href="mailto:Harald@Alvestrand.no" title="Google">H. Alvestrand</a>, “<a href="https://tools.ietf.org/html/rfc5226">Guidelines for Writing an IANA Considerations Section in RFCs</a>”, BCP&nbsp;26, RFC&nbsp;5226, May&nbsp;2008.
    43744369            </td>
    43754370         </tr>
    43764371         <tr>
    43774372            <td class="reference"><b id="RFC5322">[RFC5322]</b></td>
    4378             <td class="top">Resnick, P., “<a href="http://tools.ietf.org/html/rfc5322">Internet Message Format</a>”, RFC&nbsp;5322, October&nbsp;2008.
     4373            <td class="top">Resnick, P., “<a href="https://tools.ietf.org/html/rfc5322">Internet Message Format</a>”, RFC&nbsp;5322, October&nbsp;2008.
    43794374            </td>
    43804375         </tr>
    43814376         <tr>
    43824377            <td class="reference"><b id="RFC5789">[RFC5789]</b></td>
    4383             <td class="top">Dusseault, L. and J. Snell, “<a href="http://tools.ietf.org/html/rfc5789">PATCH Method for HTTP</a>”, RFC&nbsp;5789, March&nbsp;2010.
     4378            <td class="top">Dusseault, L. and J. Snell, “<a href="https://tools.ietf.org/html/rfc5789">PATCH Method for HTTP</a>”, RFC&nbsp;5789, March&nbsp;2010.
    43844379            </td>
    43854380         </tr>
    43864381         <tr>
    43874382            <td class="reference"><b id="RFC5905">[RFC5905]</b></td>
    4388             <td class="top">Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch, “<a href="http://tools.ietf.org/html/rfc5905">Network Time Protocol Version 4: Protocol and Algorithms Specification</a>”, RFC&nbsp;5905, June&nbsp;2010.
     4383            <td class="top">Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch, “<a href="https://tools.ietf.org/html/rfc5905">Network Time Protocol Version 4: Protocol and Algorithms Specification</a>”, RFC&nbsp;5905, June&nbsp;2010.
    43894384            </td>
    43904385         </tr>
    43914386         <tr>
    43924387            <td class="reference"><b id="RFC5987">[RFC5987]</b></td>
    4393             <td class="top"><a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">Reschke, J.</a>, “<a href="http://tools.ietf.org/html/rfc5987">Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters</a>”, RFC&nbsp;5987, August&nbsp;2010.
     4388            <td class="top"><a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">Reschke, J.</a>, “<a href="https://tools.ietf.org/html/rfc5987">Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters</a>”, RFC&nbsp;5987, August&nbsp;2010.
    43944389            </td>
    43954390         </tr>
    43964391         <tr>
    43974392            <td class="reference"><b id="RFC5988">[RFC5988]</b></td>
    4398             <td class="top">Nottingham, M., “<a href="http://tools.ietf.org/html/rfc5988">Web Linking</a>”, RFC&nbsp;5988, October&nbsp;2010.
     4393            <td class="top">Nottingham, M., “<a href="https://tools.ietf.org/html/rfc5988">Web Linking</a>”, RFC&nbsp;5988, October&nbsp;2010.
    43994394            </td>
    44004395         </tr>
    44014396         <tr>
    44024397            <td class="reference"><b id="RFC6265">[RFC6265]</b></td>
    4403             <td class="top"><a href="mailto:abarth@eecs.berkeley.edu" title="&#xA;        University of California, Berkeley&#xA;      ">Barth, A.</a>, “<a href="http://tools.ietf.org/html/rfc6265">HTTP State Management Mechanism</a>”, RFC&nbsp;6265, April&nbsp;2011.
     4398            <td class="top"><a href="mailto:abarth@eecs.berkeley.edu" title="&#xA;        University of California, Berkeley&#xA;      ">Barth, A.</a>, “<a href="https://tools.ietf.org/html/rfc6265">HTTP State Management Mechanism</a>”, RFC&nbsp;6265, April&nbsp;2011.
    44044399            </td>
    44054400         </tr>
    44064401         <tr>
    44074402            <td class="reference"><b id="RFC6266">[RFC6266]</b></td>
    4408             <td class="top"><a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">Reschke, J.</a>, “<a href="http://tools.ietf.org/html/rfc6266">Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)</a>”, RFC&nbsp;6266, June&nbsp;2011.
     4403            <td class="top"><a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">Reschke, J.</a>, “<a href="https://tools.ietf.org/html/rfc6266">Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)</a>”, RFC&nbsp;6266, June&nbsp;2011.
    44094404            </td>
    44104405         </tr>
    44114406         <tr>
    44124407            <td class="reference"><b id="status-308">[status-308]</b></td>
    4413             <td class="top"><a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">Reschke, J.</a>, “<a href="http://tools.ietf.org/html/draft-reschke-http-status-308-07">The Hypertext Transfer Protocol (HTTP) Status Code 308 (Permanent Redirect)</a>”, Internet-Draft&nbsp;draft-reschke-http-status-308-07 (work in progress), March&nbsp;2012.
     4408            <td class="top"><a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">Reschke, J.</a>, “<a href="https://tools.ietf.org/html/draft-reschke-http-status-308-07">The Hypertext Transfer Protocol (HTTP) Status Code 308 (Permanent Redirect)</a>”, Internet-Draft&nbsp;draft-reschke-http-status-308-07 (work in progress), March&nbsp;2012.
    44144409            </td>
    44154410         </tr>
    44164411      </table>
    4417       <div class="avoidbreak">
    4418          <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
    4419          <p><b>Roy T. Fielding</b>
    4420             (editor)
    4421             <br>Adobe Systems Incorporated<br>345 Park Ave<br>San Jose, CA&nbsp;95110<br>USA<br>Email: <a href="mailto:fielding@gbiv.com">fielding@gbiv.com</a><br>URI: <a href="http://roy.gbiv.com/">http://roy.gbiv.com/</a></p>
    4422          <p><b>Julian F. Reschke</b>
    4423             (editor)
    4424             <br>greenbytes GmbH<br>Hafenweg 16<br>Muenster, NW&nbsp;48155<br>Germany<br>Email: <a href="mailto:julian.reschke@greenbytes.de">julian.reschke@greenbytes.de</a><br>URI: <a href="http://greenbytes.de/tech/webdav/">http://greenbytes.de/tech/webdav/</a></p>
    4425       </div>
    44264412      <div id="differences.between.http.and.mime">
    44274413         <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a href="#differences.between.http.and.mime">Differences between HTTP and MIME</a></h1>
     
    44454431         <div id="conversion.to.canonical.form">
    44464432            <h2 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a>&nbsp;<a href="#conversion.to.canonical.form">Conversion to Canonical Form</a></h2>
    4447             <p id="rfc.section.A.2.p.1">MIME requires that an Internet mail body part be converted to canonical form prior to being transferred, as described in <a href="http://tools.ietf.org/html/rfc2049#section-4">Section 4</a> of <a href="#RFC2049" id="rfc.xref.RFC2049.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples">[RFC2049]</cite></a>. <a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section&nbsp;3.1.1.3</a> of this document describes the forms allowed for subtypes of the "text" media type when transmitted over HTTP. <a href="#RFC2046" id="rfc.xref.RFC2046.4"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> requires that content with a type of "text" represent line breaks as CRLF and forbids the use of CR or LF outside of line
     4433            <p id="rfc.section.A.2.p.1">MIME requires that an Internet mail body part be converted to canonical form prior to being transferred, as described in <a href="https://tools.ietf.org/html/rfc2049#section-4">Section 4</a> of <a href="#RFC2049" id="rfc.xref.RFC2049.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples">[RFC2049]</cite></a>. <a href="#canonicalization.and.text.defaults" title="Canonicalization and Text Defaults">Section&nbsp;3.1.1.3</a> of this document describes the forms allowed for subtypes of the "text" media type when transmitted over HTTP. <a href="#RFC2046" id="rfc.xref.RFC2046.4"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> requires that content with a type of "text" represent line breaks as CRLF and forbids the use of CR or LF outside of line
    44484434               break sequences. HTTP allows CRLF, bare CR, and bare LF to indicate a line break within text content.
    44494435            </p>
     
    45544540         <p id="rfc.section.B.p.25">A Method Registry has been defined. (<a href="#method.registry" title="Method Registry">Section&nbsp;8.1</a>)
    45554541         </p>
    4556          <p id="rfc.section.B.p.26">The Status Code Registry has been redefined by this specification; previously, it was defined in <a href="http://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.4"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#status.code.registry" title="Status Code Registry">Section&nbsp;8.2</a>)
     4542         <p id="rfc.section.B.p.26">The Status Code Registry has been redefined by this specification; previously, it was defined in <a href="https://tools.ietf.org/html/rfc2817#section-7.1">Section 7.1</a> of <a href="#RFC2817" id="rfc.xref.RFC2817.4"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#status.code.registry" title="Status Code Registry">Section&nbsp;8.2</a>)
    45574543         </p>
    45584544         <p id="rfc.section.B.p.27">Registration of Content Codings has been changed to require IETF Review. (<a href="#content.coding.registry" title="Content Coding Registry">Section&nbsp;8.4</a>)
     
    45644550      <div id="imported.abnf">
    45654551         <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a href="#imported.abnf">Imported ABNF</a></h1>
    4566          <p id="rfc.section.C.p.1">The following core rules are included by reference, as defined in <a href="http://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a> of <a href="#RFC5234" id="rfc.xref.RFC5234.3"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
     4552         <p id="rfc.section.C.p.1">The following core rules are included by reference, as defined in <a href="https://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a> of <a href="#RFC5234" id="rfc.xref.RFC5234.3"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
    45674553            (hexadecimal 0-9/A-F/a-f), HTAB (horizontal tab), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), and VCHAR
    45684554            (any visible US-ASCII character).
     
    47494735         <ul class="ind">
    47504736            <li><a id="rfc.index.1" href="#rfc.index.1"><b>1</b></a><ul>
    4751                   <li>100 Continue (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.100.1">6.1</a>, <a href="#rfc.iref.68"><b>6.2.1</b></a>, <a href="#rfc.xref.status.100.2">8.2.3</a></li>
    4752                   <li>100-continue (expect value)&nbsp;&nbsp;<a href="#rfc.iref.40"><b>5.1.1</b></a></li>
    4753                   <li>101 Switching Protocols (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.101.1">6.1</a>, <a href="#rfc.iref.68"><b>6.2.2</b></a>, <a href="#rfc.xref.status.101.2">8.2.3</a></li>
    4754                   <li>1xx Informational (status code class)&nbsp;&nbsp;<a href="#rfc.iref.67"><b>6.2</b></a></li>
     4737                  <li>100 Continue (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.100.1">6.1</a>, <a href="#rfc.iref.1.3"><b>6.2.1</b></a>, <a href="#rfc.xref.status.100.2">8.2.3</a></li>
     4738                  <li>100-continue (expect value)&nbsp;&nbsp;<a href="#rfc.iref.1.1"><b>5.1.1</b></a></li>
     4739                  <li>101 Switching Protocols (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.101.1">6.1</a>, <a href="#rfc.iref.1.4"><b>6.2.2</b></a>, <a href="#rfc.xref.status.101.2">8.2.3</a></li>
     4740                  <li>1xx Informational (status code class)&nbsp;&nbsp;<a href="#rfc.iref.1.2"><b>6.2</b></a></li>
    47554741               </ul>
    47564742            </li>
    47574743            <li><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul>
    4758                   <li>200 OK (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.200.1">6.1</a>, <a href="#rfc.iref.69"><b>6.3.1</b></a>, <a href="#rfc.xref.status.200.2">8.2.3</a></li>
    4759                   <li>201 Created (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.201.1">6.1</a>, <a href="#rfc.iref.69"><b>6.3.2</b></a>, <a href="#rfc.xref.status.201.2">8.2.3</a>, <a href="#rfc.xref.status.201.3">B</a></li>
    4760                   <li>202 Accepted (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.202.1">6.1</a>, <a href="#rfc.iref.69"><b>6.3.3</b></a>, <a href="#rfc.xref.status.202.2">8.2.3</a></li>
    4761                   <li>203 Non-Authoritative Information (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.203.1">6.1</a>, <a href="#rfc.iref.69"><b>6.3.4</b></a>, <a href="#rfc.xref.status.203.2">8.2.3</a>, <a href="#rfc.xref.status.203.3">B</a></li>
    4762                   <li>204 No Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.204.1">6.1</a>, <a href="#rfc.iref.69"><b>6.3.5</b></a>, <a href="#rfc.xref.status.204.2">8.2.3</a></li>
    4763                   <li>205 Reset Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.205.1">6.1</a>, <a href="#rfc.iref.69"><b>6.3.6</b></a>, <a href="#rfc.xref.status.205.2">8.2.3</a></li>
    4764                   <li>2xx Successful (status code class)&nbsp;&nbsp;<a href="#rfc.iref.68"><b>6.3</b></a></li>
     4744                  <li>200 OK (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.200.1">6.1</a>, <a href="#rfc.iref.2.2"><b>6.3.1</b></a>, <a href="#rfc.xref.status.200.2">8.2.3</a></li>
     4745                  <li>201 Created (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.201.1">6.1</a>, <a href="#rfc.iref.2.3"><b>6.3.2</b></a>, <a href="#rfc.xref.status.201.2">8.2.3</a>, <a href="#rfc.xref.status.201.3">B</a></li>
     4746                  <li>202 Accepted (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.202.1">6.1</a>, <a href="#rfc.iref.2.4"><b>6.3.3</b></a>, <a href="#rfc.xref.status.202.2">8.2.3</a></li>
     4747                  <li>203 Non-Authoritative Information (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.203.1">6.1</a>, <a href="#rfc.iref.2.5"><b>6.3.4</b></a>, <a href="#rfc.xref.status.203.2">8.2.3</a>, <a href="#rfc.xref.status.203.3">B</a></li>
     4748                  <li>204 No Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.204.1">6.1</a>, <a href="#rfc.iref.2.6"><b>6.3.5</b></a>, <a href="#rfc.xref.status.204.2">8.2.3</a></li>
     4749                  <li>205 Reset Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.205.1">6.1</a>, <a href="#rfc.iref.2.7"><b>6.3.6</b></a>, <a href="#rfc.xref.status.205.2">8.2.3</a></li>
     4750                  <li>2xx Successful (status code class)&nbsp;&nbsp;<a href="#rfc.iref.2.1"><b>6.3</b></a></li>
    47654751               </ul>
    47664752            </li>
    47674753            <li><a id="rfc.index.3" href="#rfc.index.3"><b>3</b></a><ul>
    4768                   <li>300 Multiple Choices (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.300.1">6.1</a>, <a href="#rfc.iref.70"><b>6.4.1</b></a>, <a href="#rfc.xref.status.300.2">6.5.6</a>, <a href="#rfc.xref.status.300.3">8.2.3</a></li>
    4769                   <li>301 Moved Permanently (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.301.1">6.1</a>, <a href="#rfc.iref.70"><b>6.4.2</b></a>, <a href="#rfc.xref.status.301.2">8.2.3</a>, <a href="#rfc.xref.status.301.3">B</a></li>
    4770                   <li>302 Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.302.1">6.1</a>, <a href="#rfc.iref.70"><b>6.4.3</b></a>, <a href="#rfc.xref.status.302.2">8.2.3</a>, <a href="#rfc.xref.status.302.3">B</a></li>
    4771                   <li>303 See Other (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.303.1">6.1</a>, <a href="#rfc.iref.70"><b>6.4.4</b></a>, <a href="#rfc.xref.status.303.2">8.2.3</a>, <a href="#rfc.xref.status.303.3">B</a></li>
    4772                   <li>305 Use Proxy (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.305.1">6.1</a>, <a href="#rfc.iref.70"><b>6.4.5</b></a>, <a href="#rfc.xref.status.305.2">8.2.3</a>, <a href="#rfc.xref.status.305.3">B</a></li>
    4773                   <li>306 (Unused) (status code)&nbsp;&nbsp;<a href="#rfc.iref.70"><b>6.4.6</b></a>, <a href="#rfc.xref.status.306.1">8.2.3</a></li>
    4774                   <li>307 Temporary Redirect (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.307.1">6.1</a>, <a href="#rfc.iref.70"><b>6.4.7</b></a>, <a href="#rfc.xref.status.307.2">8.2.3</a></li>
    4775                   <li>3xx Redirection (status code class)&nbsp;&nbsp;<a href="#rfc.iref.69"><b>6.4</b></a>, <a href="#rfc.xref.status.3xx.1">B</a></li>
     4754                  <li>300 Multiple Choices (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.300.1">6.1</a>, <a href="#rfc.iref.3.2"><b>6.4.1</b></a>, <a href="#rfc.xref.status.300.2">6.5.6</a>, <a href="#rfc.xref.status.300.3">8.2.3</a></li>
     4755                  <li>301 Moved Permanently (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.301.1">6.1</a>, <a href="#rfc.iref.3.3"><b>6.4.2</b></a>, <a href="#rfc.xref.status.301.2">8.2.3</a>, <a href="#rfc.xref.status.301.3">B</a></li>
     4756                  <li>302 Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.302.1">6.1</a>, <a href="#rfc.iref.3.4"><b>6.4.3</b></a>, <a href="#rfc.xref.status.302.2">8.2.3</a>, <a href="#rfc.xref.status.302.3">B</a></li>
     4757                  <li>303 See Other (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.303.1">6.1</a>, <a href="#rfc.iref.3.5"><b>6.4.4</b></a>, <a href="#rfc.xref.status.303.2">8.2.3</a>, <a href="#rfc.xref.status.303.3">B</a></li>
     4758                  <li>305 Use Proxy (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.305.1">6.1</a>, <a href="#rfc.iref.3.6"><b>6.4.5</b></a>, <a href="#rfc.xref.status.305.2">8.2.3</a>, <a href="#rfc.xref.status.305.3">B</a></li>
     4759                  <li>306 (Unused) (status code)&nbsp;&nbsp;<a href="#rfc.iref.3.7"><b>6.4.6</b></a>, <a href="#rfc.xref.status.306.1">8.2.3</a></li>
     4760                  <li>307 Temporary Redirect (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.307.1">6.1</a>, <a href="#rfc.iref.3.8"><b>6.4.7</b></a>, <a href="#rfc.xref.status.307.2">8.2.3</a></li>
     4761                  <li>3xx Redirection (status code class)&nbsp;&nbsp;<a href="#rfc.iref.3.1"><b>6.4</b></a>, <a href="#rfc.xref.status.3xx.1">B</a></li>
    47764762               </ul>
    47774763            </li>
    47784764            <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul>
    4779                   <li>400 Bad Request (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.400.1">6.1</a>, <a href="#rfc.iref.71"><b>6.5.1</b></a>, <a href="#rfc.xref.status.400.2">8.2.3</a>, <a href="#rfc.xref.status.400.3">B</a></li>
    4780                   <li>402 Payment Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.402.1">6.1</a>, <a href="#rfc.iref.71"><b>6.5.2</b></a>, <a href="#rfc.xref.status.402.2">8.2.3</a></li>
    4781                   <li>403 Forbidden (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.403.1">6.1</a>, <a href="#rfc.iref.71"><b>6.5.3</b></a>, <a href="#rfc.xref.status.403.2">8.2.3</a></li>
    4782                   <li>404 Not Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.404.1">6.1</a>, <a href="#rfc.iref.71"><b>6.5.4</b></a>, <a href="#rfc.xref.status.404.2">8.2.3</a></li>
    4783                   <li>405 Method Not Allowed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.405.1">6.1</a>, <a href="#rfc.iref.71"><b>6.5.5</b></a>, <a href="#rfc.xref.status.405.2">8.2.3</a></li>
    4784                   <li>406 Not Acceptable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.406.1">6.1</a>, <a href="#rfc.iref.71"><b>6.5.6</b></a>, <a href="#rfc.xref.status.406.2">8.2.3</a></li>
    4785                   <li>408 Request Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.408.1">6.1</a>, <a href="#rfc.iref.71"><b>6.5.7</b></a>, <a href="#rfc.xref.status.408.2">8.2.3</a></li>
    4786                   <li>409 Conflict (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.409.1">6.1</a>, <a href="#rfc.iref.71"><b>6.5.8</b></a>, <a href="#rfc.xref.status.409.2">8.2.3</a></li>
    4787                   <li>410 Gone (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.410.1">6.1</a>, <a href="#rfc.iref.71"><b>6.5.9</b></a>, <a href="#rfc.xref.status.410.2">8.2.3</a></li>
    4788                   <li>411 Length Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.411.1">6.1</a>, <a href="#rfc.iref.71"><b>6.5.10</b></a>, <a href="#rfc.xref.status.411.2">8.2.3</a></li>
    4789                   <li>413 Payload Too Large (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.413.1">6.1</a>, <a href="#rfc.iref.71"><b>6.5.11</b></a>, <a href="#rfc.xref.status.413.2">8.2.3</a></li>
    4790                   <li>414 URI Too Long (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.414.1">6.1</a>, <a href="#rfc.iref.71"><b>6.5.12</b></a>, <a href="#rfc.xref.status.414.2">8.2.3</a></li>
    4791                   <li>415 Unsupported Media Type (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.415.1">6.1</a>, <a href="#rfc.iref.71"><b>6.5.13</b></a>, <a href="#rfc.xref.status.415.2">8.2.3</a></li>
    4792                   <li>417 Expectation Failed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.417.1">6.1</a>, <a href="#rfc.iref.71"><b>6.5.14</b></a>, <a href="#rfc.xref.status.417.2">8.2.3</a></li>
    4793                   <li>426 Upgrade Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.426.1">6.1</a>, <a href="#rfc.iref.71"><b>6.5.15</b></a>, <a href="#rfc.xref.status.426.2">8.2.3</a>, <a href="#rfc.xref.status.426.3">B</a></li>
    4794                   <li>4xx Client Error (status code class)&nbsp;&nbsp;<a href="#rfc.iref.70"><b>6.5</b></a></li>
     4765                  <li>400 Bad Request (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.400.1">6.1</a>, <a href="#rfc.iref.4.2"><b>6.5.1</b></a>, <a href="#rfc.xref.status.400.2">8.2.3</a>, <a href="#rfc.xref.status.400.3">B</a></li>
     4766                  <li>402 Payment Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.402.1">6.1</a>, <a href="#rfc.iref.4.3"><b>6.5.2</b></a>, <a href="#rfc.xref.status.402.2">8.2.3</a></li>
     4767                  <li>403 Forbidden (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.403.1">6.1</a>, <a href="#rfc.iref.4.4"><b>6.5.3</b></a>, <a href="#rfc.xref.status.403.2">8.2.3</a></li>
     4768                  <li>404 Not Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.404.1">6.1</a>, <a href="#rfc.iref.4.5"><b>6.5.4</b></a>, <a href="#rfc.xref.status.404.2">8.2.3</a></li>
     4769                  <li>405 Method Not Allowed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.405.1">6.1</a>, <a href="#rfc.iref.4.6"><b>6.5.5</b></a>, <a href="#rfc.xref.status.405.2">8.2.3</a></li>
     4770                  <li>406 Not Acceptable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.406.1">6.1</a>, <a href="#rfc.iref.4.7"><b>6.5.6</b></a>, <a href="#rfc.xref.status.406.2">8.2.3</a></li>
     4771                  <li>408 Request Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.408.1">6.1</a>, <a href="#rfc.iref.4.8"><b>6.5.7</b></a>, <a href="#rfc.xref.status.408.2">8.2.3</a></li>
     4772                  <li>409 Conflict (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.409.1">6.1</a>, <a href="#rfc.iref.4.9"><b>6.5.8</b></a>, <a href="#rfc.xref.status.409.2">8.2.3</a></li>
     4773                  <li>410 Gone (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.410.1">6.1</a>, <a href="#rfc.iref.4.10"><b>6.5.9</b></a>, <a href="#rfc.xref.status.410.2">8.2.3</a></li>
     4774                  <li>411 Length Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.411.1">6.1</a>, <a href="#rfc.iref.4.11"><b>6.5.10</b></a>, <a href="#rfc.xref.status.411.2">8.2.3</a></li>
     4775                  <li>413 Payload Too Large (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.413.1">6.1</a>, <a href="#rfc.iref.4.12"><b>6.5.11</b></a>, <a href="#rfc.xref.status.413.2">8.2.3</a></li>
     4776                  <li>414 URI Too Long (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.414.1">6.1</a>, <a href="#rfc.iref.4.13"><b>6.5.12</b></a>, <a href="#rfc.xref.status.414.2">8.2.3</a></li>
     4777                  <li>415 Unsupported Media Type (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.415.1">6.1</a>, <a href="#rfc.iref.4.14"><b>6.5.13</b></a>, <a href="#rfc.xref.status.415.2">8.2.3</a></li>
     4778                  <li>417 Expectation Failed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.417.1">6.1</a>, <a href="#rfc.iref.4.15"><b>6.5.14</b></a>, <a href="#rfc.xref.status.417.2">8.2.3</a></li>
     4779                  <li>426 Upgrade Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.426.1">6.1</a>, <a href="#rfc.iref.4.16"><b>6.5.15</b></a>, <a href="#rfc.xref.status.426.2">8.2.3</a>, <a href="#rfc.xref.status.426.3">B</a></li>
     4780                  <li>4xx Client Error (status code class)&nbsp;&nbsp;<a href="#rfc.iref.4.1"><b>6.5</b></a></li>
    47954781               </ul>
    47964782            </li>
    47974783            <li><a id="rfc.index.5" href="#rfc.index.5"><b>5</b></a><ul>
    4798                   <li>500 Internal Server Error (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.500.1">6.1</a>, <a href="#rfc.iref.72"><b>6.6.1</b></a>, <a href="#rfc.xref.status.500.2">8.2.3</a></li>
    4799                   <li>501 Not Implemented (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.501.1">6.1</a>, <a href="#rfc.iref.72"><b>6.6.2</b></a>, <a href="#rfc.xref.status.501.2">8.2.3</a></li>
    4800                   <li>502 Bad Gateway (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.502.1">6.1</a>, <a href="#rfc.iref.72"><b>6.6.3</b></a>, <a href="#rfc.xref.status.502.2">8.2.3</a></li>
    4801                   <li>503 Service Unavailable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.503.1">6.1</a>, <a href="#rfc.iref.72"><b>6.6.4</b></a>, <a href="#rfc.xref.status.503.2">8.2.3</a></li>
    4802                   <li>504 Gateway Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.504.1">6.1</a>, <a href="#rfc.iref.72"><b>6.6.5</b></a>, <a href="#rfc.xref.status.504.2">8.2.3</a></li>
    4803                   <li>505 HTTP Version Not Supported (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.505.1">6.1</a>, <a href="#rfc.iref.72"><b>6.6.6</b></a>, <a href="#rfc.xref.status.505.2">8.2.3</a></li>
    4804                   <li>5xx Server Error (status code class)&nbsp;&nbsp;<a href="#rfc.iref.71"><b>6.6</b></a></li>
     4784                  <li>500 Internal Server Error (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.500.1">6.1</a>, <a href="#rfc.iref.5.2"><b>6.6.1</b></a>, <a href="#rfc.xref.status.500.2">8.2.3</a></li>
     4785                  <li>501 Not Implemented (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.501.1">6.1</a>, <a href="#rfc.iref.5.3"><b>6.6.2</b></a>, <a href="#rfc.xref.status.501.2">8.2.3</a></li>
     4786                  <li>502 Bad Gateway (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.502.1">6.1</a>, <a href="#rfc.iref.5.4"><b>6.6.3</b></a>, <a href="#rfc.xref.status.502.2">8.2.3</a></li>
     4787                  <li>503 Service Unavailable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.503.1">6.1</a>, <a href="#rfc.iref.5.5"><b>6.6.4</b></a>, <a href="#rfc.xref.status.503.2">8.2.3</a></li>
     4788                  <li>504 Gateway Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.504.1">6.1</a>, <a href="#rfc.iref.5.6"><b>6.6.5</b></a>, <a href="#rfc.xref.status.504.2">8.2.3</a></li>
     4789                  <li>505 HTTP Version Not Supported (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.505.1">6.1</a>, <a href="#rfc.iref.5.7"><b>6.6.6</b></a>, <a href="#rfc.xref.status.505.2">8.2.3</a></li>
     4790                  <li>5xx Server Error (status code class)&nbsp;&nbsp;<a href="#rfc.iref.5.1"><b>6.6</b></a></li>
    48054791               </ul>
    48064792            </li>
     
    51315117         </ul>
    51325118      </div>
     5119      <div class="avoidbreak">
     5120         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
     5121         <p><b>Roy T. Fielding</b>
     5122            (editor)
     5123            <br>Adobe Systems Incorporated<br>345 Park Ave<br>San Jose, CA&nbsp;95110<br>USA<br>Email: <a href="mailto:fielding@gbiv.com">fielding@gbiv.com</a><br>URI: <a href="http://roy.gbiv.com/">http://roy.gbiv.com/</a></p>
     5124         <p><b>Julian F. Reschke</b>
     5125            (editor)
     5126            <br>greenbytes GmbH<br>Hafenweg 16<br>Muenster, NW&nbsp;48155<br>Germany<br>Email: <a href="mailto:julian.reschke@greenbytes.de">julian.reschke@greenbytes.de</a><br>URI: <a href="http://greenbytes.de/tech/webdav/">http://greenbytes.de/tech/webdav/</a></p>
     5127      </div>
    51335128   </body>
    51345129</html>
Note: See TracChangeset for help on using the changeset viewer.