Changeset 1138


Ignore:
Timestamp:
22/02/11 20:45:17 (12 years ago)
Author:
julian.reschke@…
Message:

remove header field ABNF dependencies; replace with Overview tables (see #276)

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

Legend:

Unmodified
Added
Removed

  • draft-ietf-httpbis/latest/httpbis.abnf

    r1128 r1138  
    185185field-value = *( field-content / OWS )
    186186first-byte-pos = 1*DIGIT
    187 general-header = Cache-Control / Connection / Date / Pragma / Trailer / Transfer-Encoding / Upgrade / Via / Warning / MIME-Version
    188187header-field = field-name ":" OWS [ field-value ] OWS
    189188hour = 2DIGIT
    … …  
    251250received-protocol = [ protocol-name "/" ] protocol-version
    252251relative-part = <relative-part, defined in [RFC3986], Section 4.2>
    253 request-header = Accept / Accept-Charset / Accept-Encoding / Accept-Language / Authorization / Expect / From / Host / If-Match / If-Modified-Since / If-None-Match / If-Range / If-Unmodified-Since / Max-Forwards / Proxy-Authorization / Range / Referer / TE / User-Agent
    254252request-target = "*" / absolute-URI / ( path-absolute [ "?" query ] ) / authority
    255 response-header = Accept-Ranges / Age / Allow / ETag / Location / Proxy-Authenticate / Retry-After / Server / Vary / WWW-Authenticate
    256253rfc1123-date = day-name "," SP date1 SP time-of-day SP GMT
    257254rfc850-date = day-name-l "," SP date2 SP time-of-day SP GMT
    … …  
    284281word = token / quoted-string
    285282year = 4DIGIT
     283; Accept defined but not used
     284; Accept-Charset defined but not used
     285; Accept-Encoding defined but not used
     286; Accept-Language defined but not used
     287; Accept-Ranges defined but not used
     288; Age defined but not used
     289; Allow defined but not used
     290; Authorization defined but not used
     291; Cache-Control defined but not used
    286292; Chunked-Body defined but not used
     293; Connection defined but not used
    287294; Content-Encoding defined but not used
    288295; Content-Language defined but not used
    … …  
    292299; Content-Range defined but not used
    293300; Content-Type defined but not used
     301; Date defined but not used
     302; ETag defined but not used
     303; Expect defined but not used
    294304; Expires defined but not used
     305; From defined but not used
    295306; HTTP-message defined but not used
     307; Host defined but not used
     308; If-Match defined but not used
     309; If-Modified-Since defined but not used
     310; If-None-Match defined but not used
     311; If-Range defined but not used
     312; If-Unmodified-Since defined but not used
    296313; Last-Modified defined but not used
     314; Location defined but not used
     315; MIME-Version defined but not used
     316; Max-Forwards defined but not used
     317; Pragma defined but not used
     318; Proxy-Authenticate defined but not used
     319; Proxy-Authorization defined but not used
     320; Range defined but not used
     321; Referer defined but not used
    297322; Request defined but not used
    298323; Response defined but not used
    299 ; general-header defined but not used
     324; Retry-After defined but not used
     325; Server defined but not used
     326; TE defined but not used
     327; Trailer defined but not used
     328; Transfer-Encoding defined but not used
     329; Upgrade defined but not used
     330; User-Agent defined but not used
     331; Vary defined but not used
     332; Via defined but not used
     333; WWW-Authenticate defined but not used
     334; Warning defined but not used
    300335; http-URI defined but not used
    301336; https-URI defined but not used
    302337; realm defined but not used
    303 ; request-header defined but not used
    304 ; response-header defined but not used
    305338; special defined but not used

  • draft-ietf-httpbis/latest/p1-messaging.xml

    r1127 r1138  
    14691469   message being transmitted.
    14701470</t>
    1471 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="general-header"/>
    1472   <x:ref>general-header</x:ref> = <x:ref>Cache-Control</x:ref>            ; &header-cache-control;
    1473                  / <x:ref>Connection</x:ref>               ; <xref target="header.connection"/>
    1474                  / <x:ref>Date</x:ref>                     ; <xref target="header.date"/>
    1475                  / <x:ref>Pragma</x:ref>                   ; &header-pragma;
    1476                  / <x:ref>Trailer</x:ref>                  ; <xref target="header.trailer"/>
    1477                  / <x:ref>Transfer-Encoding</x:ref>        ; <xref target="header.transfer-encoding"/>
    1478                  / <x:ref>Upgrade</x:ref>                  ; <xref target="header.upgrade"/>
    1479                  / <x:ref>Via</x:ref>                      ; <xref target="header.via"/>
    1480                  / <x:ref>Warning</x:ref>                  ; &header-warning;
    1481                  / <x:ref>MIME-Version</x:ref>             ; &header-mime-version;
    1482 </artwork></figure>
     1471<texttable align="left">
     1472  <ttcol>Header Field Name</ttcol>
     1473  <ttcol>Defined in...</ttcol>
     1474 
     1475  <c>Connection</c> <c><xref target="header.connection"/></c>
     1476  <c>Date</c> <c><xref target="header.date"/></c>
     1477  <c>Pragma</c> <c>&header-pragma;</c>
     1478  <c>Trailer</c> <c><xref target="header.trailer"/></c>
     1479  <c>Transfer-Encoding</c> <c><xref target="header.transfer-encoding"/></c>
     1480  <c>Upgrade</c> <c><xref target="header.upgrade"/></c>
     1481  <c>Via</c> <c><xref target="header.via"/></c>
     1482  <c>Warning</c> <c>&header-warning;</c>
     1483  <c>MIME-Version</c> <c>&header-mime-version;</c>
     1484</texttable>
    14831485<t>
    14841486   General-header field names can be extended reliably only in
    … …  
    50705072<x:ref>field-value</x:ref> = *( field-content / OWS )
    50715073
    5072 <x:ref>general-header</x:ref> = Cache-Control / Connection / Date / Pragma / Trailer
    5073  / Transfer-Encoding / Upgrade / Via / Warning / MIME-Version
    5074 
    50755074<x:ref>header-field</x:ref> = field-name ":" OWS [ field-value ] OWS
    50765075<x:ref>hour</x:ref> = 2DIGIT
    … …  
    51605159</figure>
    51615160<figure><preamble>ABNF diagnostics:</preamble><artwork type="inline">
     5161; Cache-Control defined but not used
    51625162; Chunked-Body defined but not used
     5163; Connection defined but not used
    51635164; Content-Length defined but not used
     5165; Date defined but not used
    51645166; HTTP-message defined but not used
    51655167; Host defined but not used
     5168; MIME-Version defined but not used
     5169; Pragma defined but not used
    51665170; Request defined but not used
    51675171; Response defined but not used
    51685172; TE defined but not used
     5173; Trailer defined but not used
     5174; Transfer-Encoding defined but not used
    51695175; URI-reference defined but not used
    5170 ; general-header defined but not used
     5176; Upgrade defined but not used
     5177; Via defined but not used
     5178; Warning defined but not used
    51715179; http-URI defined but not used
    51725180; https-URI defined but not used
    … …  
    57735781      "Migrate Upgrade details from RFC2817"
    57745782    </t>
     5783    <t>
     5784      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/276"/>:
     5785      "untangle ABNFs for header fields"
     5786    </t>
    57755787  </list>
    57765788</t>

  • draft-ietf-httpbis/latest/p2-semantics.html

    r1137 r1138  
    859859         method invocation.
    860860      </p>
    861       <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.2"></span>  <a href="#request.header.fields" class="smpl">request-header</a> = <a href="#abnf.dependencies" class="smpl">Accept</a>                   ; <a href="#Part3" id="rfc.xref.Part3.5"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept" title="Accept">Section 6.1</a>
    862                  / <a href="#abnf.dependencies" class="smpl">Accept-Charset</a>           ; <a href="#Part3" id="rfc.xref.Part3.6"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-charset" title="Accept-Charset">Section 6.2</a>
    863                  / <a href="#abnf.dependencies" class="smpl">Accept-Encoding</a>          ; <a href="#Part3" id="rfc.xref.Part3.7"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-encoding" title="Accept-Encoding">Section 6.3</a>
    864                  / <a href="#abnf.dependencies" class="smpl">Accept-Language</a>          ; <a href="#Part3" id="rfc.xref.Part3.8"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#header.accept-language" title="Accept-Language">Section 6.4</a>
    865                  / <a href="#abnf.dependencies" class="smpl">Authorization</a>            ; <a href="#Part7" id="rfc.xref.Part7.5"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a>
    866                  / <a href="#header.expect" class="smpl">Expect</a>                   ; <a href="#header.expect" id="rfc.xref.header.expect.1" title="Expect">Section&nbsp;9.2</a>
    867                  / <a href="#header.from" class="smpl">From</a>                     ; <a href="#header.from" id="rfc.xref.header.from.1" title="From">Section&nbsp;9.3</a>
    868                  / <a href="#abnf.dependencies" class="smpl">Host</a>                     ; <a href="#Part1" id="rfc.xref.Part1.19"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.host" title="Host">Section 9.4</a>
    869                  / <a href="#abnf.dependencies" class="smpl">If-Match</a>                 ; <a href="#Part4" id="rfc.xref.Part4.6"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-match" title="If-Match">Section 6.2</a>
    870                  / <a href="#abnf.dependencies" class="smpl">If-Modified-Since</a>        ; <a href="#Part4" id="rfc.xref.Part4.7"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-modified-since" title="If-Modified-Since">Section 6.3</a>
    871                  / <a href="#abnf.dependencies" class="smpl">If-None-Match</a>            ; <a href="#Part4" id="rfc.xref.Part4.8"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-none-match" title="If-None-Match">Section 6.4</a>
    872                  / <a href="#abnf.dependencies" class="smpl">If-Range</a>                 ; <a href="#Part5" id="rfc.xref.Part5.4"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.if-range" title="If-Range">Section 5.3</a>
    873                  / <a href="#abnf.dependencies" class="smpl">If-Unmodified-Since</a>      ; <a href="#Part4" id="rfc.xref.Part4.9"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-unmodified-since" title="If-Unmodified-Since">Section 6.5</a>
    874                  / <a href="#header.max-forwards" class="smpl">Max-Forwards</a>             ; <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.1" title="Max-Forwards">Section&nbsp;9.5</a>
    875                  / <a href="#abnf.dependencies" class="smpl">Proxy-Authorization</a>      ; <a href="#Part7" id="rfc.xref.Part7.6"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.proxy-authorization" title="Proxy-Authorization">Section 4.3</a>
    876                  / <a href="#abnf.dependencies" class="smpl">Range</a>                    ; <a href="#Part5" id="rfc.xref.Part5.5"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.range" title="Range">Section 5.4</a>
    877                  / <a href="#header.referer" class="smpl">Referer</a>                  ; <a href="#header.referer" id="rfc.xref.header.referer.1" title="Referer">Section&nbsp;9.6</a>
    878                  / <a href="#abnf.dependencies" class="smpl">TE</a>                       ; <a href="#Part1" id="rfc.xref.Part1.20"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.te" title="TE">Section 9.5</a>
    879                  / <a href="#header.user-agent" class="smpl">User-Agent</a>               ; <a href="#header.user-agent" id="rfc.xref.header.user-agent.1" title="User-Agent">Section&nbsp;9.9</a>
    880 </pre><p id="rfc.section.3.p.3">Request-header field names can be extended reliably only in combination with a change in the protocol version. However, new
     861      <div id="rfc.table.u.2">
     862         <table class="tt full left" cellpadding="3" cellspacing="0">
     863            <thead>
     864               <tr>
     865                  <th>Header Field Name</th>
     866                  <th>Defined in...</th>
     867               </tr>
     868            </thead>
     869            <tbody>
     870               <tr>
     871                  <td class="left">Accept</td>
     872                  <td class="left"><a href="p3-payload.html#header.accept" title="Accept">Section 6.1</a> of <a href="#Part3" id="rfc.xref.Part3.5"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a></td>
     873               </tr>
     874               <tr>
     875                  <td class="left">Accept-Charset</td>
     876                  <td class="left"><a href="p3-payload.html#header.accept-charset" title="Accept-Charset">Section 6.2</a> of <a href="#Part3" id="rfc.xref.Part3.6"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a></td>
     877               </tr>
     878               <tr>
     879                  <td class="left">Accept-Encoding</td>
     880                  <td class="left"><a href="p3-payload.html#header.accept-encoding" title="Accept-Encoding">Section 6.3</a> of <a href="#Part3" id="rfc.xref.Part3.7"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a></td>
     881               </tr>
     882               <tr>
     883                  <td class="left">Accept-Language</td>
     884                  <td class="left"><a href="p3-payload.html#header.accept-language" title="Accept-Language">Section 6.4</a> of <a href="#Part3" id="rfc.xref.Part3.8"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a></td>
     885               </tr>
     886               <tr>
     887                  <td class="left">Authorization</td>
     888                  <td class="left"><a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a> of <a href="#Part7" id="rfc.xref.Part7.5"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a></td>
     889               </tr>
     890               <tr>
     891                  <td class="left">Expect</td>
     892                  <td class="left"><a href="#header.expect" id="rfc.xref.header.expect.1" title="Expect">Section&nbsp;9.2</a></td>
     893               </tr>
     894               <tr>
     895                  <td class="left">From</td>
     896                  <td class="left"><a href="#header.from" id="rfc.xref.header.from.1" title="From">Section&nbsp;9.3</a></td>
     897               </tr>
     898               <tr>
     899                  <td class="left">Host</td>
     900                  <td class="left"><a href="p1-messaging.html#header.host" title="Host">Section 9.4</a> of <a href="#Part1" id="rfc.xref.Part1.19"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a></td>
     901               </tr>
     902               <tr>
     903                  <td class="left">If-Match</td>
     904                  <td class="left"><a href="p4-conditional.html#header.if-match" title="If-Match">Section 6.2</a> of <a href="#Part4" id="rfc.xref.Part4.6"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a></td>
     905               </tr>
     906               <tr>
     907                  <td class="left">If-Modified-Since</td>
     908                  <td class="left"><a href="p4-conditional.html#header.if-modified-since" title="If-Modified-Since">Section 6.3</a> of <a href="#Part4" id="rfc.xref.Part4.7"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a></td>
     909               </tr>
     910               <tr>
     911                  <td class="left">If-None-Match</td>
     912                  <td class="left"><a href="p4-conditional.html#header.if-none-match" title="If-None-Match">Section 6.4</a> of <a href="#Part4" id="rfc.xref.Part4.8"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a></td>
     913               </tr>
     914               <tr>
     915                  <td class="left">If-Range</td>
     916                  <td class="left"><a href="p5-range.html#header.if-range" title="If-Range">Section 5.3</a> of <a href="#Part5" id="rfc.xref.Part5.4"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a></td>
     917               </tr>
     918               <tr>
     919                  <td class="left">If-Unmodified-Since</td>
     920                  <td class="left"><a href="p4-conditional.html#header.if-unmodified-since" title="If-Unmodified-Since">Section 6.5</a> of <a href="#Part4" id="rfc.xref.Part4.9"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a></td>
     921               </tr>
     922               <tr>
     923                  <td class="left">Max-Forwards</td>
     924                  <td class="left"><a href="#header.max-forwards" id="rfc.xref.header.max-forwards.1" title="Max-Forwards">Section&nbsp;9.5</a></td>
     925               </tr>
     926               <tr>
     927                  <td class="left">Proxy-Authorization</td>
     928                  <td class="left"><a href="p7-auth.html#header.proxy-authorization" title="Proxy-Authorization">Section 4.3</a> of <a href="#Part7" id="rfc.xref.Part7.6"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a></td>
     929               </tr>
     930               <tr>
     931                  <td class="left">Range</td>
     932                  <td class="left"><a href="p5-range.html#header.range" title="Range">Section 5.4</a> of <a href="#Part5" id="rfc.xref.Part5.5"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a></td>
     933               </tr>
     934               <tr>
     935                  <td class="left">Referer</td>
     936                  <td class="left"><a href="#header.referer" id="rfc.xref.header.referer.1" title="Referer">Section&nbsp;9.6</a></td>
     937               </tr>
     938               <tr>
     939                  <td class="left">TE</td>
     940                  <td class="left"><a href="p1-messaging.html#header.te" title="TE">Section 9.5</a> of <a href="#Part1" id="rfc.xref.Part1.20"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a></td>
     941               </tr>
     942               <tr>
     943                  <td class="left">User-Agent</td>
     944                  <td class="left"><a href="#header.user-agent" id="rfc.xref.header.user-agent.1" title="User-Agent">Section&nbsp;9.9</a></td>
     945               </tr>
     946            </tbody>
     947         </table>
     948      </div>
     949      <p id="rfc.section.3.p.2">Request-header field names can be extended reliably only in combination with a change in the protocol version. However, new
    881950         or experimental header fields <em class="bcp14">MAY</em> be given the semantics of request-header fields if all parties in the communication recognize them to be request-header fields.
    882951      </p>
    … …  
    886955         client does not need to examine or display the Reason-Phrase.
    887956      </p>
    888       <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.3"></span><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span>  <a href="#status.code.and.reason.phrase" class="smpl">Status-Code</a>    = 3<a href="#notation" class="smpl">DIGIT</a>
     957      <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.2"></span><span id="rfc.iref.g.3"></span><span id="rfc.iref.g.4"></span>  <a href="#status.code.and.reason.phrase" class="smpl">Status-Code</a>    = 3<a href="#notation" class="smpl">DIGIT</a>
    889958  <a href="#status.code.and.reason.phrase" class="smpl">Reason-Phrase</a>  = *( <a href="#notation" class="smpl">WSP</a> / <a href="#notation" class="smpl">VCHAR</a> / <a href="#core.rules" class="smpl">obs-text</a> )
    890959</pre><p id="rfc.section.4.p.4">HTTP status codes are extensible. HTTP applications are not required to understand the meaning of all registered status codes,
    … …  
    898967         protocol.
    899968      </p>
    900       <div id="rfc.table.u.2">
     969      <div id="rfc.table.u.3">
    901970         <table class="tt full left" cellpadding="3" cellspacing="0">
    902971            <thead>
    … …  
    11441213         Status-Line. These header fields give information about the server and about further access to the target resource (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.21"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
    11451214      </p>
    1146       <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.6"></span>  <a href="#response.header.fields" class="smpl">response-header</a> = <a href="#abnf.dependencies" class="smpl">Accept-Ranges</a>           ; <a href="#Part5" id="rfc.xref.Part5.9"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.accept-ranges" title="Accept-Ranges">Section 5.1</a>
    1147                   / <a href="#abnf.dependencies" class="smpl">Age</a>                     ; <a href="#Part6" id="rfc.xref.Part6.5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.age" title="Age">Section 3.1</a>
    1148                   / <a href="#header.allow" class="smpl">Allow</a>                   ; <a href="#header.allow" id="rfc.xref.header.allow.2" title="Allow">Section&nbsp;9.1</a>
    1149                   / <a href="#abnf.dependencies" class="smpl">ETag</a>                    ; <a href="#Part4" id="rfc.xref.Part4.13"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.etag" title="ETag">Section 6.1</a>
    1150                   / <a href="#header.location" class="smpl">Location</a>                ; <a href="#header.location" id="rfc.xref.header.location.1" title="Location">Section&nbsp;9.4</a>
    1151                   / <a href="#abnf.dependencies" class="smpl">Proxy-Authenticate</a>      ; <a href="#Part7" id="rfc.xref.Part7.10"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.proxy-authenticate" title="Proxy-Authenticate">Section 4.2</a>
    1152                   / <a href="#header.retry-after" class="smpl">Retry-After</a>             ; <a href="#header.retry-after" id="rfc.xref.header.retry-after.1" title="Retry-After">Section&nbsp;9.7</a>
    1153                   / <a href="#header.server" class="smpl">Server</a>                  ; <a href="#header.server" id="rfc.xref.header.server.1" title="Server">Section&nbsp;9.8</a>
    1154                   / <a href="#abnf.dependencies" class="smpl">Vary</a>                    ; <a href="#Part6" id="rfc.xref.Part6.6"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.vary" title="Vary">Section 3.5</a>
    1155                   / <a href="#abnf.dependencies" class="smpl">WWW-Authenticate</a>        ; <a href="#Part7" id="rfc.xref.Part7.11"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.www-authenticate" title="WWW-Authenticate">Section 4.4</a>
    1156 </pre><p id="rfc.section.5.p.3">Response-header field names can be extended reliably only in combination with a change in the protocol version. However, new
     1215      <div id="rfc.table.u.4">
     1216         <table class="tt full left" cellpadding="3" cellspacing="0">
     1217            <thead>
     1218               <tr>
     1219                  <th>Method Name</th>
     1220                  <th>Defined in...</th>
     1221               </tr>
     1222            </thead>
     1223            <tbody>
     1224               <tr>
     1225                  <td class="left">Accept-Ranges</td>
     1226                  <td class="left"><a href="p5-range.html#header.accept-ranges" title="Accept-Ranges">Section 5.1</a> of <a href="#Part5" id="rfc.xref.Part5.9"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a></td>
     1227               </tr>
     1228               <tr>
     1229                  <td class="left">Age</td>
     1230                  <td class="left"><a href="p6-cache.html#header.age" title="Age">Section 3.1</a> of <a href="#Part6" id="rfc.xref.Part6.5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a></td>
     1231               </tr>
     1232               <tr>
     1233                  <td class="left">Allow</td>
     1234                  <td class="left"><a href="#header.allow" id="rfc.xref.header.allow.2" title="Allow">Section&nbsp;9.1</a></td>
     1235               </tr>
     1236               <tr>
     1237                  <td class="left">ETag</td>
     1238                  <td class="left"><a href="p4-conditional.html#header.etag" title="ETag">Section 6.1</a> of <a href="#Part4" id="rfc.xref.Part4.13"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a></td>
     1239               </tr>
     1240               <tr>
     1241                  <td class="left">Location</td>
     1242                  <td class="left"><a href="#header.location" id="rfc.xref.header.location.1" title="Location">Section&nbsp;9.4</a></td>
     1243               </tr>
     1244               <tr>
     1245                  <td class="left">Proxy-Authenticate</td>
     1246                  <td class="left"><a href="p7-auth.html#header.proxy-authenticate" title="Proxy-Authenticate">Section 4.2</a> of <a href="#Part7" id="rfc.xref.Part7.10"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a></td>
     1247               </tr>
     1248               <tr>
     1249                  <td class="left">Retry-After</td>
     1250                  <td class="left"><a href="#header.retry-after" id="rfc.xref.header.retry-after.1" title="Retry-After">Section&nbsp;9.7</a></td>
     1251               </tr>
     1252               <tr>
     1253                  <td class="left">Server</td>
     1254                  <td class="left"><a href="#header.server" id="rfc.xref.header.server.1" title="Server">Section&nbsp;9.8</a></td>
     1255               </tr>
     1256               <tr>
     1257                  <td class="left">Vary</td>
     1258                  <td class="left"><a href="p6-cache.html#header.vary" title="Vary">Section 3.5</a> of <a href="#Part6" id="rfc.xref.Part6.6"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a></td>
     1259               </tr>
     1260               <tr>
     1261                  <td class="left">WWW-Authenticate</td>
     1262                  <td class="left"><a href="p7-auth.html#header.www-authenticate" title="WWW-Authenticate">Section 4.4</a> of <a href="#Part7" id="rfc.xref.Part7.11"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a></td>
     1263               </tr>
     1264            </tbody>
     1265         </table>
     1266      </div>
     1267      <p id="rfc.section.5.p.2">Response-header field names can be extended reliably only in combination with a change in the protocol version. However, new
    11571268         or experimental header fields <em class="bcp14">MAY</em> be given the semantics of response-header fields if all parties in the communication recognize them to be response-header
    11581269         fields.
    … …  
    12421353      </p>
    12431354      <h2 id="rfc.section.7.3"><a href="#rfc.section.7.3">7.3</a>&nbsp;<a id="GET" href="#GET">GET</a></h2>
    1244       <div id="rfc.iref.g.7"></div>
     1355      <div id="rfc.iref.g.5"></div>
    12451356      <div id="rfc.iref.m.2"></div>
    12461357      <p id="rfc.section.7.3.p.1">The GET method means retrieve whatever information (in the form of a representation) currently corresponds to the target resource.</p>
    … …  
    13651476      <p id="rfc.section.7.9.p.2">When using CONNECT, the request-target <em class="bcp14">MUST</em> be use the authority form (<a href="p1-messaging.html#request-target" title="request-target">Section 4.1.2</a> of <a href="#Part1" id="rfc.xref.Part1.26"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>); i.e., the host name and port number destination of the requested connection separated by a colon:
    13661477      </p>
    1367       <div id="rfc.figure.u.12"></div><pre class="text2">CONNECT server.example.com:80 HTTP/1.1
     1478      <div id="rfc.figure.u.10"></div><pre class="text2">CONNECT server.example.com:80 HTTP/1.1
    13681479Host: server.example.com:80
    13691480
    … …  
    13721483      </p>
    13731484      <p id="rfc.section.7.9.p.5">For example, proxy authentication might be used to establish the authority to create a tunnel:</p>
    1374       <div id="rfc.figure.u.13"></div><pre class="text2">CONNECT server.example.com:80 HTTP/1.1
     1485      <div id="rfc.figure.u.11"></div><pre class="text2">CONNECT server.example.com:80 HTTP/1.1
    13751486Host: server.example.com:80
    13761487Proxy-Authorization: basic aGVsbG86d29ybGQ=
    … …  
    14081519         a request, then it need not forward the corresponding 100 (Continue) response(s).)
    14091520      </p>
    1410       <div id="rfc.iref.24"></div>
     1521      <div id="rfc.iref.22"></div>
    14111522      <div id="rfc.iref.s.2"></div>
    14121523      <h3 id="rfc.section.8.1.1"><a href="#rfc.section.8.1.1">8.1.1</a>&nbsp;<a id="status.100" href="#status.100">100 Continue</a></h3>
    … …  
    14151526         server <em class="bcp14">MUST</em> send a final response after the request has been completed. See <a href="p1-messaging.html#use.of.the.100.status" title="Use of the 100 (Continue) Status">Section 7.2.3</a> of <a href="#Part1" id="rfc.xref.Part1.27"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for detailed discussion of the use and handling of this status code.
    14161527      </p>
    1417       <div id="rfc.iref.25"></div>
     1528      <div id="rfc.iref.23"></div>
    14181529      <div id="rfc.iref.s.3"></div>
    14191530      <h3 id="rfc.section.8.1.2"><a href="#rfc.section.8.1.2">8.1.2</a>&nbsp;<a id="status.101" href="#status.101">101 Switching Protocols</a></h3>
    … …  
    14271538      <h2 id="rfc.section.8.2"><a href="#rfc.section.8.2">8.2</a>&nbsp;<a id="status.2xx" href="#status.2xx">Successful 2xx</a></h2>
    14281539      <p id="rfc.section.8.2.p.1">This class of status code indicates that the client's request was successfully received, understood, and accepted.</p>
    1429       <div id="rfc.iref.26"></div>
     1540      <div id="rfc.iref.24"></div>
    14301541      <div id="rfc.iref.s.4"></div>
    14311542      <h3 id="rfc.section.8.2.1"><a href="#rfc.section.8.2.1">8.2.1</a>&nbsp;<a id="status.200" href="#status.200">200 OK</a></h3>
    … …  
    14431554      <p id="rfc.section.8.2.1.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.13"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 200 responses.
    14441555      </p>
    1445       <div id="rfc.iref.27"></div>
     1556      <div id="rfc.iref.25"></div>
    14461557      <div id="rfc.iref.s.5"></div>
    14471558      <h3 id="rfc.section.8.2.2"><a href="#rfc.section.8.2.2">8.2.2</a>&nbsp;<a id="status.201" href="#status.201">201 Created</a></h3>
    … …  
    14551566         just created (see <a href="p4-conditional.html#header.etag" title="ETag">Section 6.1</a> of <a href="#Part4" id="rfc.xref.Part4.14"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>).
    14561567      </p>
    1457       <div id="rfc.iref.28"></div>
     1568      <div id="rfc.iref.26"></div>
    14581569      <div id="rfc.iref.s.6"></div>
    14591570      <h3 id="rfc.section.8.2.3"><a href="#rfc.section.8.2.3">8.2.3</a>&nbsp;<a id="status.202" href="#status.202">202 Accepted</a></h3>
    … …  
    14671578         user can expect the request to be fulfilled.
    14681579      </p>
    1469       <div id="rfc.iref.29"></div>
     1580      <div id="rfc.iref.27"></div>
    14701581      <div id="rfc.iref.s.7"></div>
    14711582      <h3 id="rfc.section.8.2.4"><a href="#rfc.section.8.2.4">8.2.4</a>&nbsp;<a id="status.203" href="#status.203">203 Non-Authoritative Information</a></h3>
    … …  
    14771588      <p id="rfc.section.8.2.4.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.14"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 203 responses.
    14781589      </p>
    1479       <div id="rfc.iref.30"></div>
     1590      <div id="rfc.iref.28"></div>
    14801591      <div id="rfc.iref.s.8"></div>
    14811592      <h3 id="rfc.section.8.2.5"><a href="#rfc.section.8.2.5">8.2.5</a>&nbsp;<a id="status.204" href="#status.204">204 No Content</a></h3>
    … …  
    14911602      <p id="rfc.section.8.2.5.p.3">The 204 response <em class="bcp14">MUST NOT</em> include a message-body, and thus is always terminated by the first empty line after the header fields.
    14921603      </p>
    1493       <div id="rfc.iref.31"></div>
     1604      <div id="rfc.iref.29"></div>
    14941605      <div id="rfc.iref.s.9"></div>
    14951606      <h3 id="rfc.section.8.2.6"><a href="#rfc.section.8.2.6">8.2.6</a>&nbsp;<a id="status.205" href="#status.205">205 Reset Content</a></h3>
    … …  
    15001611      <p id="rfc.section.8.2.6.p.2">The message-body included with the response <em class="bcp14">MUST</em> be empty. Note that receivers still need to parse the response according to the algorithm defined in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.29"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
    15011612      </p>
    1502       <div id="rfc.iref.32"></div>
     1613      <div id="rfc.iref.30"></div>
    15031614      <div id="rfc.iref.s.10"></div>
    15041615      <h3 id="rfc.section.8.2.7"><a href="#rfc.section.8.2.7">8.2.7</a>&nbsp;<a id="status.206" href="#status.206">206 Partial Content</a></h3>
    … …  
    15171628         </p>
    15181629      </div>
    1519       <div id="rfc.iref.33"></div>
     1630      <div id="rfc.iref.31"></div>
    15201631      <div id="rfc.iref.s.11"></div>
    15211632      <h3 id="rfc.section.8.3.1"><a href="#rfc.section.8.3.1">8.3.1</a>&nbsp;<a id="status.300" href="#status.300">300 Multiple Choices</a></h3>
    … …  
    15321643      <p id="rfc.section.8.3.1.p.4">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.16"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 300 responses.
    15331644      </p>
    1534       <div id="rfc.iref.34"></div>
     1645      <div id="rfc.iref.32"></div>
    15351646      <div id="rfc.iref.s.12"></div>
    15361647      <h3 id="rfc.section.8.3.2"><a href="#rfc.section.8.3.2">8.3.2</a>&nbsp;<a id="status.301" href="#status.301">301 Moved Permanently</a></h3>
    … …  
    15501661         </p>
    15511662      </div>
    1552       <div id="rfc.iref.35"></div>
     1663      <div id="rfc.iref.33"></div>
    15531664      <div id="rfc.iref.s.13"></div>
    15541665      <h3 id="rfc.section.8.3.3"><a href="#rfc.section.8.3.3">8.3.3</a>&nbsp;<a id="status.302" href="#status.302">302 Found</a></h3>
    … …  
    15661677         </p>
    15671678      </div>
    1568       <div id="rfc.iref.36"></div>
     1679      <div id="rfc.iref.34"></div>
    15691680      <div id="rfc.iref.s.14"></div>
    15701681      <h3 id="rfc.section.8.3.4"><a href="#rfc.section.8.3.4">8.3.4</a>&nbsp;<a id="status.303" href="#status.303">303 See Other</a></h3>
    … …  
    15861697      <p id="rfc.section.8.3.4.p.4">Except for responses to a HEAD request, the representation of a 303 response <em class="bcp14">SHOULD</em> contain a short hypertext note with a hyperlink to the Location URI.
    15871698      </p>
    1588       <div id="rfc.iref.37"></div>
     1699      <div id="rfc.iref.35"></div>
    15891700      <div id="rfc.iref.s.15"></div>
    15901701      <h3 id="rfc.section.8.3.5"><a href="#rfc.section.8.3.5">8.3.5</a>&nbsp;<a id="status.304" href="#status.304">304 Not Modified</a></h3>
    … …  
    15921703         as defined in <a href="p4-conditional.html#status.304" title="304 Not Modified">Section 3.1</a> of <a href="#Part4" id="rfc.xref.Part4.15"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.
    15931704      </p>
    1594       <div id="rfc.iref.38"></div>
     1705      <div id="rfc.iref.36"></div>
    15951706      <div id="rfc.iref.s.16"></div>
    15961707      <h3 id="rfc.section.8.3.6"><a href="#rfc.section.8.3.6">8.3.6</a>&nbsp;<a id="status.305" href="#status.305">305 Use Proxy</a></h3>
    15971708      <p id="rfc.section.8.3.6.p.1">The 305 status code was defined in a previous version of this specification (see <a href="#changes.from.rfc.2616" title="Changes from RFC 2616">Appendix&nbsp;A</a>), and is now deprecated.
    15981709      </p>
    1599       <div id="rfc.iref.39"></div>
     1710      <div id="rfc.iref.37"></div>
    16001711      <div id="rfc.iref.s.17"></div>
    16011712      <h3 id="rfc.section.8.3.7"><a href="#rfc.section.8.3.7">8.3.7</a>&nbsp;<a id="status.306" href="#status.306">306 (Unused)</a></h3>
    16021713      <p id="rfc.section.8.3.7.p.1">The 306 status code was used in a previous version of the specification, is no longer used, and the code is reserved.</p>
    1603       <div id="rfc.iref.40"></div>
     1714      <div id="rfc.iref.38"></div>
    16041715      <div id="rfc.iref.s.18"></div>
    16051716      <h3 id="rfc.section.8.3.8"><a href="#rfc.section.8.3.8">8.3.8</a>&nbsp;<a id="status.307" href="#status.307">307 Temporary Redirect</a></h3>
    … …  
    16221733         by the HTTP application.
    16231734      </p>
    1624       <div id="rfc.iref.41"></div>
     1735      <div id="rfc.iref.39"></div>
    16251736      <div id="rfc.iref.s.19"></div>
    16261737      <h3 id="rfc.section.8.4.1"><a href="#rfc.section.8.4.1">8.4.1</a>&nbsp;<a id="status.400" href="#status.400">400 Bad Request</a></h3>
    16271738      <p id="rfc.section.8.4.1.p.1">The request could not be understood by the server due to malformed syntax. The client <em class="bcp14">SHOULD NOT</em> repeat the request without modifications.
    16281739      </p>
    1629       <div id="rfc.iref.42"></div>
     1740      <div id="rfc.iref.40"></div>
    16301741      <div id="rfc.iref.s.20"></div>
    16311742      <h3 id="rfc.section.8.4.2"><a href="#rfc.section.8.4.2">8.4.2</a>&nbsp;<a id="status.401" href="#status.401">401 Unauthorized</a></h3>
    16321743      <p id="rfc.section.8.4.2.p.1">The request requires user authentication (see <a href="p7-auth.html#status.401" title="401 Unauthorized">Section 3.1</a> of <a href="#Part7" id="rfc.xref.Part7.12"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>).
    16331744      </p>
    1634       <div id="rfc.iref.43"></div>
     1745      <div id="rfc.iref.41"></div>
    16351746      <div id="rfc.iref.s.21"></div>
    16361747      <h3 id="rfc.section.8.4.3"><a href="#rfc.section.8.4.3">8.4.3</a>&nbsp;<a id="status.402" href="#status.402">402 Payment Required</a></h3>
    16371748      <p id="rfc.section.8.4.3.p.1">This code is reserved for future use.</p>
    1638       <div id="rfc.iref.44"></div>
     1749      <div id="rfc.iref.42"></div>
    16391750      <div id="rfc.iref.s.22"></div>
    16401751      <h3 id="rfc.section.8.4.4"><a href="#rfc.section.8.4.4">8.4.4</a>&nbsp;<a id="status.403" href="#status.403">403 Forbidden</a></h3>
    … …  
    16431754         to the client, the status code 404 (Not Found) can be used instead.
    16441755      </p>
    1645       <div id="rfc.iref.45"></div>
     1756      <div id="rfc.iref.43"></div>
    16461757      <div id="rfc.iref.s.23"></div>
    16471758      <h3 id="rfc.section.8.4.5"><a href="#rfc.section.8.4.5">8.4.5</a>&nbsp;<a id="status.404" href="#status.404">404 Not Found</a></h3>
    … …  
    16511762         has been refused, or when no other response is applicable.
    16521763      </p>
    1653       <div id="rfc.iref.46"></div>
     1764      <div id="rfc.iref.44"></div>
    16541765      <div id="rfc.iref.s.24"></div>
    16551766      <h3 id="rfc.section.8.4.6"><a href="#rfc.section.8.4.6">8.4.6</a>&nbsp;<a id="status.405" href="#status.405">405 Method Not Allowed</a></h3>
    16561767      <p id="rfc.section.8.4.6.p.1">The method specified in the Request-Line is not allowed for the target resource. The response <em class="bcp14">MUST</em> include an Allow header field containing a list of valid methods for the requested resource.
    16571768      </p>
    1658       <div id="rfc.iref.47"></div>
     1769      <div id="rfc.iref.45"></div>
    16591770      <div id="rfc.iref.s.25"></div>
    16601771      <h3 id="rfc.section.8.4.7"><a href="#rfc.section.8.4.7">8.4.7</a>&nbsp;<a id="status.406" href="#status.406">406 Not Acceptable</a></h3>
    … …  
    16741785      <p id="rfc.section.8.4.7.p.4">If the response could be unacceptable, a user agent <em class="bcp14">SHOULD</em> temporarily stop receipt of more data and query the user for a decision on further actions.
    16751786      </p>
    1676       <div id="rfc.iref.48"></div>
     1787      <div id="rfc.iref.46"></div>
    16771788      <div id="rfc.iref.s.26"></div>
    16781789      <h3 id="rfc.section.8.4.8"><a href="#rfc.section.8.4.8">8.4.8</a>&nbsp;<a id="status.407" href="#status.407">407 Proxy Authentication Required</a></h3>
    16791790      <p id="rfc.section.8.4.8.p.1">This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy (see <a href="p7-auth.html#status.407" title="407 Proxy Authentication Required">Section 3.2</a> of <a href="#Part7" id="rfc.xref.Part7.13"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>).
    16801791      </p>
    1681       <div id="rfc.iref.49"></div>
     1792      <div id="rfc.iref.47"></div>
    16821793      <div id="rfc.iref.s.27"></div>
    16831794      <h3 id="rfc.section.8.4.9"><a href="#rfc.section.8.4.9">8.4.9</a>&nbsp;<a id="status.408" href="#status.408">408 Request Timeout</a></h3>
    16841795      <p id="rfc.section.8.4.9.p.1">The client did not produce a request within the time that the server was prepared to wait. The client <em class="bcp14">MAY</em> repeat the request without modifications at any later time.
    16851796      </p>
    1686       <div id="rfc.iref.50"></div>
     1797      <div id="rfc.iref.48"></div>
    16871798      <div id="rfc.iref.s.28"></div>
    16881799      <h3 id="rfc.section.8.4.10"><a href="#rfc.section.8.4.10">8.4.10</a>&nbsp;<a id="status.409" href="#status.409">409 Conflict</a></h3>
    … …  
    16971808         contain a list of the differences between the two versions in a format defined by the response Content-Type.
    16981809      </p>
    1699       <div id="rfc.iref.51"></div>
     1810      <div id="rfc.iref.49"></div>
    17001811      <div id="rfc.iref.s.29"></div>
    17011812      <h3 id="rfc.section.8.4.11"><a href="#rfc.section.8.4.11">8.4.11</a>&nbsp;<a id="status.410" href="#status.410">410 Gone</a></h3>
    … …  
    17121823      <p id="rfc.section.8.4.11.p.3">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 2.3.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.18"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 410 responses.
    17131824      </p>
    1714       <div id="rfc.iref.52"></div>
     1825      <div id="rfc.iref.50"></div>
    17151826      <div id="rfc.iref.s.30"></div>
    17161827      <h3 id="rfc.section.8.4.12"><a href="#rfc.section.8.4.12">8.4.12</a>&nbsp;<a id="status.411" href="#status.411">411 Length Required</a></h3>
    … …  
    17181829         message.
    17191830      </p>
    1720       <div id="rfc.iref.53"></div>
     1831      <div id="rfc.iref.51"></div>
    17211832      <div id="rfc.iref.s.31"></div>
    17221833      <h3 id="rfc.section.8.4.13"><a href="#rfc.section.8.4.13">8.4.13</a>&nbsp;<a id="status.412" href="#status.412">412 Precondition Failed</a></h3>
    … …  
    17241835         defined in <a href="p4-conditional.html#status.412" title="412 Precondition Failed">Section 3.2</a> of <a href="#Part4" id="rfc.xref.Part4.16"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.
    17251836      </p>
    1726       <div id="rfc.iref.54"></div>
     1837      <div id="rfc.iref.52"></div>
    17271838      <div id="rfc.iref.s.32"></div>
    17281839      <h3 id="rfc.section.8.4.14"><a href="#rfc.section.8.4.14">8.4.14</a>&nbsp;<a id="status.413" href="#status.413">413 Request Entity Too Large</a></h3>
    … …  
    17321843      <p id="rfc.section.8.4.14.p.2">If the condition is temporary, the server <em class="bcp14">SHOULD</em> include a Retry-After header field to indicate that it is temporary and after what time the client <em class="bcp14">MAY</em> try again.
    17331844      </p>
    1734       <div id="rfc.iref.55"></div>
     1845      <div id="rfc.iref.53"></div>
    17351846      <div id="rfc.iref.s.33"></div>
    17361847      <h3 id="rfc.section.8.4.15"><a href="#rfc.section.8.4.15">8.4.15</a>&nbsp;<a id="status.414" href="#status.414">414 URI Too Long</a></h3>
    … …  
    17411852         in some servers using fixed-length buffers for reading or manipulating the effective request URI.
    17421853      </p>
    1743       <div id="rfc.iref.56"></div>
     1854      <div id="rfc.iref.54"></div>
    17441855      <div id="rfc.iref.s.34"></div>
    17451856      <h3 id="rfc.section.8.4.16"><a href="#rfc.section.8.4.16">8.4.16</a>&nbsp;<a id="status.415" href="#status.415">415 Unsupported Media Type</a></h3>
    … …  
    17471858         target resource for the requested method.
    17481859      </p>
    1749       <div id="rfc.iref.57"></div>
     1860      <div id="rfc.iref.55"></div>
    17501861      <div id="rfc.iref.s.35"></div>
    17511862      <h3 id="rfc.section.8.4.17"><a href="#rfc.section.8.4.17">8.4.17</a>&nbsp;<a id="status.416" href="#status.416">416 Requested Range Not Satisfiable</a></h3>
    17521863      <p id="rfc.section.8.4.17.p.1">The request included a Range request-header field (<a href="p5-range.html#header.range" title="Range">Section 5.4</a> of <a href="#Part5" id="rfc.xref.Part5.12"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>) and none of the range-specifier values in this field overlap the current extent of the selected resource. See <a href="p5-range.html#status.416" title="416 Requested Range Not Satisfiable">Section 3.2</a> of <a href="#Part5" id="rfc.xref.Part5.13"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>.
    17531864      </p>
    1754       <div id="rfc.iref.58"></div>
     1865      <div id="rfc.iref.56"></div>
    17551866      <div id="rfc.iref.s.36"></div>
    17561867      <h3 id="rfc.section.8.4.18"><a href="#rfc.section.8.4.18">8.4.18</a>&nbsp;<a id="status.417" href="#status.417">417 Expectation Failed</a></h3>
    … …  
    17581869         not be met by the next-hop server.
    17591870      </p>
    1760       <div id="rfc.iref.59"></div>
     1871      <div id="rfc.iref.57"></div>
    17611872      <div id="rfc.iref.s.37"></div>
    17621873      <h3 id="rfc.section.8.4.19"><a href="#rfc.section.8.4.19">8.4.19</a>&nbsp;<a id="status.426" href="#status.426">426 Upgrade Required</a></h3>
    17631874      <p id="rfc.section.8.4.19.p.1">The request can not be completed without a prior protocol upgrade. This response <em class="bcp14">MUST</em> include an Upgrade header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 9.8</a> of <a href="#Part1" id="rfc.xref.Part1.30"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) specifying the required protocols.
    17641875      </p>
    1765       <div id="rfc.figure.u.14"></div>
     1876      <div id="rfc.figure.u.12"></div>
    17661877      <p>Example:</p>  <pre class="text2">HTTP/1.1 426 Upgrade Required
    17671878Upgrade: HTTP/2.0
    … …  
    17761887         User agents <em class="bcp14">SHOULD</em> display any included representation to the user. These response codes are applicable to any request method.
    17771888      </p>
    1778       <div id="rfc.iref.60"></div>
     1889      <div id="rfc.iref.58"></div>
    17791890      <div id="rfc.iref.s.38"></div>
    17801891      <h3 id="rfc.section.8.5.1"><a href="#rfc.section.8.5.1">8.5.1</a>&nbsp;<a id="status.500" href="#status.500">500 Internal Server Error</a></h3>
    17811892      <p id="rfc.section.8.5.1.p.1">The server encountered an unexpected condition which prevented it from fulfilling the request.</p>
    1782       <div id="rfc.iref.61"></div>
     1893      <div id="rfc.iref.59"></div>
    17831894      <div id="rfc.iref.s.39"></div>
    17841895      <h3 id="rfc.section.8.5.2"><a href="#rfc.section.8.5.2">8.5.2</a>&nbsp;<a id="status.501" href="#status.501">501 Not Implemented</a></h3>
    … …  
    17861897         does not recognize the request method and is not capable of supporting it for any resource.
    17871898      </p>
    1788       <div id="rfc.iref.62"></div>
     1899      <div id="rfc.iref.60"></div>
    17891900      <div id="rfc.iref.s.40"></div>
    17901901      <h3 id="rfc.section.8.5.3"><a href="#rfc.section.8.5.3">8.5.3</a>&nbsp;<a id="status.502" href="#status.502">502 Bad Gateway</a></h3>
    … …  
    17921903         to fulfill the request.
    17931904      </p>
    1794       <div id="rfc.iref.63"></div>
     1905      <div id="rfc.iref.61"></div>
    17951906      <div id="rfc.iref.s.41"></div>
    17961907      <h3 id="rfc.section.8.5.4"><a href="#rfc.section.8.5.4">8.5.4</a>&nbsp;<a id="status.503" href="#status.503">503 Service Unavailable</a></h3>
    … …  
    18031914         </p>
    18041915      </div>
    1805       <div id="rfc.iref.64"></div>
     1916      <div id="rfc.iref.62"></div>
    18061917      <div id="rfc.iref.s.42"></div>
    18071918      <h3 id="rfc.section.8.5.5"><a href="#rfc.section.8.5.5">8.5.5</a>&nbsp;<a id="status.504" href="#status.504">504 Gateway Timeout</a></h3>
    … …  
    18131924         </p>
    18141925      </div>
    1815       <div id="rfc.iref.65"></div>
     1926      <div id="rfc.iref.63"></div>
    18161927      <div id="rfc.iref.s.43"></div>
    18171928      <h3 id="rfc.section.8.5.6"><a href="#rfc.section.8.5.6">8.5.6</a>&nbsp;<a id="status.505" href="#status.505">505 HTTP Version Not Supported</a></h3>
    … …  
    18281939         this field is strictly to inform the recipient of valid methods associated with the resource.
    18291940      </p>
    1830       <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span>  <a href="#header.allow" class="smpl">Allow</a>   = "Allow" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.allow" class="smpl">Allow-v</a>
     1941      <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span>  <a href="#header.allow" class="smpl">Allow</a>   = "Allow" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.allow" class="smpl">Allow-v</a>
    18311942  <a href="#header.allow" class="smpl">Allow-v</a> = #<a href="#method" class="smpl">Method</a>
    18321943</pre><p id="rfc.section.9.1.p.3">Example of use:</p>
    1833       <div id="rfc.figure.u.16"></div><pre class="text">  Allow: GET, HEAD, PUT
     1944      <div id="rfc.figure.u.14"></div><pre class="text">  Allow: GET, HEAD, PUT
    18341945</pre><p id="rfc.section.9.1.p.5">The actual set of allowed methods is defined by the origin server at the time of each request.</p>
    18351946      <p id="rfc.section.9.1.p.6">A proxy <em class="bcp14">MUST NOT</em> modify the Allow header field — it does not need to understand all the methods specified in order to handle them according
    … …  
    18401951      <h2 id="rfc.section.9.2"><a href="#rfc.section.9.2">9.2</a>&nbsp;<a id="header.expect" href="#header.expect">Expect</a></h2>
    18411952      <p id="rfc.section.9.2.p.1">The "Expect" request-header field is used to indicate that particular server behaviors are required by the client.</p>
    1842       <div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g.10"></span><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span>  <a href="#header.expect" class="smpl">Expect</a>       = "Expect" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.expect" class="smpl">Expect-v</a>
     1953      <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span>  <a href="#header.expect" class="smpl">Expect</a>       = "Expect" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.expect" class="smpl">Expect-v</a>
    18431954  <a href="#header.expect" class="smpl">Expect-v</a>     = 1#<a href="#header.expect" class="smpl">expectation</a>
    18441955 
    … …  
    18671978      <p id="rfc.section.9.3.p.1">The "From" request-header field, if given, <em class="bcp14">SHOULD</em> contain an Internet e-mail address for the human user who controls the requesting user agent. The address <em class="bcp14">SHOULD</em> 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>:
    18681979      </p>
    1869       <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.15"></span><span id="rfc.iref.g.16"></span>  <a href="#header.from" class="smpl">From</a>    = "From" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.from" class="smpl">From-v</a>
     1980      <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span>  <a href="#header.from" class="smpl">From</a>    = "From" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.from" class="smpl">From-v</a>
    18701981  <a href="#header.from" class="smpl">From-v</a>  = <a href="#header.from" class="smpl">mailbox</a>
    18711982 
    18721983  <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;
    18731984</pre><p id="rfc.section.9.3.p.3">An example is:</p>
    1874       <div id="rfc.figure.u.19"></div><pre class="text">  From: webmaster@example.org
     1985      <div id="rfc.figure.u.17"></div><pre class="text">  From: webmaster@example.org
    18751986</pre><p id="rfc.section.9.3.p.5">This header field <em class="bcp14">MAY</em> be used for logging purposes and as a means for identifying the source of invalid or unwanted requests. It <em class="bcp14">SHOULD NOT</em> be used as an insecure form of access protection. The interpretation of this field is that the request is being performed
    18761987         on behalf of the person given, who accepts responsibility for the method performed. In particular, robot agents <em class="bcp14">SHOULD</em> include this header field so that the person responsible for running the robot can be contacted if problems occur on the receiving
    … …  
    18952006      <p id="rfc.section.9.4.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.1"><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.2"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>, <a href="http://tools.ietf.org/html/rfc3986#section-5">Section 5</a>).
    18962007      </p>
    1897       <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.17"></span><span id="rfc.iref.g.18"></span>  <a href="#header.location" class="smpl">Location</a>       = "Location" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.location" class="smpl">Location-v</a>
     2008      <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.15"></span><span id="rfc.iref.g.16"></span>  <a href="#header.location" class="smpl">Location</a>       = "Location" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.location" class="smpl">Location-v</a>
    18982009  <a href="#header.location" class="smpl">Location-v</a>     = <a href="#abnf.dependencies" class="smpl">URI-reference</a>
    1899 </pre><div id="rfc.figure.u.21"></div>
     2010</pre><div id="rfc.figure.u.19"></div>
    19002011      <p>Examples are:</p>  <pre class="text">  Location: http://www.example.org/pub/WWW/People.html#tim
    1901 </pre><div id="rfc.figure.u.22"></div><pre class="text">  Location: /index.html
     2012</pre><div id="rfc.figure.u.20"></div><pre class="text">  Location: /index.html
    19022013</pre><p id="rfc.section.9.4.p.7">There are circumstances in which a fragment identifier in a Location URI would not be appropriate: </p>
    19032014      <ul>
    … …  
    19222033         is attempting to trace a request which appears to be failing or looping in mid-chain.
    19232034      </p>
    1924       <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></span>  <a href="#header.max-forwards" class="smpl">Max-Forwards</a>   = "Max-Forwards" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.max-forwards" class="smpl">Max-Forwards-v</a>
     2035      <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.17"></span><span id="rfc.iref.g.18"></span>  <a href="#header.max-forwards" class="smpl">Max-Forwards</a>   = "Max-Forwards" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.max-forwards" class="smpl">Max-Forwards-v</a>
    19252036  <a href="#header.max-forwards" class="smpl">Max-Forwards-v</a> = 1*<a href="#notation" class="smpl">DIGIT</a>
    19262037</pre><p id="rfc.section.9.5.p.3">The Max-Forwards value is a decimal integer indicating the remaining number of times this request message can be forwarded.</p>
    … …  
    19432054         non-HTTP URIs (e.g., FTP).
    19442055      </p>
    1945       <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.21"></span><span id="rfc.iref.g.22"></span>  <a href="#header.referer" class="smpl">Referer</a>        = "Referer" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.referer" class="smpl">Referer-v</a>
     2056      <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></span>  <a href="#header.referer" class="smpl">Referer</a>        = "Referer" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.referer" class="smpl">Referer-v</a>
    19462057  <a href="#header.referer" class="smpl">Referer-v</a>      = <a href="#abnf.dependencies" class="smpl">absolute-URI</a> / <a href="#abnf.dependencies" class="smpl">partial-URI</a>
    19472058</pre><p id="rfc.section.9.6.p.5">Example:</p>
    1948       <div id="rfc.figure.u.25"></div><pre class="text">  Referer: http://www.example.org/hypertext/Overview.html
     2059      <div id="rfc.figure.u.23"></div><pre class="text">  Referer: http://www.example.org/hypertext/Overview.html
    19492060</pre><p id="rfc.section.9.6.p.7">If the field value is a relative URI, it <em class="bcp14">SHOULD</em> be interpreted relative to the effective request URI. The URI <em class="bcp14">MUST NOT</em> include a fragment. See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section&nbsp;11.2</a> for security considerations.
    19502061      </p>
    … …  
    19572068      </p>
    19582069      <p id="rfc.section.9.7.p.2">The value of this field can be either an HTTP-date or an integer number of seconds (in decimal) after the time of the response.</p>
    1959       <div id="rfc.figure.u.26"></div><pre class="inline"><span id="rfc.iref.g.23"></span><span id="rfc.iref.g.24"></span>  <a href="#header.retry-after" class="smpl">Retry-After</a>   = "Retry-After" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.retry-after" class="smpl">Retry-After-v</a>
     2070      <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.21"></span><span id="rfc.iref.g.22"></span>  <a href="#header.retry-after" class="smpl">Retry-After</a>   = "Retry-After" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.retry-after" class="smpl">Retry-After-v</a>
    19602071  <a href="#header.retry-after" class="smpl">Retry-After-v</a> = <a href="#abnf.dependencies" class="smpl">HTTP-date</a> / <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>
    19612072</pre><div id="rule.delta-seconds">
    19622073         <p id="rfc.section.9.7.p.4">  Time spans are non-negative decimal integers, representing time in seconds.</p>
    19632074      </div>
    1964       <div id="rfc.figure.u.27"></div><pre class="inline"><span id="rfc.iref.g.25"></span>  <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>  = 1*<a href="#notation" class="smpl">DIGIT</a>
     2075      <div id="rfc.figure.u.25"></div><pre class="inline"><span id="rfc.iref.g.23"></span>  <a href="#rule.delta-seconds" class="smpl">delta-seconds</a>  = 1*<a href="#notation" class="smpl">DIGIT</a>
    19652076</pre><p id="rfc.section.9.7.p.6">Two examples of its use are</p>
    1966       <div id="rfc.figure.u.28"></div><pre class="text">  Retry-After: Fri, 31 Dec 1999 23:59:59 GMT
     2077      <div id="rfc.figure.u.26"></div><pre class="text">  Retry-After: Fri, 31 Dec 1999 23:59:59 GMT
    19672078  Retry-After: 120
    19682079</pre><p id="rfc.section.9.7.p.8">In the latter example, the delay is 2 minutes.</p>
    … …  
    19742085         identifying the application.
    19752086      </p>
    1976       <div id="rfc.figure.u.29"></div><pre class="inline"><span id="rfc.iref.g.26"></span><span id="rfc.iref.g.27"></span>  <a href="#header.server" class="smpl">Server</a>         = "Server" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.server" class="smpl">Server-v</a>
     2087      <div id="rfc.figure.u.27"></div><pre class="inline"><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span>  <a href="#header.server" class="smpl">Server</a>         = "Server" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.server" class="smpl">Server-v</a>
    19772088  <a href="#header.server" class="smpl">Server-v</a>       = <a href="#abnf.dependencies" class="smpl">product</a>
    19782089                   *( <a href="#core.rules" class="smpl">RWS</a> ( <a href="#abnf.dependencies" class="smpl">product</a> / <a href="#abnf.dependencies" class="smpl">comment</a> ) )
    19792090</pre><p id="rfc.section.9.8.p.4">Example:</p>
    1980       <div id="rfc.figure.u.30"></div><pre class="text">  Server: CERN/3.0 libwww/2.17
     2091      <div id="rfc.figure.u.28"></div><pre class="text">  Server: CERN/3.0 libwww/2.17
    19812092</pre><p id="rfc.section.9.8.p.6">If the response is being forwarded through a proxy, the proxy application <em class="bcp14">MUST NOT</em> modify the Server response-header field. Instead, it <em class="bcp14">MUST</em> include a Via field (as described in <a href="p1-messaging.html#header.via" title="Via">Section 9.9</a> of <a href="#Part1" id="rfc.xref.Part1.35"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
    19822093      </p>
    … …  
    20062117         doing so makes the field value more difficult to parse.
    20072118      </p>
    2008       <div id="rfc.figure.u.31"></div><pre class="inline"><span id="rfc.iref.g.28"></span><span id="rfc.iref.g.29"></span>  <a href="#header.user-agent" class="smpl">User-Agent</a>     = "User-Agent" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.user-agent" class="smpl">User-Agent-v</a>
     2119      <div id="rfc.figure.u.29"></div><pre class="inline"><span id="rfc.iref.g.26"></span><span id="rfc.iref.g.27"></span>  <a href="#header.user-agent" class="smpl">User-Agent</a>     = "User-Agent" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.user-agent" class="smpl">User-Agent-v</a>
    20092120  <a href="#header.user-agent" class="smpl">User-Agent-v</a>   = <a href="#abnf.dependencies" class="smpl">product</a> *( <a href="#core.rules" class="smpl">RWS</a> ( <a href="#abnf.dependencies" class="smpl">product</a> / <a href="#abnf.dependencies" class="smpl">comment</a> ) )
    20102121</pre><p id="rfc.section.9.9.p.7">Example:</p>
    2011       <div id="rfc.figure.u.32"></div><pre class="text">  User-Agent: CERN-LineMode/2.15 libwww/2.17b3
     2122      <div id="rfc.figure.u.30"></div><pre class="text">  User-Agent: CERN-LineMode/2.15 libwww/2.17b3
    20122123</pre><h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
    20132124      <h2 id="rfc.section.10.1"><a href="#rfc.section.10.1">10.1</a>&nbsp;<a id="method.registration" href="#method.registration">Method Registry</a></h2>
    … …  
    26002711      </p>
    26012712      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
    2602       <div id="rfc.figure.u.33"></div> <pre class="inline"><a href="#abnf.dependencies" class="smpl">Accept</a> = &lt;Accept, defined in [Part3], Section 6.1&gt;
     2713      <div id="rfc.figure.u.31"></div> <pre class="inline"><a href="#abnf.dependencies" class="smpl">Accept</a> = &lt;Accept, defined in [Part3], Section 6.1&gt;
    26032714<a href="#abnf.dependencies" class="smpl">Accept-Charset</a> = &lt;Accept-Charset, defined in [Part3], Section 6.2&gt;
    26042715<a href="#abnf.dependencies" class="smpl">Accept-Encoding</a> = &lt;Accept-Encoding, defined in [Part3], Section 6.3&gt;
    … …  
    26852796<a href="#core.rules" class="smpl">quoted-string</a> = &lt;quoted-string, defined in [Part1], Section 1.2.2&gt;
    26862797
    2687 <a href="#request.header.fields" class="smpl">request-header</a> = Accept / Accept-Charset / Accept-Encoding /
    2688  Accept-Language / Authorization / Expect / From / Host / If-Match /
    2689  If-Modified-Since / If-None-Match / If-Range / If-Unmodified-Since /
    2690  Max-Forwards / Proxy-Authorization / Range / Referer / TE /
    2691  User-Agent
    2692 <a href="#response.header.fields" class="smpl">response-header</a> = Accept-Ranges / Age / Allow / ETag / Location /
    2693  Proxy-Authenticate / Retry-After / Server / Vary / WWW-Authenticate
    2694 
    26952798<a href="#core.rules" class="smpl">token</a> = &lt;token, defined in [Part1], Section 1.2.2&gt;
    2696 </pre> <div id="rfc.figure.u.34"></div>
    2697       <p>ABNF diagnostics:</p><pre class="inline">; Reason-Phrase defined but not used
     2799</pre> <div id="rfc.figure.u.32"></div>
     2800      <p>ABNF diagnostics:</p><pre class="inline">; Accept defined but not used
     2801; Accept-Charset defined but not used
     2802; Accept-Encoding defined but not used
     2803; Accept-Language defined but not used
     2804; Accept-Ranges defined but not used
     2805; Age defined but not used
     2806; Allow defined but not used
     2807; Authorization defined but not used
     2808; ETag defined but not used
     2809; Expect defined but not used
     2810; From defined but not used
     2811; Host defined but not used
     2812; If-Match defined but not used
     2813; If-Modified-Since defined but not used
     2814; If-None-Match defined but not used
     2815; If-Range defined but not used
     2816; If-Unmodified-Since defined but not used
     2817; Location defined but not used
     2818; Max-Forwards defined but not used
     2819; Proxy-Authenticate defined but not used
     2820; Proxy-Authorization defined but not used
     2821; Range defined but not used
     2822; Reason-Phrase defined but not used
     2823; Referer defined but not used
     2824; Retry-After defined but not used
     2825; Server defined but not used
    26982826; Status-Code defined but not used
    2699 ; request-header defined but not used
    2700 ; response-header defined but not used
     2827; TE defined but not used
     2828; User-Agent defined but not used
     2829; Vary defined but not used
     2830; WWW-Authenticate defined but not used
    27012831</pre><h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
    27022832      <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a>&nbsp;Since RFC 2616
    … …  
    29173047         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/275">http://tools.ietf.org/wg/httpbis/trac/ticket/275</a>&gt;: "duplicate ABNF for 'Method'"
    29183048         </li>
     3049         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/276">http://tools.ietf.org/wg/httpbis/trac/ticket/276</a>&gt;: "untangle ABNFs for header fields"
     3050         </li>
    29193051      </ul>
    29203052      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    … …  
    29243056         <ul class="ind">
    29253057            <li><a id="rfc.index.1" href="#rfc.index.1"><b>1</b></a><ul>
    2926                   <li>100 Continue (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.100.1">4.1</a>, <a href="#rfc.iref.24"><b>8.1.1</b></a>, <a href="#rfc.xref.status.100.2">10.2</a></li>
    2927                   <li>101 Switching Protocols (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.101.1">4.1</a>, <a href="#rfc.iref.25"><b>8.1.2</b></a>, <a href="#rfc.xref.status.101.2">10.2</a></li>
     3058                  <li>100 Continue (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.100.1">4.1</a>, <a href="#rfc.iref.22"><b>8.1.1</b></a>, <a href="#rfc.xref.status.100.2">10.2</a></li>
     3059                  <li>101 Switching Protocols (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.101.1">4.1</a>, <a href="#rfc.iref.23"><b>8.1.2</b></a>, <a href="#rfc.xref.status.101.2">10.2</a></li>
    29283060               </ul>
    29293061            </li>
    29303062            <li><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul>
    2931                   <li>200 OK (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.200.1">4.1</a>, <a href="#rfc.iref.26"><b>8.2.1</b></a>, <a href="#rfc.xref.status.200.2">10.2</a></li>
    2932                   <li>201 Created (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.201.1">4.1</a>, <a href="#rfc.iref.27"><b>8.2.2</b></a>, <a href="#rfc.xref.status.201.2">10.2</a></li>
    2933                   <li>202 Accepted (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.202.1">4.1</a>, <a href="#rfc.iref.28"><b>8.2.3</b></a>, <a href="#rfc.xref.status.202.2">10.2</a></li>
    2934                   <li>203 Non-Authoritative Information (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.203.1">4.1</a>, <a href="#rfc.iref.29"><b>8.2.4</b></a>, <a href="#rfc.xref.status.203.2">10.2</a></li>
    2935                   <li>204 No Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.204.1">4.1</a>, <a href="#rfc.iref.30"><b>8.2.5</b></a>, <a href="#rfc.xref.status.204.2">10.2</a></li>
    2936                   <li>205 Reset Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.205.1">4.1</a>, <a href="#rfc.iref.31"><b>8.2.6</b></a>, <a href="#rfc.xref.status.205.2">10.2</a></li>
    2937                   <li>206 Partial Content (status code)&nbsp;&nbsp;<a href="#rfc.iref.32"><b>8.2.7</b></a></li>
     3063                  <li>200 OK (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.200.1">4.1</a>, <a href="#rfc.iref.24"><b>8.2.1</b></a>, <a href="#rfc.xref.status.200.2">10.2</a></li>
     3064                  <li>201 Created (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.201.1">4.1</a>, <a href="#rfc.iref.25"><b>8.2.2</b></a>, <a href="#rfc.xref.status.201.2">10.2</a></li>
     3065                  <li>202 Accepted (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.202.1">4.1</a>, <a href="#rfc.iref.26"><b>8.2.3</b></a>, <a href="#rfc.xref.status.202.2">10.2</a></li>
     3066                  <li>203 Non-Authoritative Information (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.203.1">4.1</a>, <a href="#rfc.iref.27"><b>8.2.4</b></a>, <a href="#rfc.xref.status.203.2">10.2</a></li>
     3067                  <li>204 No Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.204.1">4.1</a>, <a href="#rfc.iref.28"><b>8.2.5</b></a>, <a href="#rfc.xref.status.204.2">10.2</a></li>
     3068                  <li>205 Reset Content (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.205.1">4.1</a>, <a href="#rfc.iref.29"><b>8.2.6</b></a>, <a href="#rfc.xref.status.205.2">10.2</a></li>
     3069                  <li>206 Partial Content (status code)&nbsp;&nbsp;<a href="#rfc.iref.30"><b>8.2.7</b></a></li>
    29383070               </ul>
    29393071            </li>
    29403072            <li><a id="rfc.index.3" href="#rfc.index.3"><b>3</b></a><ul>
    2941                   <li>300 Multiple Choices (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.300.1">4.1</a>, <a href="#rfc.iref.33"><b>8.3.1</b></a>, <a href="#rfc.xref.status.300.2">10.2</a></li>
    2942                   <li>301 Moved Permanently (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.301.1">4.1</a>, <a href="#rfc.iref.34"><b>8.3.2</b></a>, <a href="#rfc.xref.status.301.2">10.2</a>, <a href="#rfc.xref.status.301.3">A</a></li>
    2943                   <li>302 Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.302.1">4.1</a>, <a href="#rfc.iref.35"><b>8.3.3</b></a>, <a href="#rfc.xref.status.302.2">10.2</a>, <a href="#rfc.xref.status.302.3">A</a></li>
    2944                   <li>303 See Other (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.303.1">4.1</a>, <a href="#rfc.xref.status.303.2">8.3.3</a>, <a href="#rfc.iref.36"><b>8.3.4</b></a>, <a href="#rfc.xref.status.303.3">10.2</a></li>
    2945                   <li>304 Not Modified (status code)&nbsp;&nbsp;<a href="#rfc.iref.37"><b>8.3.5</b></a></li>
    2946                   <li>305 Use Proxy (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.305.1">4.1</a>, <a href="#rfc.iref.38"><b>8.3.6</b></a>, <a href="#rfc.xref.status.305.2">10.2</a>, <a href="#rfc.xref.status.305.3">A</a></li>
    2947                   <li>306 (Unused) (status code)&nbsp;&nbsp;<a href="#rfc.iref.39"><b>8.3.7</b></a>, <a href="#rfc.xref.status.306.1">10.2</a></li>
    2948                   <li>307 Temporary Redirect (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.307.1">4.1</a>, <a href="#rfc.xref.status.307.2">8.3.3</a>, <a href="#rfc.iref.40"><b>8.3.8</b></a>, <a href="#rfc.xref.status.307.3">10.2</a>, <a href="#rfc.xref.status.307.4">A</a></li>
     3073                  <li>300 Multiple Choices (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.300.1">4.1</a>, <a href="#rfc.iref.31"><b>8.3.1</b></a>, <a href="#rfc.xref.status.300.2">10.2</a></li>
     3074                  <li>301 Moved Permanently (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.301.1">4.1</a>, <a href="#rfc.iref.32"><b>8.3.2</b></a>, <a href="#rfc.xref.status.301.2">10.2</a>, <a href="#rfc.xref.status.301.3">A</a></li>
     3075                  <li>302 Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.302.1">4.1</a>, <a href="#rfc.iref.33"><b>8.3.3</b></a>, <a href="#rfc.xref.status.302.2">10.2</a>, <a href="#rfc.xref.status.302.3">A</a></li>
     3076                  <li>303 See Other (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.303.1">4.1</a>, <a href="#rfc.xref.status.303.2">8.3.3</a>, <a href="#rfc.iref.34"><b>8.3.4</b></a>, <a href="#rfc.xref.status.303.3">10.2</a></li>
     3077                  <li>304 Not Modified (status code)&nbsp;&nbsp;<a href="#rfc.iref.35"><b>8.3.5</b></a></li>
     3078                  <li>305 Use Proxy (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.305.1">4.1</a>, <a href="#rfc.iref.36"><b>8.3.6</b></a>, <a href="#rfc.xref.status.305.2">10.2</a>, <a href="#rfc.xref.status.305.3">A</a></li>
     3079                  <li>306 (Unused) (status code)&nbsp;&nbsp;<a href="#rfc.iref.37"><b>8.3.7</b></a>, <a href="#rfc.xref.status.306.1">10.2</a></li>
     3080                  <li>307 Temporary Redirect (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.307.1">4.1</a>, <a href="#rfc.xref.status.307.2">8.3.3</a>, <a href="#rfc.iref.38"><b>8.3.8</b></a>, <a href="#rfc.xref.status.307.3">10.2</a>, <a href="#rfc.xref.status.307.4">A</a></li>
    29493081               </ul>
    29503082            </li>
    29513083            <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul>
    2952                   <li>400 Bad Request (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.400.1">4.1</a>, <a href="#rfc.iref.41"><b>8.4.1</b></a>, <a href="#rfc.xref.status.400.2">10.2</a></li>
    2953                   <li>401 Unauthorized (status code)&nbsp;&nbsp;<a href="#rfc.iref.42"><b>8.4.2</b></a></li>
    2954                   <li>402 Payment Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.402.1">4.1</a>, <a href="#rfc.iref.43"><b>8.4.3</b></a>, <a href="#rfc.xref.status.402.2">10.2</a></li>
    2955                   <li>403 Forbidden (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.403.1">4.1</a>, <a href="#rfc.iref.44"><b>8.4.4</b></a>, <a href="#rfc.xref.status.403.2">10.2</a></li>
    2956                   <li>404 Not Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.404.1">4.1</a>, <a href="#rfc.iref.45"><b>8.4.5</b></a>, <a href="#rfc.xref.status.404.2">10.2</a></li>
    2957                   <li>405 Method Not Allowed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.405.1">4.1</a>, <a href="#rfc.iref.46"><b>8.4.6</b></a>, <a href="#rfc.xref.status.405.2">10.2</a></li>
    2958                   <li>406 Not Acceptable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.406.1">4.1</a>, <a href="#rfc.iref.47"><b>8.4.7</b></a>, <a href="#rfc.xref.status.406.2">10.2</a></li>
    2959                   <li>407 Proxy Authentication Required (status code)&nbsp;&nbsp;<a href="#rfc.iref.48"><b>8.4.8</b></a>, <a href="#rfc.xref.status.407.1">10.2</a></li>
    2960                   <li>408 Request Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.408.1">4.1</a>, <a href="#rfc.iref.49"><b>8.4.9</b></a>, <a href="#rfc.xref.status.408.2">10.2</a></li>
    2961                   <li>409 Conflict (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.409.1">4.1</a>, <a href="#rfc.iref.50"><b>8.4.10</b></a>, <a href="#rfc.xref.status.409.2">10.2</a></li>
    2962                   <li>410 Gone (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.410.1">4.1</a>, <a href="#rfc.iref.51"><b>8.4.11</b></a>, <a href="#rfc.xref.status.410.2">10.2</a></li>
    2963                   <li>411 Length Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.411.1">4.1</a>, <a href="#rfc.iref.52"><b>8.4.12</b></a>, <a href="#rfc.xref.status.411.2">10.2</a></li>
    2964                   <li>412 Precondition Failed (status code)&nbsp;&nbsp;<a href="#rfc.iref.53"><b>8.4.13</b></a></li>
    2965                   <li>413 Request Entity Too Large (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.413.1">4.1</a>, <a href="#rfc.iref.54"><b>8.4.14</b></a>, <a href="#rfc.xref.status.413.2">10.2</a></li>
    2966                   <li>414 URI Too Long (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.414.1">4.1</a>, <a href="#rfc.iref.55"><b>8.4.15</b></a>, <a href="#rfc.xref.status.414.2">10.2</a></li>
    2967                   <li>415 Unsupported Media Type (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.415.1">4.1</a>, <a href="#rfc.iref.56"><b>8.4.16</b></a>, <a href="#rfc.xref.status.415.2">10.2</a></li>
    2968                   <li>416 Requested Range Not Satisfiable (status code)&nbsp;&nbsp;<a href="#rfc.iref.57"><b>8.4.17</b></a></li>
    2969                   <li>417 Expectation Failed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.417.1">4.1</a>, <a href="#rfc.iref.58"><b>8.4.18</b></a>, <a href="#rfc.xref.status.417.2">10.2</a></li>
    2970                   <li>426 Upgrade Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.426.1">4.1</a>, <a href="#rfc.iref.59"><b>8.4.19</b></a>, <a href="#rfc.xref.status.426.2">10.2</a>, <a href="#rfc.xref.status.426.3">A</a></li>
     3084                  <li>400 Bad Request (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.400.1">4.1</a>, <a href="#rfc.iref.39"><b>8.4.1</b></a>, <a href="#rfc.xref.status.400.2">10.2</a></li>
     3085                  <li>401 Unauthorized (status code)&nbsp;&nbsp;<a href="#rfc.iref.40"><b>8.4.2</b></a></li>
     3086                  <li>402 Payment Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.402.1">4.1</a>, <a href="#rfc.iref.41"><b>8.4.3</b></a>, <a href="#rfc.xref.status.402.2">10.2</a></li>
     3087                  <li>403 Forbidden (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.403.1">4.1</a>, <a href="#rfc.iref.42"><b>8.4.4</b></a>, <a href="#rfc.xref.status.403.2">10.2</a></li>
     3088                  <li>404 Not Found (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.404.1">4.1</a>, <a href="#rfc.iref.43"><b>8.4.5</b></a>, <a href="#rfc.xref.status.404.2">10.2</a></li>
     3089                  <li>405 Method Not Allowed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.405.1">4.1</a>, <a href="#rfc.iref.44"><b>8.4.6</b></a>, <a href="#rfc.xref.status.405.2">10.2</a></li>
     3090                  <li>406 Not Acceptable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.406.1">4.1</a>, <a href="#rfc.iref.45"><b>8.4.7</b></a>, <a href="#rfc.xref.status.406.2">10.2</a></li>
     3091                  <li>407 Proxy Authentication Required (status code)&nbsp;&nbsp;<a href="#rfc.iref.46"><b>8.4.8</b></a>, <a href="#rfc.xref.status.407.1">10.2</a></li>
     3092                  <li>408 Request Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.408.1">4.1</a>, <a href="#rfc.iref.47"><b>8.4.9</b></a>, <a href="#rfc.xref.status.408.2">10.2</a></li>
     3093                  <li>409 Conflict (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.409.1">4.1</a>, <a href="#rfc.iref.48"><b>8.4.10</b></a>, <a href="#rfc.xref.status.409.2">10.2</a></li>
     3094                  <li>410 Gone (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.410.1">4.1</a>, <a href="#rfc.iref.49"><b>8.4.11</b></a>, <a href="#rfc.xref.status.410.2">10.2</a></li>
     3095                  <li>411 Length Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.411.1">4.1</a>, <a href="#rfc.iref.50"><b>8.4.12</b></a>, <a href="#rfc.xref.status.411.2">10.2</a></li>
     3096                  <li>412 Precondition Failed (status code)&nbsp;&nbsp;<a href="#rfc.iref.51"><b>8.4.13</b></a></li>
     3097                  <li>413 Request Entity Too Large (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.413.1">4.1</a>, <a href="#rfc.iref.52"><b>8.4.14</b></a>, <a href="#rfc.xref.status.413.2">10.2</a></li>
     3098                  <li>414 URI Too Long (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.414.1">4.1</a>, <a href="#rfc.iref.53"><b>8.4.15</b></a>, <a href="#rfc.xref.status.414.2">10.2</a></li>
     3099                  <li>415 Unsupported Media Type (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.415.1">4.1</a>, <a href="#rfc.iref.54"><b>8.4.16</b></a>, <a href="#rfc.xref.status.415.2">10.2</a></li>
     3100                  <li>416 Requested Range Not Satisfiable (status code)&nbsp;&nbsp;<a href="#rfc.iref.55"><b>8.4.17</b></a></li>
     3101                  <li>417 Expectation Failed (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.417.1">4.1</a>, <a href="#rfc.iref.56"><b>8.4.18</b></a>, <a href="#rfc.xref.status.417.2">10.2</a></li>
     3102                  <li>426 Upgrade Required (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.426.1">4.1</a>, <a href="#rfc.iref.57"><b>8.4.19</b></a>, <a href="#rfc.xref.status.426.2">10.2</a>, <a href="#rfc.xref.status.426.3">A</a></li>
    29713103               </ul>
    29723104            </li>
    29733105            <li><a id="rfc.index.5" href="#rfc.index.5"><b>5</b></a><ul>
    2974                   <li>500 Internal Server Error (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.500.1">4.1</a>, <a href="#rfc.iref.60"><b>8.5.1</b></a>, <a href="#rfc.xref.status.500.2">10.2</a></li>
    2975                   <li>501 Not Implemented (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.501.1">4.1</a>, <a href="#rfc.iref.61"><b>8.5.2</b></a>, <a href="#rfc.xref.status.501.2">10.2</a></li>
    2976                   <li>502 Bad Gateway (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.502.1">4.1</a>, <a href="#rfc.iref.62"><b>8.5.3</b></a>, <a href="#rfc.xref.status.502.2">10.2</a></li>
    2977                   <li>503 Service Unavailable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.503.1">4.1</a>, <a href="#rfc.iref.63"><b>8.5.4</b></a>, <a href="#rfc.xref.status.503.2">10.2</a></li>
    2978                   <li>504 Gateway Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.504.1">4.1</a>, <a href="#rfc.iref.64"><b>8.5.5</b></a>, <a href="#rfc.xref.status.504.2">10.2</a></li>
    2979                   <li>505 HTTP Version Not Supported (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.505.1">4.1</a>, <a href="#rfc.iref.65"><b>8.5.6</b></a>, <a href="#rfc.xref.status.505.2">10.2</a></li>
     3106                  <li>500 Internal Server Error (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.500.1">4.1</a>, <a href="#rfc.iref.58"><b>8.5.1</b></a>, <a href="#rfc.xref.status.500.2">10.2</a></li>
     3107                  <li>501 Not Implemented (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.501.1">4.1</a>, <a href="#rfc.iref.59"><b>8.5.2</b></a>, <a href="#rfc.xref.status.501.2">10.2</a></li>
     3108                  <li>502 Bad Gateway (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.502.1">4.1</a>, <a href="#rfc.iref.60"><b>8.5.3</b></a>, <a href="#rfc.xref.status.502.2">10.2</a></li>
     3109                  <li>503 Service Unavailable (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.503.1">4.1</a>, <a href="#rfc.iref.61"><b>8.5.4</b></a>, <a href="#rfc.xref.status.503.2">10.2</a></li>
     3110                  <li>504 Gateway Timeout (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.504.1">4.1</a>, <a href="#rfc.iref.62"><b>8.5.5</b></a>, <a href="#rfc.xref.status.504.2">10.2</a></li>
     3111                  <li>505 HTTP Version Not Supported (status code)&nbsp;&nbsp;<a href="#rfc.xref.status.505.1">4.1</a>, <a href="#rfc.iref.63"><b>8.5.6</b></a>, <a href="#rfc.xref.status.505.2">10.2</a></li>
    29803112               </ul>
    29813113            </li>
    … …  
    30013133            </li>
    30023134            <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul>
    3003                   <li>GET method&nbsp;&nbsp;<a href="#rfc.xref.GET.1">2.1</a>, <a href="#rfc.iref.g.7"><b>7.3</b></a>, <a href="#rfc.xref.GET.2">10.1</a></li>
     3135                  <li>GET method&nbsp;&nbsp;<a href="#rfc.xref.GET.1">2.1</a>, <a href="#rfc.iref.g.5"><b>7.3</b></a>, <a href="#rfc.xref.GET.2">10.1</a></li>
    30043136                  <li><tt>Grammar</tt>&nbsp;&nbsp;
    30053137                     <ul>
    3006                         <li><tt>Allow</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.8"><b>9.1</b></a></li>
    3007                         <li><tt>Allow-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.9"><b>9.1</b></a></li>
    3008                         <li><tt>delta-seconds</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.25"><b>9.7</b></a></li>
    3009                         <li><tt>Expect</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.10"><b>9.2</b></a></li>
    3010                         <li><tt>expect-params</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.14"><b>9.2</b></a></li>
    3011                         <li><tt>Expect-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.11"><b>9.2</b></a></li>
    3012                         <li><tt>expectation</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.12"><b>9.2</b></a></li>
    3013                         <li><tt>expectation-extension</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.13"><b>9.2</b></a></li>
    3014                         <li><tt>extension-code</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.4"><b>4</b></a></li>
    3015                         <li><tt>From</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.15"><b>9.3</b></a></li>
    3016                         <li><tt>From-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.16"><b>9.3</b></a></li>
    3017                         <li><tt>Location</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.17"><b>9.4</b></a></li>
    3018                         <li><tt>Location-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.18"><b>9.4</b></a></li>
    3019                         <li><tt>Max-Forwards</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.19"><b>9.5</b></a></li>
    3020                         <li><tt>Max-Forwards-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.20"><b>9.5</b></a></li>
     3138                        <li><tt>Allow</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.6"><b>9.1</b></a></li>
     3139                        <li><tt>Allow-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.7"><b>9.1</b></a></li>
     3140                        <li><tt>delta-seconds</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.23"><b>9.7</b></a></li>
     3141                        <li><tt>Expect</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.8"><b>9.2</b></a></li>
     3142                        <li><tt>expect-params</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.12"><b>9.2</b></a></li>
     3143                        <li><tt>Expect-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.9"><b>9.2</b></a></li>
     3144                        <li><tt>expectation</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.10"><b>9.2</b></a></li>
     3145                        <li><tt>expectation-extension</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.11"><b>9.2</b></a></li>
     3146                        <li><tt>extension-code</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.3"><b>4</b></a></li>
     3147                        <li><tt>From</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.13"><b>9.3</b></a></li>
     3148                        <li><tt>From-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.14"><b>9.3</b></a></li>
     3149                        <li><tt>Location</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.15"><b>9.4</b></a></li>
     3150                        <li><tt>Location-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.16"><b>9.4</b></a></li>
     3151                        <li><tt>Max-Forwards</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.17"><b>9.5</b></a></li>
     3152                        <li><tt>Max-Forwards-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.18"><b>9.5</b></a></li>
    30213153                        <li><tt>Method</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.1"><b>2</b></a></li>
    3022                         <li><tt>Reason-Phrase</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.5"><b>4</b></a></li>
    3023                         <li><tt>Referer</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.21"><b>9.6</b></a></li>
    3024                         <li><tt>Referer-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.22"><b>9.6</b></a></li>
    3025                         <li><tt>request-header</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.2"><b>3</b></a></li>
    3026                         <li><tt>response-header</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.6"><b>5</b></a></li>
    3027                         <li><tt>Retry-After</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.23"><b>9.7</b></a></li>
    3028                         <li><tt>Retry-After-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.24"><b>9.7</b></a></li>
    3029                         <li><tt>Server</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.26"><b>9.8</b></a></li>
    3030                         <li><tt>Server-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.27"><b>9.8</b></a></li>
    3031                         <li><tt>Status-Code</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.3"><b>4</b></a></li>
    3032                         <li><tt>User-Agent</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.28"><b>9.9</b></a></li>
    3033                         <li><tt>User-Agent-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.29"><b>9.9</b></a></li>
     3154                        <li><tt>Reason-Phrase</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.4"><b>4</b></a></li>
     3155                        <li><tt>Referer</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.19"><b>9.6</b></a></li>
     3156                        <li><tt>Referer-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.20"><b>9.6</b></a></li>
     3157                        <li><tt>Retry-After</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.21"><b>9.7</b></a></li>
     3158                        <li><tt>Retry-After-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.22"><b>9.7</b></a></li>
     3159                        <li><tt>Server</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.24"><b>9.8</b></a></li>
     3160                        <li><tt>Server-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.25"><b>9.8</b></a></li>
     3161                        <li><tt>Status-Code</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.2"><b>4</b></a></li>
     3162                        <li><tt>User-Agent</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.26"><b>9.9</b></a></li>
     3163                        <li><tt>User-Agent-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.27"><b>9.9</b></a></li>
    30343164                     </ul>
    30353165                  </li>

  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1137 r1138  
    536536   invocation.
    537537</t>
    538 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="request-header"/>
    539   <x:ref>request-header</x:ref> = <x:ref>Accept</x:ref>                   ; &header-accept;
    540                  / <x:ref>Accept-Charset</x:ref>           ; &header-accept-charset;
    541                  / <x:ref>Accept-Encoding</x:ref>          ; &header-accept-encoding;
    542                  / <x:ref>Accept-Language</x:ref>          ; &header-accept-language;
    543                  / <x:ref>Authorization</x:ref>            ; &header-authorization;
    544                  / <x:ref>Expect</x:ref>                   ; <xref target="header.expect"/>
    545                  / <x:ref>From</x:ref>                     ; <xref target="header.from"/>
    546                  / <x:ref>Host</x:ref>                     ; &header-host;
    547                  / <x:ref>If-Match</x:ref>                 ; &header-if-match;
    548                  / <x:ref>If-Modified-Since</x:ref>        ; &header-if-modified-since;
    549                  / <x:ref>If-None-Match</x:ref>            ; &header-if-none-match;
    550                  / <x:ref>If-Range</x:ref>                 ; &header-if-range;
    551                  / <x:ref>If-Unmodified-Since</x:ref>      ; &header-if-unmodified-since;
    552                  / <x:ref>Max-Forwards</x:ref>             ; <xref target="header.max-forwards"/>
    553                  / <x:ref>Proxy-Authorization</x:ref>      ; &header-proxy-authorization;
    554                  / <x:ref>Range</x:ref>                    ; &header-range;
    555                  / <x:ref>Referer</x:ref>                  ; <xref target="header.referer"/>
    556                  / <x:ref>TE</x:ref>                       ; &header-te;
    557                  / <x:ref>User-Agent</x:ref>               ; <xref target="header.user-agent"/>
    558 </artwork></figure>
     538<texttable align="left">
     539  <ttcol>Header Field Name</ttcol>
     540  <ttcol>Defined in...</ttcol>
     541
     542  <c>Accept</c> <c>&header-accept;</c>
     543  <c>Accept-Charset</c> <c>&header-accept-charset;</c>
     544  <c>Accept-Encoding</c> <c>&header-accept-encoding;</c>
     545  <c>Accept-Language</c> <c>&header-accept-language;</c>
     546  <c>Authorization</c> <c>&header-authorization;</c>
     547  <c>Expect</c> <c><xref target="header.expect"/></c>
     548  <c>From</c> <c><xref target="header.from"/></c>
     549  <c>Host</c> <c>&header-host;</c>
     550  <c>If-Match</c> <c>&header-if-match;</c>
     551  <c>If-Modified-Since</c> <c>&header-if-modified-since;</c>
     552  <c>If-None-Match</c> <c>&header-if-none-match;</c>
     553  <c>If-Range</c> <c>&header-if-range;</c>
     554  <c>If-Unmodified-Since</c> <c>&header-if-unmodified-since;</c>
     555  <c>Max-Forwards</c> <c><xref target="header.max-forwards"/></c>
     556  <c>Proxy-Authorization</c> <c>&header-proxy-authorization;</c>
     557  <c>Range</c> <c>&header-range;</c>
     558  <c>Referer</c> <c><xref target="header.referer"/></c>
     559  <c>TE</c> <c>&header-te;</c>
     560  <c>User-Agent</c> <c><xref target="header.user-agent"/></c>
     561</texttable>
    559562<t>
    560563   Request-header field names can be extended reliably only in
    … …  
    725728   further access to the target resource (&effective-request-uri;).
    726729</t>
    727 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="response-header"/>
    728   <x:ref>response-header</x:ref> = <x:ref>Accept-Ranges</x:ref>           ; &header-accept-ranges;
    729                   / <x:ref>Age</x:ref>                     ; &header-age;
    730                   / <x:ref>Allow</x:ref>                   ; <xref target="header.allow"/>
    731                   / <x:ref>ETag</x:ref>                    ; &header-etag;
    732                   / <x:ref>Location</x:ref>                ; <xref target="header.location"/>
    733                   / <x:ref>Proxy-Authenticate</x:ref>      ; &header-proxy-authenticate;
    734                   / <x:ref>Retry-After</x:ref>             ; <xref target="header.retry-after"/>
    735                   / <x:ref>Server</x:ref>                  ; <xref target="header.server"/>
    736                   / <x:ref>Vary</x:ref>                    ; &header-vary;
    737                   / <x:ref>WWW-Authenticate</x:ref>        ; &header-www-authenticate;
    738 </artwork></figure>
     730<texttable align="left">
     731  <ttcol>Method Name</ttcol><ttcol>Defined in...</ttcol>
     732
     733  <c>Accept-Ranges</c> <c>&header-accept-ranges;</c>
     734  <c>Age</c> <c>&header-age;</c>
     735  <c>Allow</c> <c><xref target="header.allow"/></c>
     736  <c>ETag</c> <c>&header-etag;</c>
     737  <c>Location</c> <c><xref target="header.location"/></c>
     738  <c>Proxy-Authenticate</c> <c>&header-proxy-authenticate;</c>
     739  <c>Retry-After</c> <c><xref target="header.retry-after"/></c>
     740  <c>Server</c> <c><xref target="header.server"/></c>
     741  <c>Vary</c> <c>&header-vary;</c>
     742  <c>WWW-Authenticate</c> <c>&header-www-authenticate;</c>
     743</texttable>
    739744<t>
    740745   Response-header field names can be extended reliably only in
    … …  
    36253630<x:ref>quoted-string</x:ref> = &lt;quoted-string, defined in [Part1], Section 1.2.2&gt;
    36263631
    3627 <x:ref>request-header</x:ref> = Accept / Accept-Charset / Accept-Encoding /
    3628  Accept-Language / Authorization / Expect / From / Host / If-Match /
    3629  If-Modified-Since / If-None-Match / If-Range / If-Unmodified-Since /
    3630  Max-Forwards / Proxy-Authorization / Range / Referer / TE /
    3631  User-Agent
    3632 <x:ref>response-header</x:ref> = Accept-Ranges / Age / Allow / ETag / Location /
    3633  Proxy-Authenticate / Retry-After / Server / Vary / WWW-Authenticate
    3634 
    36353632<x:ref>token</x:ref> = &lt;token, defined in [Part1], Section 1.2.2&gt;
    36363633</artwork>
    36373634</figure>
    36383635<figure><preamble>ABNF diagnostics:</preamble><artwork type="inline">
     3636; Accept defined but not used
     3637; Accept-Charset defined but not used
     3638; Accept-Encoding defined but not used
     3639; Accept-Language defined but not used
     3640; Accept-Ranges defined but not used
     3641; Age defined but not used
     3642; Allow defined but not used
     3643; Authorization defined but not used
     3644; ETag defined but not used
     3645; Expect defined but not used
     3646; From defined but not used
     3647; Host defined but not used
     3648; If-Match defined but not used
     3649; If-Modified-Since defined but not used
     3650; If-None-Match defined but not used
     3651; If-Range defined but not used
     3652; If-Unmodified-Since defined but not used
     3653; Location defined but not used
     3654; Max-Forwards defined but not used
     3655; Proxy-Authenticate defined but not used
     3656; Proxy-Authorization defined but not used
     3657; Range defined but not used
    36393658; Reason-Phrase defined but not used
     3659; Referer defined but not used
     3660; Retry-After defined but not used
     3661; Server defined but not used
    36403662; Status-Code defined but not used
    3641 ; request-header defined but not used
    3642 ; response-header defined but not used
     3663; TE defined but not used
     3664; User-Agent defined but not used
     3665; Vary defined but not used
     3666; WWW-Authenticate defined but not used
    36433667</artwork></figure></section>
    36443668<?ENDINC p2-semantics.abnf-appendix ?>
    … …  
    40704094      "duplicate ABNF for 'Method'"
    40714095    </t>
     4096    <t>
     4097      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/276"/>:
     4098      "untangle ABNFs for header fields"
     4099    </t>
    40724100  </list>
    40734101</t>

  • draft-ietf-httpbis/latest/p3-payload.html

    r1120 r1138  
    353353  }
    354354  @bottom-center {
    355        content: "Expires August 21, 2011";
     355       content: "Expires August 26, 2011";
    356356  }
    357357  @bottom-right {
    … …  
    402402      <meta name="dct.creator" content="Reschke, J. F.">
    403403      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-latest">
    404       <meta name="dct.issued" scheme="ISO8601" content="2011-02-17">
     404      <meta name="dct.issued" scheme="ISO8601" content="2011-02-22">
    405405      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    406406      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 3 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 3 defines HTTP message content, metadata, and content negotiation.">
    … …  
    428428            </tr>
    429429            <tr>
    430                <td class="left">Expires: August 21, 2011</td>
     430               <td class="left">Expires: August 26, 2011</td>
    431431               <td class="right">J. Mogul</td>
    432432            </tr>
    … …  
    485485            <tr>
    486486               <td class="left"></td>
    487                <td class="right">February 17, 2011</td>
     487               <td class="right">February 22, 2011</td>
    488488            </tr>
    489489         </tbody>
    … …  
    511511         in progress”.
    512512      </p>
    513       <p>This Internet-Draft will expire on August 21, 2011.</p>
     513      <p>This Internet-Draft will expire on August 26, 2011.</p>
    514514      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    515515      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    … …  
    857857         header fields". The following payload header fields are defined by HTTP/1.1:
    858858      </p>
    859       <div id="rfc.figure.u.12"></div><pre class="inline">   <a href="#abnf.dependencies" class="smpl">Content-Length</a>           ; <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.content-length" title="Content-Length">Section 9.2</a>
    860    <a href="#header.content-md5" class="smpl">Content-MD5</a>              ; <a href="#header.content-md5" id="rfc.xref.header.content-md5.1" title="Content-MD5">Section&nbsp;6.8</a>
    861    <a href="#abnf.dependencies" class="smpl">Content-Range</a>            ; <a href="#Part5" id="rfc.xref.Part5.2"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.content-range" title="Content-Range">Section 5.2</a>
    862 </pre><h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a id="payload.body" href="#payload.body">Payload Body</a></h2>
     859      <div id="rfc.table.u.1">
     860         <table class="tt full left" cellpadding="3" cellspacing="0">
     861            <thead>
     862               <tr>
     863                  <th>Header Field Name</th>
     864                  <th>Defined in...</th>
     865               </tr>
     866            </thead>
     867            <tbody>
     868               <tr>
     869                  <td class="left">Content-Length</td>
     870                  <td class="left"><a href="p1-messaging.html#header.content-length" title="Content-Length">Section 9.2</a> of <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a></td>
     871               </tr>
     872               <tr>
     873                  <td class="left">Content-MD5</td>
     874                  <td class="left"><a href="#header.content-md5" id="rfc.xref.header.content-md5.1" title="Content-MD5">Section&nbsp;6.8</a></td>
     875               </tr>
     876               <tr>
     877                  <td class="left">Content-Range</td>
     878                  <td class="left"><a href="p5-range.html#header.content-range" title="Content-Range">Section 5.2</a> of <a href="#Part5" id="rfc.xref.Part5.2"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a></td>
     879               </tr>
     880            </tbody>
     881         </table>
     882      </div>
     883      <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a id="payload.body" href="#payload.body">Payload Body</a></h2>
    863884      <p id="rfc.section.3.2.p.1">A payload body is only present in a message when a message-body is present, as described in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The payload body is obtained from the message-body by decoding any Transfer-Encoding that might have been applied to ensure
    864885         safe and proper transfer of the message.
    … …  
    885906      </p>
    886907      <p id="rfc.section.4.1.p.2">The following header fields are defined as representation metadata:</p>
    887       <div id="rfc.figure.u.13"></div><pre class="inline">   <a href="#header.content-encoding" class="smpl">Content-Encoding</a>         ; <a href="#header.content-encoding" id="rfc.xref.header.content-encoding.2" title="Content-Encoding">Section&nbsp;6.5</a>
    888    <a href="#header.content-language" class="smpl">Content-Language</a>         ; <a href="#header.content-language" id="rfc.xref.header.content-language.1" title="Content-Language">Section&nbsp;6.6</a>
    889    <a href="#header.content-location" class="smpl">Content-Location</a>         ; <a href="#header.content-location" id="rfc.xref.header.content-location.1" title="Content-Location">Section&nbsp;6.7</a>
    890    <a href="#header.content-type" class="smpl">Content-Type</a>             ; <a href="#header.content-type" id="rfc.xref.header.content-type.2" title="Content-Type">Section&nbsp;6.9</a>
    891    <a href="#abnf.dependencies" class="smpl">Expires</a>                  ; <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.expires" title="Expires">Section 3.3</a>
    892    <a href="#abnf.dependencies" class="smpl">Last-Modified</a>            ; <a href="#Part4" id="rfc.xref.Part4.2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.last-modified" title="Last-Modified">Section 6.6</a>
    893 </pre><h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a id="representation.data" href="#representation.data">Representation Data</a></h2>
     908      <div id="rfc.table.u.2">
     909         <table class="tt full left" cellpadding="3" cellspacing="0">
     910            <thead>
     911               <tr>
     912                  <th>Header Field Name</th>
     913                  <th>Defined in...</th>
     914               </tr>
     915            </thead>
     916            <tbody>
     917               <tr>
     918                  <td class="left">Content-Encoding</td>
     919                  <td class="left"><a href="#header.content-encoding" id="rfc.xref.header.content-encoding.2" title="Content-Encoding">Section&nbsp;6.5</a></td>
     920               </tr>
     921               <tr>
     922                  <td class="left">Content-Language</td>
     923                  <td class="left"><a href="#header.content-language" id="rfc.xref.header.content-language.1" title="Content-Language">Section&nbsp;6.6</a></td>
     924               </tr>
     925               <tr>
     926                  <td class="left">Content-Location</td>
     927                  <td class="left"><a href="#header.content-location" id="rfc.xref.header.content-location.1" title="Content-Location">Section&nbsp;6.7</a></td>
     928               </tr>
     929               <tr>
     930                  <td class="left">Content-Type</td>
     931                  <td class="left"><a href="#header.content-type" id="rfc.xref.header.content-type.2" title="Content-Type">Section&nbsp;6.9</a></td>
     932               </tr>
     933               <tr>
     934                  <td class="left">Expires</td>
     935                  <td class="left"><a href="p6-cache.html#header.expires" title="Expires">Section 3.3</a> of <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a></td>
     936               </tr>
     937               <tr>
     938                  <td class="left">Last-Modified</td>
     939                  <td class="left"><a href="p4-conditional.html#header.last-modified" title="Last-Modified">Section 6.6</a> of <a href="#Part4" id="rfc.xref.Part4.2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a></td>
     940               </tr>
     941            </tbody>
     942         </table>
     943      </div>
     944      <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a id="representation.data" href="#representation.data">Representation Data</a></h2>
    894945      <p id="rfc.section.4.2.p.1">The representation body associated with an HTTP message is either provided as the payload body of the message or referred
    895946         to by the message semantics and the effective request URI. The representation data is in a format and encoding defined by
    … …  
    899950         a two-layer, ordered encoding model:
    900951      </p>
    901       <div id="rfc.figure.u.14"></div><pre class="text">  representation-data := Content-Encoding( Content-Type( bits ) )
     952      <div id="rfc.figure.u.12"></div><pre class="text">  representation-data := Content-Encoding( Content-Type( bits ) )
    902953</pre><p id="rfc.section.4.2.p.4">Content-Type specifies the media type of the underlying data, which defines both the data format and how that data <em class="bcp14">SHOULD</em> be processed by the recipient (within the scope of the request method semantics). Any HTTP/1.1 message containing a payload
    903954         body <em class="bcp14">SHOULD</em> include a Content-Type header field defining the media type of the associated representation unless that metadata is unknown
    … …  
    10011052         a request for an in-line image.
    10021053      </p>
    1003       <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span>  <a href="#header.accept" class="smpl">Accept</a>   = "Accept" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.accept" class="smpl">Accept-v</a>
     1054      <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.11"></span><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span>  <a href="#header.accept" class="smpl">Accept</a>   = "Accept" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.accept" class="smpl">Accept-v</a>
    10041055  <a href="#header.accept" class="smpl">Accept-v</a> = #( <a href="#header.accept" class="smpl">media-range</a> [ <a href="#header.accept" class="smpl">accept-params</a> ] )
    10051056 
    … …  
    10251076      </div>
    10261077      <p id="rfc.section.6.1.p.6">The example</p>
    1027       <div id="rfc.figure.u.16"></div><pre class="text">  Accept: audio/*; q=0.2, audio/basic
     1078      <div id="rfc.figure.u.14"></div><pre class="text">  Accept: audio/*; q=0.2, audio/basic
    10281079</pre><p id="rfc.section.6.1.p.8"> <em class="bcp14">SHOULD</em> be interpreted as "I prefer audio/basic, but send me any audio type if it is the best available after an 80% mark-down in
    10291080         quality".
    … …  
    10341085      </p>
    10351086      <p id="rfc.section.6.1.p.10">A more elaborate example is</p>
    1036       <div id="rfc.figure.u.17"></div><pre class="text">  Accept: text/plain; q=0.5, text/html,
     1087      <div id="rfc.figure.u.15"></div><pre class="text">  Accept: text/plain; q=0.5, text/html,
    10371088          text/x-dvi; q=0.8, text/x-c
    10381089</pre><p id="rfc.section.6.1.p.12">Verbally, this would be interpreted as "text/html and text/x-c are the preferred media types, but if they do not exist, then
    … …  
    10421093         to a given type, the most specific reference has precedence. For example,
    10431094      </p>
    1044       <div id="rfc.figure.u.18"></div><pre class="text">  Accept: text/*, text/html, text/html;level=1, */*
     1095      <div id="rfc.figure.u.16"></div><pre class="text">  Accept: text/*, text/html, text/html;level=1, */*
    10451096</pre><p id="rfc.section.6.1.p.15">have the following precedence: </p>
    10461097      <ol>
    … …  
    10531104         which matches that type. For example,
    10541105      </p>
    1055       <div id="rfc.figure.u.19"></div><pre class="text">  Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1,
     1106      <div id="rfc.figure.u.17"></div><pre class="text">  Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1,
    10561107          text/html;level=2;q=0.4, */*;q=0.5
    10571108</pre><p id="rfc.section.6.1.p.18">would cause the following values to be associated:</p>
    1058       <div id="rfc.table.u.1">
     1109      <div id="rfc.table.u.3">
    10591110         <table class="tt full left" cellpadding="3" cellspacing="0">
    10601111            <thead>
    … …  
    11021153         to a server which is capable of representing documents in those character sets.
    11031154      </p>
    1104       <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span>  <a href="#header.accept-charset" class="smpl">Accept-Charset</a>   = "Accept-Charset" ":" <a href="#core.rules" class="smpl">OWS</a>
     1155      <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.16"></span><span id="rfc.iref.g.17"></span>  <a href="#header.accept-charset" class="smpl">Accept-Charset</a>   = "Accept-Charset" ":" <a href="#core.rules" class="smpl">OWS</a>
    11051156          <a href="#header.accept-charset" class="smpl">Accept-Charset-v</a>
    11061157  <a href="#header.accept-charset" class="smpl">Accept-Charset-v</a> = 1#( ( <a href="#rule.charset" class="smpl">charset</a> / "*" )
    … …  
    11091160         example is
    11101161      </p>
    1111       <div id="rfc.figure.u.21"></div><pre class="text">  Accept-Charset: iso-8859-5, unicode-1-1;q=0.8
     1162      <div id="rfc.figure.u.19"></div><pre class="text">  Accept-Charset: iso-8859-5, unicode-1-1;q=0.8
    11121163</pre><p id="rfc.section.6.2.p.5">The special value "*", if present in the Accept-Charset field, matches every character set (including ISO-8859-1) which is
    11131164         not mentioned elsewhere in the Accept-Charset field. If no "*" is present in an Accept-Charset field, then all character sets
    … …  
    11241175      <p id="rfc.section.6.3.p.1">The "Accept-Encoding" request-header field can be used by user agents to indicate what response content-codings (<a href="#content.codings" title="Content Codings">Section&nbsp;2.2</a>) are acceptable in the response.
    11251176      </p>
    1126       <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></span>  <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a>    = "Accept-Encoding" ":" <a href="#core.rules" class="smpl">OWS</a>
     1177      <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></span>  <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a>    = "Accept-Encoding" ":" <a href="#core.rules" class="smpl">OWS</a>
    11271178                     <a href="#header.accept-encoding" class="smpl">Accept-Encoding-v</a>
    11281179  <a href="#header.accept-encoding" class="smpl">Accept-Encoding-v</a>  =
    … …  
    11321183      </p>
    11331184      <p id="rfc.section.6.3.p.4">Examples of its use are:</p>
    1134       <div id="rfc.figure.u.23"></div><pre class="text">  Accept-Encoding: compress, gzip
     1185      <div id="rfc.figure.u.21"></div><pre class="text">  Accept-Encoding: compress, gzip
    11351186  Accept-Encoding:
    11361187  Accept-Encoding: *
    … …  
    11761227         in the response. Language tags are defined in <a href="#language.tags" title="Language Tags">Section&nbsp;2.4</a>.
    11771228      </p>
    1178       <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.21"></span><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span>  <a href="#header.accept-language" class="smpl">Accept-Language</a>   = "Accept-Language" ":" <a href="#core.rules" class="smpl">OWS</a>
     1229      <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.21"></span><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span>  <a href="#header.accept-language" class="smpl">Accept-Language</a>   = "Accept-Language" ":" <a href="#core.rules" class="smpl">OWS</a>
    11791230                    <a href="#header.accept-language" class="smpl">Accept-Language-v</a>
    11801231  <a href="#header.accept-language" class="smpl">Accept-Language-v</a> =
    … …  
    11851236         languages specified by that range. The quality value defaults to "q=1". For example,
    11861237      </p>
    1187       <div id="rfc.figure.u.25"></div><pre class="text">  Accept-Language: da, en-gb;q=0.8, en;q=0.7
     1238      <div id="rfc.figure.u.23"></div><pre class="text">  Accept-Language: da, en-gb;q=0.8, en;q=0.7
    11881239</pre><p id="rfc.section.6.4.p.5">would mean: "I prefer Danish, but will accept British English and other types of English". (see also <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>)
    11891240      </p>
    … …  
    12141265         is primarily used to allow a representation to be compressed without losing the identity of its underlying media type.
    12151266      </p>
    1216       <div id="rfc.figure.u.26"></div><pre class="inline"><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span>  <a href="#header.content-encoding" class="smpl">Content-Encoding</a>   = "Content-Encoding" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-encoding" class="smpl">Content-Encoding-v</a>
     1267      <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span>  <a href="#header.content-encoding" class="smpl">Content-Encoding</a>   = "Content-Encoding" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-encoding" class="smpl">Content-Encoding-v</a>
    12171268  <a href="#header.content-encoding" class="smpl">Content-Encoding-v</a> = 1#<a href="#content.codings" class="smpl">content-coding</a>
    12181269</pre><p id="rfc.section.6.5.p.3">Content codings are defined in <a href="#content.codings" title="Content Codings">Section&nbsp;2.2</a>. An example of its use is
    12191270      </p>
    1220       <div id="rfc.figure.u.27"></div><pre class="text">  Content-Encoding: gzip
     1271      <div id="rfc.figure.u.25"></div><pre class="text">  Content-Encoding: gzip
    12211272</pre><p id="rfc.section.6.5.p.5">The content-coding is a characteristic of the representation. Typically, the representation body is stored with this encoding
    12221273         and is only decoded before rendering or analogous usage. However, a transforming proxy <em class="bcp14">MAY</em> modify the content-coding if the new coding is known to be acceptable to the recipient, unless the "no-transform" cache-control
    … …  
    12351286         that this might not be equivalent to all the languages used within the representation.
    12361287      </p>
    1237       <div id="rfc.figure.u.28"></div><pre class="inline"><span id="rfc.iref.g.26"></span><span id="rfc.iref.g.27"></span>  <a href="#header.content-language" class="smpl">Content-Language</a>   = "Content-Language" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-language" class="smpl">Content-Language-v</a>
     1288      <div id="rfc.figure.u.26"></div><pre class="inline"><span id="rfc.iref.g.26"></span><span id="rfc.iref.g.27"></span>  <a href="#header.content-language" class="smpl">Content-Language</a>   = "Content-Language" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-language" class="smpl">Content-Language-v</a>
    12381289  <a href="#header.content-language" class="smpl">Content-Language-v</a> = 1#<a href="#language.tags" class="smpl">language-tag</a>
    12391290</pre><p id="rfc.section.6.6.p.3">Language tags are defined in <a href="#language.tags" title="Language Tags">Section&nbsp;2.4</a>. The primary purpose of Content-Language is to allow a user to identify and differentiate representations according to the
    … …  
    12411292         field is
    12421293      </p>
    1243       <div id="rfc.figure.u.29"></div><pre class="text">  Content-Language: da
     1294      <div id="rfc.figure.u.27"></div><pre class="text">  Content-Language: da
    12441295</pre><p id="rfc.section.6.6.p.5">If no Content-Language is specified, the default is that the content is intended for all language audiences. This might mean
    12451296         that the sender does not consider it to be specific to any natural language, or that the sender does not know for which language
    … …  
    12491300         simultaneously in the original Maori and English versions, would call for
    12501301      </p>
    1251       <div id="rfc.figure.u.30"></div><pre class="text">  Content-Language: mi, en
     1302      <div id="rfc.figure.u.28"></div><pre class="text">  Content-Language: mi, en
    12521303</pre><p id="rfc.section.6.6.p.8">However, just because multiple languages are present within a representation does not mean that it is intended for multiple
    12531304         linguistic audiences. An example would be a beginner's language primer, such as "A First Lesson in Latin", which is clearly
    … …  
    12631314         would contain the same representation that is enclosed as payload in this message.
    12641315      </p>
    1265       <div id="rfc.figure.u.31"></div><pre class="inline"><span id="rfc.iref.g.28"></span><span id="rfc.iref.g.29"></span>  <a href="#header.content-location" class="smpl">Content-Location</a>   = "Content-Location" ":" <a href="#core.rules" class="smpl">OWS</a>
     1316      <div id="rfc.figure.u.29"></div><pre class="inline"><span id="rfc.iref.g.28"></span><span id="rfc.iref.g.29"></span>  <a href="#header.content-location" class="smpl">Content-Location</a>   = "Content-Location" ":" <a href="#core.rules" class="smpl">OWS</a>
    12661317                    <a href="#header.content-location" class="smpl">Content-Location-v</a>
    12671318  <a href="#header.content-location" class="smpl">Content-Location-v</a> =
    … …  
    13081359         body in transit, but is not proof against malicious attacks.
    13091360      </p>
    1310       <div id="rfc.figure.u.32"></div><pre class="inline"><span id="rfc.iref.g.30"></span><span id="rfc.iref.g.31"></span>  <a href="#header.content-md5" class="smpl">Content-MD5</a>   = "Content-MD5" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-md5" class="smpl">Content-MD5-v</a>
     1361      <div id="rfc.figure.u.30"></div><pre class="inline"><span id="rfc.iref.g.30"></span><span id="rfc.iref.g.31"></span>  <a href="#header.content-md5" class="smpl">Content-MD5</a>   = "Content-MD5" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-md5" class="smpl">Content-MD5-v</a>
    13111362  <a href="#header.content-md5" class="smpl">Content-MD5-v</a> = &lt;base64 of 128 bit MD5 digest as per <a href="#RFC1864" id="rfc.xref.RFC1864.2"><cite title="The Content-MD5 Header Field">[RFC1864]</cite></a>&gt;
    13121363</pre><p id="rfc.section.6.8.p.3">The Content-MD5 header field <em class="bcp14">MAY</em> be generated by an origin server or client to function as an integrity check of the payload body. Only origin servers or user
    … …  
    13421393         the media type is that which would have been sent had the request been a GET.
    13431394      </p>
    1344       <div id="rfc.figure.u.33"></div><pre class="inline"><span id="rfc.iref.g.32"></span><span id="rfc.iref.g.33"></span>  <a href="#header.content-type" class="smpl">Content-Type</a>   = "Content-Type" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-type" class="smpl">Content-Type-v</a>
     1395      <div id="rfc.figure.u.31"></div><pre class="inline"><span id="rfc.iref.g.32"></span><span id="rfc.iref.g.33"></span>  <a href="#header.content-type" class="smpl">Content-Type</a>   = "Content-Type" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.content-type" class="smpl">Content-Type-v</a>
    13451396  <a href="#header.content-type" class="smpl">Content-Type-v</a> = <a href="#media.types" class="smpl">media-type</a>
    13461397</pre><p id="rfc.section.6.9.p.3">Media types are defined in <a href="#media.types" title="Media Types">Section&nbsp;2.3</a>. An example of the field is
    13471398      </p>
    1348       <div id="rfc.figure.u.34"></div><pre class="text">  Content-Type: text/html; charset=ISO-8859-4
     1399      <div id="rfc.figure.u.32"></div><pre class="text">  Content-Type: text/html; charset=ISO-8859-4
    13491400</pre><p id="rfc.section.6.9.p.5">Further discussion of Content-Type is provided in <a href="#representation.data" title="Representation Data">Section&nbsp;4.2</a>.
    13501401      </p>
    … …  
    17101761         environments.
    17111762      </p>
    1712       <div id="rfc.figure.u.35"></div><pre class="inline"><span id="rfc.iref.g.34"></span><span id="rfc.iref.g.35"></span>  <a href="#mime-version" class="smpl">MIME-Version</a>   = "MIME-Version" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#mime-version" class="smpl">MIME-Version-v</a>
     1763      <div id="rfc.figure.u.33"></div><pre class="inline"><span id="rfc.iref.g.34"></span><span id="rfc.iref.g.35"></span>  <a href="#mime-version" class="smpl">MIME-Version</a>   = "MIME-Version" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#mime-version" class="smpl">MIME-Version-v</a>
    17131764  <a href="#mime-version" class="smpl">MIME-Version-v</a> = 1*<a href="#notation" class="smpl">DIGIT</a> "." 1*<a href="#notation" class="smpl">DIGIT</a>
    17141765</pre><p id="rfc.section.A.1.p.3">MIME version "1.0" is the default for use in HTTP/1.1. However, HTTP/1.1 message parsing and semantics are defined by this
    … …  
    17701821      </p>
    17711822      <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
    1772       <div id="rfc.figure.u.36"></div> <pre class="inline"><a href="#header.accept" class="smpl">Accept</a> = "Accept:" OWS Accept-v
     1823      <div id="rfc.figure.u.34"></div> <pre class="inline"><a href="#header.accept" class="smpl">Accept</a> = "Accept:" OWS Accept-v
    17731824<a href="#header.accept-charset" class="smpl">Accept-Charset</a> = "Accept-Charset:" OWS Accept-Charset-v
    17741825<a href="#header.accept-charset" class="smpl">Accept-Charset-v</a> = *( "," OWS ) ( charset / "*" ) [ OWS ";" OWS "q="
    … …  
    18381889
    18391890<a href="#core.rules" class="smpl">word</a> = &lt;word, defined in [Part1], Section 1.2.2&gt;
    1840 </pre> <div id="rfc.figure.u.37"></div>
     1891</pre> <div id="rfc.figure.u.35"></div>
    18411892      <p>ABNF diagnostics:</p><pre class="inline">; Accept defined but not used
    18421893; Accept-Charset defined but not used

  • draft-ietf-httpbis/latest/p3-payload.xml

    r1120 r1138  
    694694   The following payload header fields are defined by HTTP/1.1:
    695695</t>
    696 <figure><artwork type="inline">
    697    <x:ref>Content-Length</x:ref>           ; &header-content-length;
    698    <x:ref>Content-MD5</x:ref>              ; <xref target="header.content-md5"/>
    699    <x:ref>Content-Range</x:ref>            ; &header-content-range;
    700 </artwork></figure>
     696<texttable align="left">
     697  <ttcol>Header Field Name</ttcol>
     698  <ttcol>Defined in...</ttcol>
     699
     700  <c>Content-Length</c> <c>&header-content-length;</c>
     701  <c>Content-MD5</c> <c><xref target="header.content-md5"/></c>
     702  <c>Content-Range</c> <c>&header-content-range;</c>
     703</texttable>
    701704</section>
    702705
    … …  
    748751   The following header fields are defined as representation metadata:
    749752</t>
    750 <figure><artwork type="inline">
    751    <x:ref>Content-Encoding</x:ref>         ; <xref target="header.content-encoding"/>
    752    <x:ref>Content-Language</x:ref>         ; <xref target="header.content-language"/>
    753    <x:ref>Content-Location</x:ref>         ; <xref target="header.content-location"/>
    754    <x:ref>Content-Type</x:ref>             ; <xref target="header.content-type"/>
    755    <x:ref>Expires</x:ref>                  ; &header-expires;
    756    <x:ref>Last-Modified</x:ref>            ; &header-last-modified;
    757 </artwork></figure>
     753<texttable align="left">
     754  <ttcol>Header Field Name</ttcol>
     755  <ttcol>Defined in...</ttcol>
     756
     757  <c>Content-Encoding</c> <c><xref target="header.content-encoding"/></c>
     758  <c>Content-Language</c> <c><xref target="header.content-language"/></c>
     759  <c>Content-Location</c> <c><xref target="header.content-location"/></c>
     760  <c>Content-Type</c> <c><xref target="header.content-type"/></c>
     761  <c>Expires</c> <c>&header-expires;</c>
     762  <c>Last-Modified</c> <c>&header-last-modified;</c>
     763</texttable>
    758764</section>
    759765
Note: See TracChangeset for help on using the changeset viewer.