Ignore:
Timestamp:
Sep 3, 2012, 4:03:33 PM (7 years ago)
Author:
fielding@…
Message:

(editorial) move Vary to p2 because it is generated by origin servers and not limited to caching

File:
1 edited

Legend:

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

    r1859 r1860  
    719719               <li><a href="#rfc.section.8.2">8.2</a>&nbsp;&nbsp;&nbsp;<a href="#response.cache.related">Cache-related</a><ul>
    720720                     <li><a href="#rfc.section.8.2.1">8.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.date">Date</a></li>
     721                     <li><a href="#rfc.section.8.2.2">8.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.vary">Vary</a></li>
    721722                  </ul>
    722723               </li>
     
    11711172         </p>
    11721173      </div>
    1173       <p id="rfc.section.3.5.1.p.7">The <a href="p6-cache.html#header.vary" class="smpl">Vary</a> header field (<a href="p6-cache.html#header.vary" title="Vary">Section 7.5</a> of <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) can be used to express the parameters the server uses to select a representation that is subject to proactive negotiation.
     1174      <p id="rfc.section.3.5.1.p.7">The <a href="#header.vary" class="smpl">Vary</a> header field (<a href="#header.vary" id="rfc.xref.header.vary.1" title="Vary">Section&nbsp;8.2.2</a>) can be used to express the parameters the server uses to select a representation that is subject to proactive negotiation.
    11741175      </p>
    11751176      <h3 id="rfc.section.3.5.2"><a href="#rfc.section.3.5.2">3.5.2</a>&nbsp;<a id="reactive.negotiation" href="#reactive.negotiation">Reactive Negotiation</a></h3>
     
    13591360         are defined to be cacheable. In general, safe methods that do not depend on a current or authoritative response are cacheable,
    13601361         though the overwhelming majority of caches only support GET and HEAD. HTTP requirements for cache behavior and cacheable responses
    1361          are defined in <a href="#Part6" id="rfc.xref.Part6.3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>.
     1362         are defined in <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>.
    13621363      </p>
    13631364      <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a>&nbsp;<a id="method.definitions" href="#method.definitions">Method Definitions</a></h2>
     
    13791380         to reject the request.
    13801381      </p>
    1381       <p id="rfc.section.5.3.1.p.6">The response to a GET request is cacheable and <em class="bcp14">MAY</em> be used to satisfy subsequent GET and HEAD requests (see <a href="#Part6" id="rfc.xref.Part6.4"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
     1382      <p id="rfc.section.5.3.1.p.6">The response to a GET request is cacheable and <em class="bcp14">MAY</em> be used to satisfy subsequent GET and HEAD requests (see <a href="#Part6" id="rfc.xref.Part6.3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
    13821383      </p>
    13831384      <p id="rfc.section.5.3.1.p.7">See <a href="#encoding.sensitive.information.in.uris" title="Encoding Sensitive Information in URIs">Section&nbsp;11.2</a> for security considerations when used for forms.
     
    13901391         hypertext links for validity, accessibility, and recent modification.
    13911392      </p>
    1392       <p id="rfc.section.5.3.2.p.2">The response to a HEAD request is cacheable and <em class="bcp14">MAY</em> be used to satisfy a subsequent HEAD request. It also has potential side effects on previously stored responses to GET; see <a href="p6-cache.html#head.effects" title="Updating Caches with HEAD Responses">Section 5</a> of <a href="#Part6" id="rfc.xref.Part6.5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>.
     1393      <p id="rfc.section.5.3.2.p.2">The response to a HEAD request is cacheable and <em class="bcp14">MAY</em> be used to satisfy a subsequent HEAD request. It also has potential side effects on previously stored responses to GET; see <a href="p6-cache.html#head.effects" title="Updating Caches with HEAD Responses">Section 5</a> of <a href="#Part6" id="rfc.xref.Part6.4"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>.
    13931394      </p>
    13941395      <p id="rfc.section.5.3.2.p.3">Bodies on HEAD requests have no defined semantics. Note that sending a body on a HEAD request might cause some existing implementations
     
    14151416      <p id="rfc.section.5.3.3.p.4">If a resource has been created on the origin server, the response <em class="bcp14">SHOULD</em> be <a href="#status.201" class="smpl">201 (Created)</a> and contain a representation which describes the status of the request and refers to the new resource, and a <a href="#header.location" class="smpl">Location</a> header field (see <a href="#header.location" id="rfc.xref.header.location.1" title="Location">Section&nbsp;8.1.1</a>).
    14161417      </p>
    1417       <p id="rfc.section.5.3.3.p.5">Responses to POST requests are only cacheable when they include explicit freshness information (see <a href="p6-cache.html#calculating.freshness.lifetime" title="Calculating Freshness Lifetime">Section 4.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.6"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>). A cached POST response with a <a href="#header.content-location" class="smpl">Content-Location</a> header field (see <a href="#header.content-location" id="rfc.xref.header.content-location.2" title="Content-Location">Section&nbsp;3.2.4</a>) whose value is the effective Request URI <em class="bcp14">MAY</em> be used to satisfy subsequent GET and HEAD requests.
     1418      <p id="rfc.section.5.3.3.p.5">Responses to POST requests are only cacheable when they include explicit freshness information (see <a href="p6-cache.html#calculating.freshness.lifetime" title="Calculating Freshness Lifetime">Section 4.1.1</a> of <a href="#Part6" id="rfc.xref.Part6.5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>). A cached POST response with a <a href="#header.content-location" class="smpl">Content-Location</a> header field (see <a href="#header.content-location" id="rfc.xref.header.content-location.2" title="Content-Location">Section&nbsp;3.2.4</a>) whose value is the effective Request URI <em class="bcp14">MAY</em> be used to satisfy subsequent GET and HEAD requests.
    14181419      </p>
    14191420      <p id="rfc.section.5.3.3.p.6">Note that POST caching is not widely implemented. However, the <a href="#status.303" class="smpl">303 (See Other)</a> response can be used to direct the user agent to retrieve a cacheable representation of the resource.
     
    14811482      </p>
    14821483      <p id="rfc.section.5.3.4.p.11">Responses to the PUT method are not cacheable. If a PUT request passes through a cache that has one or more stored responses
    1483          for the effective request URI, those stored responses will be invalidated (see <a href="p6-cache.html#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section 6</a> of <a href="#Part6" id="rfc.xref.Part6.7"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
     1484         for the effective request URI, those stored responses will be invalidated (see <a href="p6-cache.html#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section 6</a> of <a href="#Part6" id="rfc.xref.Part6.6"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
    14841485      </p>
    14851486      <h3 id="rfc.section.5.3.5"><a href="#rfc.section.5.3.5">5.3.5</a>&nbsp;<a id="DELETE" href="#DELETE">DELETE</a></h3>
     
    14971498      </p>
    14981499      <p id="rfc.section.5.3.5.p.4">Responses to the DELETE method are not cacheable. If a DELETE request passes through a cache that has one or more stored responses
    1499          for the effective request URI, those stored responses will be invalidated (see <a href="p6-cache.html#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section 6</a> of <a href="#Part6" id="rfc.xref.Part6.8"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
     1500         for the effective request URI, those stored responses will be invalidated (see <a href="p6-cache.html#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section 6</a> of <a href="#Part6" id="rfc.xref.Part6.7"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
    15001501      </p>
    15011502      <div id="rfc.iref.c.7"></div>
     
    23802381         <dd>a representation containing the request message as received by the end server.</dd>
    23812382      </dl>
    2382       <p id="rfc.section.7.3.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 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.9"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 200 responses.
     2383      <p id="rfc.section.7.3.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 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.8"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 200 responses.
    23832384      </p>
    23842385      <div id="rfc.iref.80"></div>
     
    24102411      <div id="rfc.iref.s.10"></div>
    24112412      <h3 id="rfc.section.7.3.4"><a href="#rfc.section.7.3.4">7.3.4</a>&nbsp;<a id="status.203" href="#status.203">203 Non-Authoritative Information</a></h3>
    2412       <p id="rfc.section.7.3.4.p.1">The representation in the response has been transformed or otherwise modified by a transforming proxy (<a href="p1-messaging.html#intermediaries" title="Intermediaries">Section 2.3</a> of <a href="#Part1" id="rfc.xref.Part1.20"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>). Note that the behavior of transforming intermediaries is controlled by the no-transform Cache-Control directive (<a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 7.2</a> of <a href="#Part6" id="rfc.xref.Part6.10"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
     2413      <p id="rfc.section.7.3.4.p.1">The representation in the response has been transformed or otherwise modified by a transforming proxy (<a href="p1-messaging.html#intermediaries" title="Intermediaries">Section 2.3</a> of <a href="#Part1" id="rfc.xref.Part1.20"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>). Note that the behavior of transforming intermediaries is controlled by the no-transform Cache-Control directive (<a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 7.2</a> of <a href="#Part6" id="rfc.xref.Part6.9"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
    24132414      </p>
    24142415      <p id="rfc.section.7.3.4.p.2">This status code is only appropriate when the response status code would have been <a href="#status.200" class="smpl">200 (OK)</a> otherwise. When the status code before transformation would have been different, the 214 Transformation Applied warn-code
    2415          (<a href="p6-cache.html#header.warning" title="Warning">Section 7.6</a> of <a href="#Part6" id="rfc.xref.Part6.11"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) is appropriate.
    2416       </p>
    2417       <p id="rfc.section.7.3.4.p.3">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.12"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 203 responses.
     2416         (<a href="p6-cache.html#header.warning" title="Warning">Section 7.5</a> of <a href="#Part6" id="rfc.xref.Part6.10"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) is appropriate.
     2417      </p>
     2418      <p id="rfc.section.7.3.4.p.3">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.11"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 203 responses.
    24182419      </p>
    24192420      <div id="rfc.iref.83"></div>
     
    25072508      <p id="rfc.section.7.4.1.p.3">If the server has a preferred choice of representation, it <em class="bcp14">SHOULD</em> include the specific URI for that representation in the <a href="#header.location" class="smpl">Location</a> field; user agents <em class="bcp14">MAY</em> use the Location field value for automatic redirection.
    25082509      </p>
    2509       <p id="rfc.section.7.4.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 4.1.2</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 300 responses.
     2510      <p id="rfc.section.7.4.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 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.12"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 300 responses.
    25102511      </p>
    25112512      <div id="rfc.iref.87"></div>
     
    25152516         request URI to one or more of the new references returned by the server, where possible.
    25162517      </p>
    2517       <p id="rfc.section.7.4.2.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</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 301 responses.
     2518      <p id="rfc.section.7.4.2.p.2">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</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 301 responses.
    25182519      </p>
    25192520      <p id="rfc.section.7.4.2.p.3">The new permanent URI <em class="bcp14">SHOULD</em> be given by the <a href="#header.location" class="smpl">Location</a> field in the response. A response payload can contain a short hypertext note with a hyperlink to the new URI(s).
     
    26642665         — that is left to the discretion of the server owner.
    26652666      </p>
    2666       <p id="rfc.section.7.5.9.p.3">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.15"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) to determine freshness for 410 responses.
     2667      <p id="rfc.section.7.5.9.p.3">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</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 410 responses.
    26672668      </p>
    26682669      <div id="rfc.iref.103"></div>
     
    28562857            <tbody>
    28572858               <tr>
     2859                  <td class="left">Age</td>
     2860                  <td class="left"><a href="p6-cache.html#header.age" title="Age">Section 7.1</a> of <a href="#Part6" id="rfc.xref.Part6.15"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a></td>
     2861               </tr>
     2862               <tr>
    28582863                  <td class="left">Date</td>
    28592864                  <td class="left"><a href="#header.date" id="rfc.xref.header.date.1" title="Date">Section&nbsp;8.2.1</a></td>
    28602865               </tr>
    28612866               <tr>
    2862                   <td class="left">Age</td>
    2863                   <td class="left"><a href="p6-cache.html#header.age" title="Age">Section 7.1</a> of <a href="#Part6" id="rfc.xref.Part6.16"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a></td>
    2864                </tr>
    2865                <tr>
    28662867                  <td class="left">Vary</td>
    2867                   <td class="left"><a href="p6-cache.html#header.vary" title="Vary">Section 7.5</a> of <a href="#Part6" id="rfc.xref.Part6.17"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a></td>
     2868                  <td class="left"><a href="#header.vary" id="rfc.xref.header.vary.2" title="Vary">Section&nbsp;8.2.2</a></td>
    28682869               </tr>
    28692870            </tbody>
     
    29002901         value.
    29012902      </p>
     2903      <div id="rfc.iref.v.1"></div>
     2904      <div id="rfc.iref.h.18"></div>
     2905      <h3 id="rfc.section.8.2.2"><a href="#rfc.section.8.2.2">8.2.2</a>&nbsp;<a id="header.vary" href="#header.vary">Vary</a></h3>
     2906      <p id="rfc.section.8.2.2.p.1">The "Vary" header field conveys the set of header fields that were used to select the representation.</p>
     2907      <p id="rfc.section.8.2.2.p.2">Caches use this information as part of determining whether a stored response can be used to satisfy a given request (<a href="p6-cache.html#caching.negotiated.responses" title="Using Negotiated Responses">Section 4.3</a> of <a href="#Part6" id="rfc.xref.Part6.16"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
     2908      </p>
     2909      <p id="rfc.section.8.2.2.p.3">In uncacheable or stale responses, the Vary field value advises the user agent about the criteria that were used to select
     2910         the representation.
     2911      </p>
     2912      <div id="rfc.figure.u.42"></div><pre class="inline"><span id="rfc.iref.g.31"></span>  <a href="#header.vary" class="smpl">Vary</a> = "*" / 1#<a href="p1-messaging.html#header.fields" class="smpl">field-name</a>
     2913</pre><p id="rfc.section.8.2.2.p.5">The set of header fields named by the Vary field value is known as the selecting header fields.</p>
     2914      <p id="rfc.section.8.2.2.p.6">A server <em class="bcp14">SHOULD</em> include a Vary header field with any cacheable response that is subject to proactive negotiation. Doing so allows a cache
     2915         to properly interpret future requests on that resource and informs the user agent about the presence of negotiation on that
     2916         resource. A server <em class="bcp14">MAY</em> include a Vary header field with a non-cacheable response that is subject to proactive negotiation, since this might provide
     2917         the user agent with useful information about the dimensions over which the response varies at the time of the response.
     2918      </p>
     2919      <p id="rfc.section.8.2.2.p.7">A Vary field value of "*" signals that unspecified parameters not limited to the header fields (e.g., the network address
     2920         of the client), play a role in the selection of the response representation; therefore, a cache cannot determine whether this
     2921         response is appropriate. A proxy <em class="bcp14">MUST NOT</em> generate the "*" value.
     2922      </p>
     2923      <p id="rfc.section.8.2.2.p.8">The field-names given are not limited to the set of standard header fields defined by this specification. Field names are
     2924         case-insensitive.
     2925      </p>
    29022926      <h2 id="rfc.section.8.3"><a href="#rfc.section.8.3">8.3</a>&nbsp;<a id="response.auth" href="#response.auth">Authentication Challenges</a></h2>
    29032927      <p id="rfc.section.8.3.p.1">Authentication challenges indicate what mechanisms are available for the client to provide authentication credentials in future
     
    29512975      </div>
    29522976      <div id="rfc.iref.a.5"></div>
    2953       <div id="rfc.iref.h.18"></div>
     2977      <div id="rfc.iref.h.19"></div>
    29542978      <h3 id="rfc.section.8.4.1"><a href="#rfc.section.8.4.1">8.4.1</a>&nbsp;<a id="header.allow" href="#header.allow">Allow</a></h3>
    29552979      <p id="rfc.section.8.4.1.p.1">The "Allow" header field lists the set of methods advertised as supported by the target resource. The purpose of this field
    29562980         is strictly to inform the recipient of valid request methods associated with the resource.
    29572981      </p>
    2958       <div id="rfc.figure.u.42"></div><pre class="inline"><span id="rfc.iref.g.31"></span>  <a href="#header.allow" class="smpl">Allow</a> = #<a href="#method.overview" class="smpl">method</a>
     2982      <div id="rfc.figure.u.43"></div><pre class="inline"><span id="rfc.iref.g.32"></span>  <a href="#header.allow" class="smpl">Allow</a> = #<a href="#method.overview" class="smpl">method</a>
    29592983</pre><p id="rfc.section.8.4.1.p.3">Example of use:</p>
    2960       <div id="rfc.figure.u.43"></div><pre class="text">  Allow: GET, HEAD, PUT
     2984      <div id="rfc.figure.u.44"></div><pre class="text">  Allow: GET, HEAD, PUT
    29612985</pre><p id="rfc.section.8.4.1.p.5">The actual set of allowed methods is defined by the origin server at the time of each request.</p>
    29622986      <p id="rfc.section.8.4.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
     
    29642988      </p>
    29652989      <div id="rfc.iref.s.44"></div>
    2966       <div id="rfc.iref.h.19"></div>
     2990      <div id="rfc.iref.h.20"></div>
    29672991      <h3 id="rfc.section.8.4.2"><a href="#rfc.section.8.4.2">8.4.2</a>&nbsp;<a id="header.server" href="#header.server">Server</a></h3>
    29682992      <p id="rfc.section.8.4.2.p.1">The "Server" header field contains information about the software used by the origin server to handle the request.</p>
     
    29702994         identifying the application.
    29712995      </p>
    2972       <div id="rfc.figure.u.44"></div><pre class="inline"><span id="rfc.iref.g.32"></span>  <a href="#header.server" class="smpl">Server</a> = <a href="#product.tokens" class="smpl">product</a> *( <a href="#imported.abnf" class="smpl">RWS</a> ( <a href="#product.tokens" class="smpl">product</a> / <a href="#imported.abnf" class="smpl">comment</a> ) )
     2996      <div id="rfc.figure.u.45"></div><pre class="inline"><span id="rfc.iref.g.33"></span>  <a href="#header.server" class="smpl">Server</a> = <a href="#product.tokens" class="smpl">product</a> *( <a href="#imported.abnf" class="smpl">RWS</a> ( <a href="#product.tokens" class="smpl">product</a> / <a href="#imported.abnf" class="smpl">comment</a> ) )
    29732997</pre><p id="rfc.section.8.4.2.p.4">Example:</p>
    2974       <div id="rfc.figure.u.45"></div><pre class="text">  Server: CERN/3.0 libwww/2.17
     2998      <div id="rfc.figure.u.46"></div><pre class="text">  Server: CERN/3.0 libwww/2.17
    29752999</pre><p id="rfc.section.8.4.2.p.6">If the response is being forwarded through a proxy, the proxy application <em class="bcp14">MUST NOT</em> modify the <a href="#header.server" class="smpl">Server</a> header field. Instead, it <em class="bcp14">MUST</em> include a <a href="p1-messaging.html#header.via" class="smpl">Via</a> field (as described in <a href="p1-messaging.html#header.via" title="Via">Section 5.7</a> of <a href="#Part1" id="rfc.xref.Part1.26"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>).
    29763000      </p>
     
    29863010         a fixed-length subset of that defined by <a href="#RFC1123" id="rfc.xref.RFC1123.1"><cite title="Requirements for Internet Hosts - Application and Support">[RFC1123]</cite></a>:
    29873011      </p>
    2988       <div id="rfc.figure.u.46"></div><pre class="text">Sun, 06 Nov 1994 08:49:37 GMT  ; RFC 1123
     3012      <div id="rfc.figure.u.47"></div><pre class="text">Sun, 06 Nov 1994 08:49:37 GMT  ; RFC 1123
    29893013</pre><p id="rfc.section.9.1.p.3">The other formats are described here only for compatibility with obsolete implementations.</p>
    2990       <div id="rfc.figure.u.47"></div><pre class="text">Sunday, 06-Nov-94 08:49:37 GMT ; obsolete RFC 850 format
     3014      <div id="rfc.figure.u.48"></div><pre class="text">Sunday, 06-Nov-94 08:49:37 GMT ; obsolete RFC 850 format
    29913015Sun Nov  6 08:49:37 1994       ; ANSI C's asctime() format
    29923016</pre><p id="rfc.section.9.1.p.5">HTTP/1.1 clients and servers that parse a date value <em class="bcp14">MUST</em> accept all three formats (for compatibility with HTTP/1.0), though they <em class="bcp14">MUST</em> only generate the RFC 1123 format for representing HTTP-date values in header fields.
     
    29963020         time zone, and <em class="bcp14">MUST</em> be assumed when reading the asctime format. HTTP-date is case sensitive and <em class="bcp14">MUST NOT</em> include additional whitespace beyond that specifically included as SP in the grammar.
    29973021      </p>
    2998       <div id="rfc.figure.u.48"></div><pre class="inline"><span id="rfc.iref.g.33"></span>  <a href="#http.date" class="smpl">HTTP-date</a>    = <a href="#preferred.date.format" class="smpl">rfc1123-date</a> / <a href="#obsolete.date.formats" class="smpl">obs-date</a>
     3022      <div id="rfc.figure.u.49"></div><pre class="inline"><span id="rfc.iref.g.34"></span>  <a href="#http.date" class="smpl">HTTP-date</a>    = <a href="#preferred.date.format" class="smpl">rfc1123-date</a> / <a href="#obsolete.date.formats" class="smpl">obs-date</a>
    29993023</pre><div id="preferred.date.format">
    30003024         <p id="rfc.section.9.1.p.8">                    Preferred format:</p>
    30013025      </div>
    3002       <div id="rfc.figure.u.49"></div><pre class="inline"><span id="rfc.iref.g.34"></span><span id="rfc.iref.g.35"></span><span id="rfc.iref.g.36"></span><span id="rfc.iref.g.37"></span><span id="rfc.iref.g.38"></span><span id="rfc.iref.g.39"></span><span id="rfc.iref.g.40"></span><span id="rfc.iref.g.41"></span><span id="rfc.iref.g.42"></span><span id="rfc.iref.g.43"></span><span id="rfc.iref.g.44"></span><span id="rfc.iref.g.45"></span>  <a href="#preferred.date.format" class="smpl">rfc1123-date</a> = <a href="#preferred.date.format" class="smpl">day-name</a> "," <a href="#imported.abnf" class="smpl">SP</a> date1 <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">GMT</a>
     3026      <div id="rfc.figure.u.50"></div><pre class="inline"><span id="rfc.iref.g.35"></span><span id="rfc.iref.g.36"></span><span id="rfc.iref.g.37"></span><span id="rfc.iref.g.38"></span><span id="rfc.iref.g.39"></span><span id="rfc.iref.g.40"></span><span id="rfc.iref.g.41"></span><span id="rfc.iref.g.42"></span><span id="rfc.iref.g.43"></span><span id="rfc.iref.g.44"></span><span id="rfc.iref.g.45"></span><span id="rfc.iref.g.46"></span>  <a href="#preferred.date.format" class="smpl">rfc1123-date</a> = <a href="#preferred.date.format" class="smpl">day-name</a> "," <a href="#imported.abnf" class="smpl">SP</a> date1 <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">GMT</a>
    30033027  ; fixed length subset of the format defined in
    30043028  ; <a href="http://tools.ietf.org/html/rfc1123#section-5.2.14">Section 5.2.14</a> of <a href="#RFC1123" id="rfc.xref.RFC1123.2"><cite title="Requirements for Internet Hosts - Application and Support">[RFC1123]</cite></a>
     
    30433067         <p id="rfc.section.9.1.p.11">              Obsolete formats:</p>
    30443068      </div>
    3045       <div id="rfc.figure.u.50"></div><pre class="inline"><span id="rfc.iref.g.46"></span>  <a href="#obsolete.date.formats" class="smpl">obs-date</a>     = <a href="#obsolete.date.formats" class="smpl">rfc850-date</a> / <a href="#obsolete.date.formats" class="smpl">asctime-date</a>
    3046 </pre><div id="rfc.figure.u.51"></div><pre class="inline"><span id="rfc.iref.g.47"></span>  <a href="#obsolete.date.formats" class="smpl">rfc850-date</a>  = <a href="#obsolete.date.formats" class="smpl">day-name-l</a> "," <a href="#imported.abnf" class="smpl">SP</a> <a href="#obsolete.date.formats" class="smpl">date2</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">GMT</a>
     3069      <div id="rfc.figure.u.51"></div><pre class="inline"><span id="rfc.iref.g.47"></span>  <a href="#obsolete.date.formats" class="smpl">obs-date</a>     = <a href="#obsolete.date.formats" class="smpl">rfc850-date</a> / <a href="#obsolete.date.formats" class="smpl">asctime-date</a>
     3070</pre><div id="rfc.figure.u.52"></div><pre class="inline"><span id="rfc.iref.g.48"></span>  <a href="#obsolete.date.formats" class="smpl">rfc850-date</a>  = <a href="#obsolete.date.formats" class="smpl">day-name-l</a> "," <a href="#imported.abnf" class="smpl">SP</a> <a href="#obsolete.date.formats" class="smpl">date2</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">GMT</a>
    30473071  <a href="#obsolete.date.formats" class="smpl">date2</a>        = <a href="#preferred.date.format" class="smpl">day</a> "-" <a href="#preferred.date.format" class="smpl">month</a> "-" 2<a href="#imported.abnf" class="smpl">DIGIT</a>
    30483072                 ; day-month-year (e.g., 02-Jun-82)
     
    30553079         / %x53.61.74.75.72.64.61.79 ; "Saturday", case-sensitive
    30563080         / %x53.75.6E.64.61.79 ; "Sunday", case-sensitive
    3057 </pre><div id="rfc.figure.u.52"></div><pre class="inline"><span id="rfc.iref.g.48"></span>  <a href="#obsolete.date.formats" class="smpl">asctime-date</a> = <a href="#preferred.date.format" class="smpl">day-name</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#obsolete.date.formats" class="smpl">date3</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">year</a>
     3081</pre><div id="rfc.figure.u.53"></div><pre class="inline"><span id="rfc.iref.g.49"></span>  <a href="#obsolete.date.formats" class="smpl">asctime-date</a> = <a href="#preferred.date.format" class="smpl">day-name</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#obsolete.date.formats" class="smpl">date3</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">year</a>
    30583082  <a href="#obsolete.date.formats" class="smpl">date3</a>        = <a href="#preferred.date.format" class="smpl">month</a> <a href="#imported.abnf" class="smpl">SP</a> ( 2<a href="#imported.abnf" class="smpl">DIGIT</a> / ( <a href="#imported.abnf" class="smpl">SP</a> 1<a href="#imported.abnf" class="smpl">DIGIT</a> ))
    30593083                 ; month day (e.g., Jun  2)
     
    30733097         By convention, the products are listed in order of their significance for identifying the application.
    30743098      </p>
    3075       <div id="rfc.figure.u.53"></div><pre class="inline"><span id="rfc.iref.g.49"></span><span id="rfc.iref.g.50"></span>  <a href="#product.tokens" class="smpl">product</a>         = <a href="#imported.abnf" class="smpl">token</a> ["/" <a href="#product.tokens" class="smpl">product-version</a>]
     3099      <div id="rfc.figure.u.54"></div><pre class="inline"><span id="rfc.iref.g.50"></span><span id="rfc.iref.g.51"></span>  <a href="#product.tokens" class="smpl">product</a>         = <a href="#imported.abnf" class="smpl">token</a> ["/" <a href="#product.tokens" class="smpl">product-version</a>]
    30763100  <a href="#product.tokens" class="smpl">product-version</a> = <a href="#imported.abnf" class="smpl">token</a>
    30773101</pre><p id="rfc.section.9.2.p.3">Examples:</p>
    3078       <div id="rfc.figure.u.54"></div><pre class="text">  User-Agent: CERN-LineMode/2.15 libwww/2.17b3
     3102      <div id="rfc.figure.u.55"></div><pre class="text">  User-Agent: CERN-LineMode/2.15 libwww/2.17b3
    30793103  Server: Apache/0.8.4
    30803104</pre><p id="rfc.section.9.2.p.5">Product tokens <em class="bcp14">SHOULD</em> be short and to the point. They <em class="bcp14">MUST NOT</em> be used for advertising or other non-essential information. Although any token octet <em class="bcp14">MAY</em> appear in a product-version, this token <em class="bcp14">SHOULD</em> only be used for a version identifier (i.e., successive versions of the same product <em class="bcp14">SHOULD</em> only differ in the product-version portion of the product value).
     
    30873111         </p>
    30883112      </div>
    3089       <div id="rfc.figure.u.55"></div><pre class="inline"><span id="rfc.iref.g.51"></span>  <a href="#rule.charset" class="smpl">charset</a> = <a href="#imported.abnf" class="smpl">token</a>
     3113      <div id="rfc.figure.u.56"></div><pre class="inline"><span id="rfc.iref.g.52"></span>  <a href="#rule.charset" class="smpl">charset</a> = <a href="#imported.abnf" class="smpl">token</a>
    30903114</pre><p id="rfc.section.9.3.p.4">Although HTTP allows an arbitrary token to be used as a charset value, any token that has a predefined value within the IANA
    30913115         Character Set registry <em class="bcp14">MUST</em> represent the character encoding defined by that registry. Applications <em class="bcp14">SHOULD</em> limit their use of character encodings to those defined within the IANA registry.
     
    31013125         directly, and only decoded by the recipient.
    31023126      </p>
    3103       <div id="rfc.figure.u.56"></div><pre class="inline"><span id="rfc.iref.g.52"></span>  <a href="#content.codings" class="smpl">content-coding</a>   = <a href="#imported.abnf" class="smpl">token</a>
     3127      <div id="rfc.figure.u.57"></div><pre class="inline"><span id="rfc.iref.g.53"></span>  <a href="#content.codings" class="smpl">content-coding</a>   = <a href="#imported.abnf" class="smpl">token</a>
    31043128</pre><p id="rfc.section.9.4.p.3">All content-coding values are case-insensitive. HTTP/1.1 uses content-coding values in the <a href="#header.accept-encoding" class="smpl">Accept-Encoding</a> (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.3" title="Accept-Encoding">Section&nbsp;6.3.4</a>) and <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;3.2.2</a>) header fields. Although the value describes the content-coding, what is more important is that it indicates what decoding
    31053129         mechanism will be required to remove the encoding.
     
    31173141         </li>
    31183142      </ul>
    3119       <p id="rfc.section.9.4.p.6">gzip<span id="rfc.iref.g.53"></span><span id="rfc.iref.c.11"></span> 
     3143      <p id="rfc.section.9.4.p.6">gzip<span id="rfc.iref.g.54"></span><span id="rfc.iref.c.11"></span> 
    31203144      </p>
    31213145      <ul class="empty">
     
    31263150      <p id="rfc.section.9.5.p.1">HTTP uses Internet Media Types <a href="#RFC2046" id="rfc.xref.RFC2046.2"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> in the <a href="#header.content-type" class="smpl">Content-Type</a> (<a href="#header.content-type" id="rfc.xref.header.content-type.3" title="Content-Type">Section&nbsp;3.2.1</a>) and <a href="#header.accept" class="smpl">Accept</a> (<a href="#header.accept" id="rfc.xref.header.accept.3" title="Accept">Section&nbsp;6.3.2</a>) header fields in order to provide open and extensible data typing and type negotiation.
    31273151      </p>
    3128       <div id="rfc.figure.u.57"></div><pre class="inline"><span id="rfc.iref.g.54"></span><span id="rfc.iref.g.55"></span><span id="rfc.iref.g.56"></span>  <a href="#media.types" class="smpl">media-type</a> = <a href="#media.types" class="smpl">type</a> "/" <a href="#media.types" class="smpl">subtype</a> *( <a href="#imported.abnf" class="smpl">OWS</a> ";" <a href="#imported.abnf" class="smpl">OWS</a> <a href="#rule.parameter" class="smpl">parameter</a> )
     3152      <div id="rfc.figure.u.58"></div><pre class="inline"><span id="rfc.iref.g.55"></span><span id="rfc.iref.g.56"></span><span id="rfc.iref.g.57"></span>  <a href="#media.types" class="smpl">media-type</a> = <a href="#media.types" class="smpl">type</a> "/" <a href="#media.types" class="smpl">subtype</a> *( <a href="#imported.abnf" class="smpl">OWS</a> ";" <a href="#imported.abnf" class="smpl">OWS</a> <a href="#rule.parameter" class="smpl">parameter</a> )
    31293153  <a href="#media.types" class="smpl">type</a>       = <a href="#imported.abnf" class="smpl">token</a>
    31303154  <a href="#media.types" class="smpl">subtype</a>    = <a href="#imported.abnf" class="smpl">token</a>
     
    31333157         </p>
    31343158      </div>
    3135       <div id="rfc.figure.u.58"></div><pre class="inline"><span id="rfc.iref.g.57"></span><span id="rfc.iref.g.58"></span><span id="rfc.iref.g.59"></span>  <a href="#rule.parameter" class="smpl">parameter</a>      = <a href="#rule.parameter" class="smpl">attribute</a> "=" <a href="#rule.parameter" class="smpl">value</a>
     3159      <div id="rfc.figure.u.59"></div><pre class="inline"><span id="rfc.iref.g.58"></span><span id="rfc.iref.g.59"></span><span id="rfc.iref.g.60"></span>  <a href="#rule.parameter" class="smpl">parameter</a>      = <a href="#rule.parameter" class="smpl">attribute</a> "=" <a href="#rule.parameter" class="smpl">value</a>
    31363160  <a href="#rule.parameter" class="smpl">attribute</a>      = <a href="#imported.abnf" class="smpl">token</a>
    31373161  <a href="#rule.parameter" class="smpl">value</a>          = <a href="#imported.abnf" class="smpl">word</a>
     
    31833207         of subtags:
    31843208      </p>
    3185       <div id="rfc.figure.u.59"></div><pre class="inline"><span id="rfc.iref.g.60"></span>  <a href="#language.tags" class="smpl">language-tag</a> = &lt;Language-Tag, defined in <a href="#RFC5646" id="rfc.xref.RFC5646.2"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a>, <a href="http://tools.ietf.org/html/rfc5646#section-2.1">Section 2.1</a>&gt;
     3209      <div id="rfc.figure.u.60"></div><pre class="inline"><span id="rfc.iref.g.61"></span>  <a href="#language.tags" class="smpl">language-tag</a> = &lt;Language-Tag, defined in <a href="#RFC5646" id="rfc.xref.RFC5646.2"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a>, <a href="http://tools.ietf.org/html/rfc5646#section-2.1">Section 2.1</a>&gt;
    31863210</pre><p id="rfc.section.9.6.p.4">White space is not allowed within the tag and all tags are case-insensitive. The name space of language subtags is administered
    31873211         by the IANA (see &lt;<a href="http://www.iana.org/assignments/language-subtag-registry">http://www.iana.org/assignments/language-subtag-registry</a>&gt;).
    31883212      </p>
    3189       <div id="rfc.figure.u.60"></div>
     3213      <div id="rfc.figure.u.61"></div>
    31903214      <p>Example tags include:</p>  <pre class="text">  en, en-US, es-419, az-Arab, x-pig-latin, man-Nkoo-GN
    31913215</pre> <p id="rfc.section.9.6.p.6">See <a href="#RFC5646" id="rfc.xref.RFC5646.3"><cite title="Tags for Identifying Languages">[RFC5646]</cite></a> for further information.
     
    33193343         a zero-length response body. They can require the presence of one or more particular HTTP response header field(s).
    33203344      </p>
    3321       <p id="rfc.section.10.2.2.p.5">Likewise, their definitions can specify that caches are allowed to use heuristics to determine their freshness (see <a href="#Part6" id="rfc.xref.Part6.18"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>; by default, it is not allowed), and can define how to determine the resource which they carry a representation for (see <a href="#identifying.response.associated.with.representation" title="Identifying the Resource Associated with a Representation">Section&nbsp;3.1</a>; by default, it is anonymous).
     3345      <p id="rfc.section.10.2.2.p.5">Likewise, their definitions can specify that caches are allowed to use heuristics to determine their freshness (see <a href="#Part6" id="rfc.xref.Part6.17"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>; by default, it is not allowed), and can define how to determine the resource which they carry a representation for (see <a href="#identifying.response.associated.with.representation" title="Identifying the Resource Associated with a Representation">Section&nbsp;3.1</a>; by default, it is anonymous).
    33223346      </p>
    33233347      <h3 id="rfc.section.10.2.3"><a href="#rfc.section.10.2.3">10.2.3</a>&nbsp;<a id="status.code.registration" href="#status.code.registration">Registrations</a></h3>
     
    35733597         these:
    35743598      </p>
    3575       <div id="rfc.figure.u.61"></div><pre class="text">  Example-URI-Field: "http://example.com/a.html,foo",
     3599      <div id="rfc.figure.u.62"></div><pre class="text">  Example-URI-Field: "http://example.com/a.html,foo",
    35763600                     "http://without-a-comma.example.com/"
    35773601  Example-Date-Field: "Sat, 04 May 1996", "Wed, 14 Sep 2005"
     
    36093633         </li>
    36103634         <li>
    3611             <p>How the header field might interact with caching (see <a href="#Part6" id="rfc.xref.Part6.19"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
     3635            <p>How the header field might interact with caching (see <a href="#Part6" id="rfc.xref.Part6.18"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).
    36123636            </p>
    36133637         </li>
     
    37653789                  <td class="left">standard</td>
    37663790                  <td class="left"> <a href="#header.user-agent" id="rfc.xref.header.user-agent.3" title="User-Agent">Section&nbsp;6.5.3</a>
     3791                  </td>
     3792               </tr>
     3793               <tr>
     3794                  <td class="left">Vary</td>
     3795                  <td class="left">http</td>
     3796                  <td class="left">standard</td>
     3797                  <td class="left"> <a href="#header.vary" id="rfc.xref.header.vary.3" title="Vary">Section&nbsp;8.2.2</a>
    37673798                  </td>
    37683799               </tr>
     
    38953926      <p id="rfc.section.11.5.p.2">An approach that limits the loss of privacy would be for a user agent to omit the sending of Accept-Language header fields
    38963927         by default, and to ask the user whether or not to start sending Accept-Language header fields to a server if it detects, by
    3897          looking for any <a href="p6-cache.html#header.vary" class="smpl">Vary</a> header fields generated by the server, that such sending could improve the quality of service.
     3928         looking for any <a href="#header.vary" class="smpl">Vary</a> header fields generated by the server, that such sending could improve the quality of service.
    38983929      </p>
    38993930      <p id="rfc.section.11.5.p.3">Elaborate user-customized accept header fields sent in every request, in particular if these include quality values, can be
     
    41264157      </p>
    41274158      <div id="rfc.iref.m.10"></div>
    4128       <div id="rfc.iref.h.20"></div>
     4159      <div id="rfc.iref.h.21"></div>
    41294160      <h2 id="rfc.section.A.1"><a href="#rfc.section.A.1">A.1</a>&nbsp;<a id="mime-version" href="#mime-version">MIME-Version</a></h2>
    41304161      <p id="rfc.section.A.1.p.1">HTTP is not a MIME-compliant protocol. However, HTTP/1.1 messages <em class="bcp14">MAY</em> include a single MIME-Version header field to indicate what version of the MIME protocol was used to construct the message.
     
    41334164         MIME environments.
    41344165      </p>
    4135       <div id="rfc.figure.u.62"></div><pre class="inline"><span id="rfc.iref.g.61"></span>  <a href="#mime-version" class="smpl">MIME-Version</a> = 1*<a href="#imported.abnf" class="smpl">DIGIT</a> "." 1*<a href="#imported.abnf" class="smpl">DIGIT</a>
     4166      <div id="rfc.figure.u.63"></div><pre class="inline"><span id="rfc.iref.g.62"></span>  <a href="#mime-version" class="smpl">MIME-Version</a> = 1*<a href="#imported.abnf" class="smpl">DIGIT</a> "." 1*<a href="#imported.abnf" class="smpl">DIGIT</a>
    41364167</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
    41374168         document and not the MIME specification.
     
    41584189      </p>
    41594190      <div id="rfc.iref.c.12"></div>
    4160       <div id="rfc.iref.h.21"></div>
     4191      <div id="rfc.iref.h.22"></div>
    41614192      <h2 id="rfc.section.A.5"><a href="#rfc.section.A.5">A.5</a>&nbsp;<a id="no.content-transfer-encoding" href="#no.content-transfer-encoding">No Content-Transfer-Encoding</a></h2>
    41624193      <p id="rfc.section.A.5.p.1">HTTP does not use the Content-Transfer-Encoding field of MIME. Proxies and gateways from MIME-compliant protocols to HTTP <em class="bcp14">MUST</em> remove any Content-Transfer-Encoding prior to delivering the response message to an HTTP client.
     
    42484279      <p id="rfc.section.D.p.2">The rules below are defined in <a href="#Part1" id="rfc.xref.Part1.45"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>:
    42494280      </p>
    4250       <div id="rfc.figure.u.63"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">BWS</a>           = &lt;BWS, defined in <a href="#Part1" id="rfc.xref.Part1.46"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.1</a>&gt;
     4281      <div id="rfc.figure.u.64"></div><pre class="inline">  <a href="#imported.abnf" class="smpl">BWS</a>           = &lt;BWS, defined in <a href="#Part1" id="rfc.xref.Part1.46"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.1</a>&gt;
    42514282  <a href="#imported.abnf" class="smpl">OWS</a>           = &lt;OWS, defined in <a href="#Part1" id="rfc.xref.Part1.47"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.1</a>&gt;
    42524283  <a href="#imported.abnf" class="smpl">RWS</a>           = &lt;RWS, defined in <a href="#Part1" id="rfc.xref.Part1.48"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.1</a>&gt;
     
    42604291  <a href="#imported.abnf" class="smpl">URI-reference</a> = &lt;URI-reference, defined in <a href="#Part1" id="rfc.xref.Part1.55"><cite title="HTTP/1.1, part 1: Message Routing and Syntax&#34;">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.7</a>&gt;
    42614292</pre><h1 id="rfc.section.E"><a href="#rfc.section.E">E.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
    4262       <div id="rfc.figure.u.64"></div> <pre class="inline"><a href="#header.accept" class="smpl">Accept</a> = [ ( "," / ( media-range [ accept-params ] ) ) *( OWS "," [
     4293      <div id="rfc.figure.u.65"></div> <pre class="inline"><a href="#header.accept" class="smpl">Accept</a> = [ ( "," / ( media-range [ accept-params ] ) ) *( OWS "," [
    42634294 OWS ( media-range [ accept-params ] ) ] ) ]
    42644295<a href="#header.accept-charset" class="smpl">Accept-Charset</a> = *( "," OWS ) ( ( charset / "*" ) [ weight ] ) *( OWS
     
    43054336<a href="#header.user-agent" class="smpl">User-Agent</a> = product *( RWS ( product / comment ) )
    43064337
     4338<a href="#header.vary" class="smpl">Vary</a> = "*" / ( *( "," OWS ) field-name *( OWS "," [ OWS field-name ]
     4339 ) )
     4340
    43074341<a href="#imported.abnf" class="smpl">absolute-URI</a> = &lt;absolute-URI, defined in [Part1], Section 2.7&gt;
     4342
    43084343<a href="#header.accept" class="smpl">accept-ext</a> = OWS ";" OWS token [ "=" word ]
    43094344<a href="#header.accept" class="smpl">accept-params</a> = weight *accept-ext
     
    43124347
    43134348<a href="#rule.charset" class="smpl">charset</a> = token
     4349
    43144350<a href="#header.accept-encoding" class="smpl">codings</a> = content-coding / "identity" / "*"
    43154351<a href="#imported.abnf" class="smpl">comment</a> = &lt;comment, defined in [Part1], Section 3.2.4&gt;
     
    43174353
    43184354<a href="#obsolete.date.formats" class="smpl">date1</a> = day SP month SP year
     4355
    43194356<a href="#obsolete.date.formats" class="smpl">date2</a> = day "-" month "-" 2DIGIT
    43204357<a href="#obsolete.date.formats" class="smpl">date3</a> = month SP ( 2DIGIT / ( SP DIGIT ) )
     
    43374374
    43384375<a href="#header.expect" class="smpl">expect-name</a> = token
     4376
    43394377<a href="#header.expect" class="smpl">expect-param</a> = expect-name [ BWS "=" BWS expect-value ]
    43404378<a href="#header.expect" class="smpl">expect-value</a> = token / quoted-string
     
    43454383
    43464384<a href="#header.accept-language" class="smpl">language-range</a> = &lt;language-range, defined in [RFC4647], Section 2.1&gt;
     4385
    43474386<a href="#language.tags" class="smpl">language-tag</a> = &lt;Language-Tag, defined in [RFC5646], Section 2.1&gt;
    43484387
    43494388<a href="#header.from" class="smpl">mailbox</a> = &lt;mailbox, defined in [RFC5322], Section 3.4&gt;
     4389
    43504390<a href="#header.accept" class="smpl">media-range</a> = ( "*/*" / ( type "/*" ) / ( type "/" subtype ) ) *( OWS
    43514391 ";" OWS parameter )
     
    43694409
    43704410<a href="#rule.parameter" class="smpl">parameter</a> = attribute "=" value
     4411
    43714412<a href="#imported.abnf" class="smpl">partial-URI</a> = &lt;partial-URI, defined in [Part1], Section 2.7&gt;
    43724413<a href="#product.tokens" class="smpl">product</a> = token [ "/" product-version ]
     
    43744415
    43754416<a href="#imported.abnf" class="smpl">quoted-string</a> = &lt;quoted-string, defined in [Part1], Section 3.2.4&gt;
     4417
    43764418<a href="#quality.values" class="smpl">qvalue</a> = ( "0" [ "." *3DIGIT ] ) / ( "1" [ "." *3"0" ] )
    43774419
    43784420<a href="#preferred.date.format" class="smpl">rfc1123-date</a> = day-name "," SP date1 SP time-of-day SP GMT
     4421
    43794422<a href="#obsolete.date.formats" class="smpl">rfc850-date</a> = day-name-l "," SP date2 SP time-of-day SP GMT
    43804423
    43814424<a href="#preferred.date.format" class="smpl">second</a> = 2DIGIT
     4425
    43824426<a href="#media.types" class="smpl">subtype</a> = token
    43834427
    43844428<a href="#preferred.date.format" class="smpl">time-of-day</a> = hour ":" minute ":" second
     4429
    43854430<a href="#imported.abnf" class="smpl">token</a> = &lt;token, defined in [Part1], Section 3.2.4&gt;
    43864431<a href="#media.types" class="smpl">type</a> = token
     
    43894434
    43904435<a href="#quality.values" class="smpl">weight</a> = OWS ";" OWS "q=" qvalue
     4436
    43914437<a href="#imported.abnf" class="smpl">word</a> = &lt;word, defined in [Part1], Section 3.2.4&gt;
    43924438
    43934439<a href="#preferred.date.format" class="smpl">year</a> = 4DIGIT
    4394 </pre> <h1 id="rfc.section.F"><a href="#rfc.section.F">F.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
     4440</pre> <div id="rfc.figure.u.66"></div>
     4441      <p>ABNF diagnostics:</p><pre class="inline">; field-name UNDEFINED
     4442</pre><h1 id="rfc.section.F"><a href="#rfc.section.F">F.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
    43954443      <h2 id="rfc.section.F.1"><a href="#rfc.section.F.1">F.1</a>&nbsp;Since RFC 2616
    43964444      </h2>
     
    49595007      <p id="rfc.section.F.41.p.1">None yet.</p>
    49605008      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    4961       <p class="noprint"><a href="#rfc.index.1">1</a> <a href="#rfc.index.2">2</a> <a href="#rfc.index.3">3</a> <a href="#rfc.index.4">4</a> <a href="#rfc.index.5">5</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.F">F</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.L">L</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.O">O</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.T">T</a> <a href="#rfc.index.U">U</a>
     5009      <p class="noprint"><a href="#rfc.index.1">1</a> <a href="#rfc.index.2">2</a> <a href="#rfc.index.3">3</a> <a href="#rfc.index.4">4</a> <a href="#rfc.index.5">5</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.F">F</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.L">L</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.O">O</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.T">T</a> <a href="#rfc.index.U">U</a> <a href="#rfc.index.V">V</a>
    49625010      </p>
    49635011      <div class="print2col">
     
    50765124                        <li><tt>Accept-Language</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.22"><b>6.3.5</b></a></li>
    50775125                        <li><tt>accept-params</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.17"><b>6.3.2</b></a></li>
    5078                         <li><tt>Allow</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.31"><b>8.4.1</b></a></li>
    5079                         <li><tt>asctime-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.48"><b>9.1</b></a></li>
    5080                         <li><tt>attribute</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.58"><b>9.5</b></a></li>
    5081                         <li><tt>charset</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.51"><b>9.3</b></a></li>
     5126                        <li><tt>Allow</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.32"><b>8.4.1</b></a></li>
     5127                        <li><tt>asctime-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.49"><b>9.1</b></a></li>
     5128                        <li><tt>attribute</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.59"><b>9.5</b></a></li>
     5129                        <li><tt>charset</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.52"><b>9.3</b></a></li>
    50825130                        <li><tt>codings</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.21"><b>6.3.4</b></a></li>
    5083                         <li><tt>content-coding</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.52"><b>9.4</b></a></li>
     5131                        <li><tt>content-coding</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.53"><b>9.4</b></a></li>
    50845132                        <li><tt>Content-Encoding</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.2"><b>3.2.2</b></a></li>
    50855133                        <li><tt>Content-Language</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.3"><b>3.2.3</b></a></li>
     
    50875135                        <li><tt>Content-Type</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.1"><b>3.2.1</b></a></li>
    50885136                        <li><tt>Date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.30"><b>8.2.1</b></a></li>
    5089                         <li><tt>date1</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.35"><b>9.1</b></a></li>
    5090                         <li><tt>day</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.42"><b>9.1</b></a></li>
    5091                         <li><tt>day-name</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.40"><b>9.1</b></a></li>
    5092                         <li><tt>day-name-l</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.41"><b>9.1</b></a></li>
     5137                        <li><tt>date1</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.36"><b>9.1</b></a></li>
     5138                        <li><tt>day</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.43"><b>9.1</b></a></li>
     5139                        <li><tt>day-name</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.41"><b>9.1</b></a></li>
     5140                        <li><tt>day-name-l</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.42"><b>9.1</b></a></li>
    50935141                        <li><tt>delta-seconds</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.29"><b>8.1.2</b></a></li>
    50945142                        <li><tt>Expect</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.8"><b>6.1.2</b></a></li>
     
    50985146                        <li><tt>expectation</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.9"><b>6.1.2</b></a></li>
    50995147                        <li><tt>From</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.24"><b>6.5.1</b></a></li>
    5100                         <li><tt>GMT</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.45"><b>9.1</b></a></li>
    5101                         <li><tt>hour</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.37"><b>9.1</b></a></li>
    5102                         <li><tt>HTTP-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.33"><b>9.1</b></a></li>
     5148                        <li><tt>GMT</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.46"><b>9.1</b></a></li>
     5149                        <li><tt>hour</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.38"><b>9.1</b></a></li>
     5150                        <li><tt>HTTP-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.34"><b>9.1</b></a></li>
    51035151                        <li><tt>language-range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.23"><b>6.3.5</b></a></li>
    5104                         <li><tt>language-tag</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.60"><b>9.6</b></a></li>
     5152                        <li><tt>language-tag</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.61"><b>9.6</b></a></li>
    51055153                        <li><tt>Location</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.27"><b>8.1.1</b></a></li>
    51065154                        <li><tt>Max-Forwards</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.7"><b>6.1.1</b></a></li>
    51075155                        <li><tt>media-range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.16"><b>6.3.2</b></a></li>
    5108                         <li><tt>media-type</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.54"><b>9.5</b></a></li>
     5156                        <li><tt>media-type</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.55"><b>9.5</b></a></li>
    51095157                        <li><tt>method</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.5"><b>5.1</b></a></li>
    5110                         <li><tt>MIME-Version</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.61"><b>A.1</b></a></li>
    5111                         <li><tt>minute</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.38"><b>9.1</b></a></li>
    5112                         <li><tt>month</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.43"><b>9.1</b></a></li>
    5113                         <li><tt>obs-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.46"><b>9.1</b></a></li>
    5114                         <li><tt>parameter</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.57"><b>9.5</b></a></li>
    5115                         <li><tt>product</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.49"><b>9.2</b></a></li>
    5116                         <li><tt>product-version</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.50"><b>9.2</b></a></li>
     5158                        <li><tt>MIME-Version</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.62"><b>A.1</b></a></li>
     5159                        <li><tt>minute</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.39"><b>9.1</b></a></li>
     5160                        <li><tt>month</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.44"><b>9.1</b></a></li>
     5161                        <li><tt>obs-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.47"><b>9.1</b></a></li>
     5162                        <li><tt>parameter</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.58"><b>9.5</b></a></li>
     5163                        <li><tt>product</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.50"><b>9.2</b></a></li>
     5164                        <li><tt>product-version</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.51"><b>9.2</b></a></li>
    51175165                        <li><tt>qvalue</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.14"><b>6.3.1</b></a></li>
    51185166                        <li><tt>Referer</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.25"><b>6.5.2</b></a></li>
    51195167                        <li><tt>Retry-After</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.28"><b>8.1.2</b></a></li>
    5120                         <li><tt>rfc1123-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.34"><b>9.1</b></a></li>
    5121                         <li><tt>rfc850-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.47"><b>9.1</b></a></li>
    5122                         <li><tt>second</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.39"><b>9.1</b></a></li>
    5123                         <li><tt>Server</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.32"><b>8.4.2</b></a></li>
    5124                         <li><tt>subtype</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.56"><b>9.5</b></a></li>
    5125                         <li><tt>time-of-day</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.36"><b>9.1</b></a></li>
    5126                         <li><tt>type</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.55"><b>9.5</b></a></li>
     5168                        <li><tt>rfc1123-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.35"><b>9.1</b></a></li>
     5169                        <li><tt>rfc850-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.48"><b>9.1</b></a></li>
     5170                        <li><tt>second</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.40"><b>9.1</b></a></li>
     5171                        <li><tt>Server</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.33"><b>8.4.2</b></a></li>
     5172                        <li><tt>subtype</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.57"><b>9.5</b></a></li>
     5173                        <li><tt>time-of-day</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.37"><b>9.1</b></a></li>
     5174                        <li><tt>type</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.56"><b>9.5</b></a></li>
    51275175                        <li><tt>User-Agent</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.26"><b>6.5.3</b></a></li>
    5128                         <li><tt>value</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.59"><b>9.5</b></a></li>
     5176                        <li><tt>value</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.60"><b>9.5</b></a></li>
     5177                        <li><tt>Vary</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.31"><b>8.2.2</b></a></li>
    51295178                        <li><tt>weight</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.13"><b>6.3.1</b></a></li>
    5130                         <li><tt>year</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.44"><b>9.1</b></a></li>
     5179                        <li><tt>year</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.45"><b>9.1</b></a></li>
    51315180                     </ul>
    51325181                  </li>
    5133                   <li>gzip (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.g.53">9.4</a></li>
     5182                  <li>gzip (Coding Format)&nbsp;&nbsp;<a href="#rfc.iref.g.54">9.4</a></li>
    51345183               </ul>
    51355184            </li>
     
    51425191                        <li>Accept-Encoding&nbsp;&nbsp;<a href="#rfc.xref.header.accept-encoding.1">3.5.1</a>, <a href="#rfc.xref.header.accept-encoding.2">6.3</a>, <a href="#rfc.iref.h.10"><b>6.3.4</b></a>, <a href="#rfc.xref.header.accept-encoding.3">9.4</a>, <a href="#rfc.xref.header.accept-encoding.4">10.3.2</a>, <a href="#rfc.xref.header.accept-encoding.5">10.4.2</a></li>
    51435192                        <li>Accept-Language&nbsp;&nbsp;<a href="#rfc.xref.header.accept-language.1">3.5.1</a>, <a href="#rfc.xref.header.accept-language.2">6.3</a>, <a href="#rfc.iref.h.11"><b>6.3.5</b></a>, <a href="#rfc.xref.header.accept-language.3">10.3.2</a></li>
    5144                         <li>Allow&nbsp;&nbsp;<a href="#rfc.xref.header.allow.1">5.1</a>, <a href="#rfc.xref.header.allow.2">8.4</a>, <a href="#rfc.iref.h.18"><b>8.4.1</b></a>, <a href="#rfc.xref.header.allow.3">10.3.2</a>, <a href="#rfc.xref.header.allow.4">C</a></li>
     5193                        <li>Allow&nbsp;&nbsp;<a href="#rfc.xref.header.allow.1">5.1</a>, <a href="#rfc.xref.header.allow.2">8.4</a>, <a href="#rfc.iref.h.19"><b>8.4.1</b></a>, <a href="#rfc.xref.header.allow.3">10.3.2</a>, <a href="#rfc.xref.header.allow.4">C</a></li>
    51455194                        <li>Content-Encoding&nbsp;&nbsp;<a href="#rfc.xref.header.content-encoding.1">3.2</a>, <a href="#rfc.iref.h.2"><b>3.2.2</b></a>, <a href="#rfc.xref.header.content-encoding.2">9.4</a>, <a href="#rfc.xref.header.content-encoding.3">10.3.2</a></li>
    51465195                        <li>Content-Language&nbsp;&nbsp;<a href="#rfc.xref.header.content-language.1">3.2</a>, <a href="#rfc.iref.h.3"><b>3.2.3</b></a>, <a href="#rfc.xref.header.content-language.2">10.3.2</a></li>
    51475196                        <li>Content-Location&nbsp;&nbsp;<a href="#rfc.xref.header.content-location.1">3.2</a>, <a href="#rfc.iref.h.4"><b>3.2.4</b></a>, <a href="#rfc.xref.header.content-location.2">5.3.3</a>, <a href="#rfc.xref.header.content-location.3">8.1.1</a>, <a href="#rfc.xref.header.content-location.4">10.3.2</a>, <a href="#rfc.xref.header.content-location.5">C</a></li>
    5148                         <li>Content-Transfer-Encoding&nbsp;&nbsp;<a href="#rfc.iref.h.21">A.5</a>, <a href="#rfc.xref.no.content-transfer-encoding.1">C</a></li>
     5197                        <li>Content-Transfer-Encoding&nbsp;&nbsp;<a href="#rfc.iref.h.22">A.5</a>, <a href="#rfc.xref.no.content-transfer-encoding.1">C</a></li>
    51495198                        <li>Content-Type&nbsp;&nbsp;<a href="#rfc.xref.header.content-type.1">3.2</a>, <a href="#rfc.iref.h.1"><b>3.2.1</b></a>, <a href="#rfc.xref.header.content-type.2">7</a>, <a href="#rfc.xref.header.content-type.3">9.5</a>, <a href="#rfc.xref.header.content-type.4">10.3.1</a>, <a href="#rfc.xref.header.content-type.5">10.3.2</a></li>
    51505199                        <li>Date&nbsp;&nbsp;<a href="#rfc.xref.header.date.1">8.2</a>, <a href="#rfc.iref.h.17"><b>8.2.1</b></a>, <a href="#rfc.xref.header.date.2">10.3.2</a></li>
     
    51535202                        <li>Location&nbsp;&nbsp;<a href="#rfc.xref.header.location.1">5.3.3</a>, <a href="#rfc.xref.header.location.2">7.4</a>, <a href="#rfc.xref.header.location.3">8.1</a>, <a href="#rfc.iref.h.15"><b>8.1.1</b></a>, <a href="#rfc.xref.header.location.4">10.3.2</a>, <a href="#rfc.xref.header.location.5">C</a></li>
    51545203                        <li>Max-Forwards&nbsp;&nbsp;<a href="#rfc.xref.header.max-forwards.1">5.3.7</a>, <a href="#rfc.xref.header.max-forwards.2">5.3.8</a>, <a href="#rfc.xref.header.max-forwards.3">6.1</a>, <a href="#rfc.iref.h.6"><b>6.1.1</b></a>, <a href="#rfc.xref.header.max-forwards.4">10.3.2</a>, <a href="#rfc.xref.header.max-forwards.5">C</a></li>
    5155                         <li>MIME-Version&nbsp;&nbsp;<a href="#rfc.xref.mime-version.1">10.3.2</a>, <a href="#rfc.iref.h.20"><b>A.1</b></a></li>
     5204                        <li>MIME-Version&nbsp;&nbsp;<a href="#rfc.xref.mime-version.1">10.3.2</a>, <a href="#rfc.iref.h.21"><b>A.1</b></a></li>
    51565205                        <li>Referer&nbsp;&nbsp;<a href="#rfc.xref.header.referer.1">6.5</a>, <a href="#rfc.iref.h.13"><b>6.5.2</b></a>, <a href="#rfc.xref.header.referer.2">10.3.2</a>, <a href="#rfc.xref.header.referer.3">C</a></li>
    51575206                        <li>Retry-After&nbsp;&nbsp;<a href="#rfc.xref.header.retry-after.1">7.6.4</a>, <a href="#rfc.xref.header.retry-after.2">8.1</a>, <a href="#rfc.iref.h.16"><b>8.1.2</b></a>, <a href="#rfc.xref.header.retry-after.3">10.3.2</a></li>
    5158                         <li>Server&nbsp;&nbsp;<a href="#rfc.xref.header.server.1">8.4</a>, <a href="#rfc.iref.h.19"><b>8.4.2</b></a>, <a href="#rfc.xref.header.server.2">10.3.2</a>, <a href="#rfc.xref.header.server.3">11.1</a>, <a href="#rfc.xref.header.server.4">C</a></li>
     5207                        <li>Server&nbsp;&nbsp;<a href="#rfc.xref.header.server.1">8.4</a>, <a href="#rfc.iref.h.20"><b>8.4.2</b></a>, <a href="#rfc.xref.header.server.2">10.3.2</a>, <a href="#rfc.xref.header.server.3">11.1</a>, <a href="#rfc.xref.header.server.4">C</a></li>
    51595208                        <li>User-Agent&nbsp;&nbsp;<a href="#rfc.xref.header.user-agent.1">3.5.1</a>, <a href="#rfc.xref.header.user-agent.2">6.5</a>, <a href="#rfc.iref.h.14"><b>6.5.3</b></a>, <a href="#rfc.xref.header.user-agent.3">10.3.2</a>, <a href="#rfc.xref.header.user-agent.4">11.1</a></li>
     5209                        <li>Vary&nbsp;&nbsp;<a href="#rfc.xref.header.vary.1">3.5.1</a>, <a href="#rfc.xref.header.vary.2">8.2</a>, <a href="#rfc.iref.h.18"><b>8.2.2</b></a>, <a href="#rfc.xref.header.vary.3">10.3.2</a></li>
    51605210                     </ul>
    51615211                  </li>
     
    52435293                     </ul>
    52445294                  </li>
    5245                   <li><em>Part6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">3.2</a>, <a href="#rfc.xref.Part6.2">3.5.1</a>, <a href="#rfc.xref.Part6.3">5.2.3</a>, <a href="#rfc.xref.Part6.4">5.3.1</a>, <a href="#rfc.xref.Part6.5">5.3.2</a>, <a href="#rfc.xref.Part6.6">5.3.3</a>, <a href="#rfc.xref.Part6.7">5.3.4</a>, <a href="#rfc.xref.Part6.8">5.3.5</a>, <a href="#rfc.xref.Part6.9">7.3.1</a>, <a href="#rfc.xref.Part6.10">7.3.4</a>, <a href="#rfc.xref.Part6.11">7.3.4</a>, <a href="#rfc.xref.Part6.12">7.3.4</a>, <a href="#rfc.xref.Part6.13">7.4.1</a>, <a href="#rfc.xref.Part6.14">7.4.2</a>, <a href="#rfc.xref.Part6.15">7.5.9</a>, <a href="#rfc.xref.Part6.16">8.2</a>, <a href="#rfc.xref.Part6.17">8.2</a>, <a href="#rfc.xref.Part6.18">10.2.2</a>, <a href="#rfc.xref.Part6.19">10.3.1</a>, <a href="#Part6"><b>13.1</b></a><ul>
    5246                         <li><em>Section 4.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.6">5.3.3</a></li>
    5247                         <li><em>Section 4.1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.9">7.3.1</a>, <a href="#rfc.xref.Part6.12">7.3.4</a>, <a href="#rfc.xref.Part6.13">7.4.1</a>, <a href="#rfc.xref.Part6.14">7.4.2</a>, <a href="#rfc.xref.Part6.15">7.5.9</a></li>
    5248                         <li><em>Section 5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.5">5.3.2</a></li>
    5249                         <li><em>Section 6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.7">5.3.4</a>, <a href="#rfc.xref.Part6.8">5.3.5</a></li>
    5250                         <li><em>Section 7.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.16">8.2</a></li>
    5251                         <li><em>Section 7.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.10">7.3.4</a></li>
     5295                  <li><em>Part6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">3.2</a>, <a href="#rfc.xref.Part6.2">5.2.3</a>, <a href="#rfc.xref.Part6.3">5.3.1</a>, <a href="#rfc.xref.Part6.4">5.3.2</a>, <a href="#rfc.xref.Part6.5">5.3.3</a>, <a href="#rfc.xref.Part6.6">5.3.4</a>, <a href="#rfc.xref.Part6.7">5.3.5</a>, <a href="#rfc.xref.Part6.8">7.3.1</a>, <a href="#rfc.xref.Part6.9">7.3.4</a>, <a href="#rfc.xref.Part6.10">7.3.4</a>, <a href="#rfc.xref.Part6.11">7.3.4</a>, <a href="#rfc.xref.Part6.12">7.4.1</a>, <a href="#rfc.xref.Part6.13">7.4.2</a>, <a href="#rfc.xref.Part6.14">7.5.9</a>, <a href="#rfc.xref.Part6.15">8.2</a>, <a href="#rfc.xref.Part6.16">8.2.2</a>, <a href="#rfc.xref.Part6.17">10.2.2</a>, <a href="#rfc.xref.Part6.18">10.3.1</a>, <a href="#Part6"><b>13.1</b></a><ul>
     5296                        <li><em>Section 4.1.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.5">5.3.3</a></li>
     5297                        <li><em>Section 4.1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.8">7.3.1</a>, <a href="#rfc.xref.Part6.11">7.3.4</a>, <a href="#rfc.xref.Part6.12">7.4.1</a>, <a href="#rfc.xref.Part6.13">7.4.2</a>, <a href="#rfc.xref.Part6.14">7.5.9</a></li>
     5298                        <li><em>Section 4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.16">8.2.2</a></li>
     5299                        <li><em>Section 5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.4">5.3.2</a></li>
     5300                        <li><em>Section 6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.6">5.3.4</a>, <a href="#rfc.xref.Part6.7">5.3.5</a></li>
     5301                        <li><em>Section 7.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.15">8.2</a></li>
     5302                        <li><em>Section 7.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.9">7.3.4</a></li>
    52525303                        <li><em>Section 7.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">3.2</a></li>
    5253                         <li><em>Section 7.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.2">3.5.1</a>, <a href="#rfc.xref.Part6.17">8.2</a></li>
    5254                         <li><em>Section 7.6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.11">7.3.4</a></li>
     5304                        <li><em>Section 7.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.10">7.3.4</a></li>
    52555305                     </ul>
    52565306                  </li>
     
    54255475               </ul>
    54265476            </li>
     5477            <li><a id="rfc.index.V" href="#rfc.index.V"><b>V</b></a><ul>
     5478                  <li>Vary header field&nbsp;&nbsp;<a href="#rfc.xref.header.vary.1">3.5.1</a>, <a href="#rfc.xref.header.vary.2">8.2</a>, <a href="#rfc.iref.v.1"><b>8.2.2</b></a>, <a href="#rfc.xref.header.vary.3">10.3.2</a></li>
     5479               </ul>
     5480            </li>
    54275481         </ul>
    54285482      </div>
Note: See TracChangeset for help on using the changeset viewer.