Changeset 207


Ignore:
Timestamp:
Feb 10, 2008, 12:26:19 PM (12 years ago)
Author:
julian.reschke@…
Message:

Work on referencing ABNF rules adopted from other parts (finished for all parts, also grouped by part); relates to #36.

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

Legend:

Unmodified
Added
Removed

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

    r206 r207  
    495495               <li class="tocline1">2.1&nbsp;&nbsp;&nbsp;<a href="#notation.abnf">Augmented BNF</a></li>
    496496               <li class="tocline1">2.2&nbsp;&nbsp;&nbsp;<a href="#basic.rules">Basic Rules</a></li>
     497               <li class="tocline1">2.3&nbsp;&nbsp;&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li>
    497498            </ul>
    498499         </li>
    … …  
    985986      </p>
    986987      <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.22"></span>  quoted-pair    = "\" CHAR
     988</pre><h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a>&nbsp;<a id="abnf.dependencies" href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h2>
     989      <p id="rfc.section.2.3.p.1">The ABNF rules below are defined in other parts:</p>
     990      <div id="rfc.figure.u.13"></div><pre class="inline">  request-header =  &lt;request-header, defined in <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#request.header.fields" title="Request Header Fields">Section 4</a>&gt;
     991  response-header = &lt;response-header, defined in <a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#response.header.fields" title="Response Header Fields">Section 6</a>&gt;
     992</pre><div id="rfc.figure.u.14"></div><pre class="inline">  accept-params   = &lt;accept-params, defined in <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" title="Accept">Section 6.1</a>&gt;
     993  entity-body     = &lt;entity-body, defined in <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#entity.body" title="Entity Body">Section 4.2</a>&gt;
     994  entity-header   = &lt;entity-header, defined in <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#entity.header.fields" title="Entity Header Fields">Section 4.1</a>&gt;
     995</pre><div id="rfc.figure.u.15"></div><pre class="inline">  Cache-Control   = &lt;Cache-Control, defined in <a href="#Part6" id="rfc.xref.Part6.3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.pragma" title="Pragma">Section 16.4</a>&gt;
     996  Pragma          = &lt;Pragma, defined in <a href="#Part6" id="rfc.xref.Part6.4"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.pragma" title="Pragma">Section 16.4</a>&gt;
     997  Warning         = &lt;Warning, defined in <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.warning" title="Warning">Section 16.6</a>&gt;
    987998</pre><h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="protocol.parameters" href="#protocol.parameters">Protocol Parameters</a></h1>
    988999      <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="http.version" href="#http.version">HTTP Version</a></h2>
    … …  
    9961007      </p>
    9971008      <p id="rfc.section.3.1.p.2">The version of an HTTP message is indicated by an HTTP-Version field in the first line of the message. HTTP-Version is case-sensitive.</p>
    998       <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.23"></span>  HTTP-Version   = "HTTP" "/" 1*DIGIT "." 1*DIGIT
     1009      <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.23"></span>  HTTP-Version   = "HTTP" "/" 1*DIGIT "." 1*DIGIT
    9991010</pre><p id="rfc.section.3.1.p.4">Note that the major and minor numbers <em class="bcp14">MUST</em> be treated as separate integers and that each <em class="bcp14">MAY</em> be incremented higher than a single digit. Thus, HTTP/2.4 is a lower version than HTTP/2.13, which in turn is lower than HTTP/12.3.
    10001011         Leading zeros <em class="bcp14">MUST</em> be ignored by recipients and <em class="bcp14">MUST NOT</em> be sent.
    … …  
    10261037         "abs_path", "query", and "authority" from that specification:
    10271038      </p>
    1028       <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span><span id="rfc.iref.g.26"></span><span id="rfc.iref.g.27"></span><span id="rfc.iref.g.28"></span><span id="rfc.iref.g.29"></span><span id="rfc.iref.g.30"></span>  absoluteURI   = &lt;absoluteURI, defined in <a href="#RFC2396" id="rfc.xref.RFC2396.2"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a>, <a href="http://tools.ietf.org/html/rfc2396#section-3">Section 3</a>&gt;
     1039      <div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span><span id="rfc.iref.g.26"></span><span id="rfc.iref.g.27"></span><span id="rfc.iref.g.28"></span><span id="rfc.iref.g.29"></span><span id="rfc.iref.g.30"></span>  absoluteURI   = &lt;absoluteURI, defined in <a href="#RFC2396" id="rfc.xref.RFC2396.2"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a>, <a href="http://tools.ietf.org/html/rfc2396#section-3">Section 3</a>&gt;
    10291040  authority     = &lt;authority, defined in <a href="#RFC2396" id="rfc.xref.RFC2396.3"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a>, <a href="http://tools.ietf.org/html/rfc2396#section-3.2">Section 3.2</a>&gt;
    10301041  fragment      = &lt;fragment, defined in <a href="#RFC2396" id="rfc.xref.RFC2396.4"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a>, <a href="http://tools.ietf.org/html/rfc2396#section-4.1">Section 4.1</a>&gt;
    … …  
    10341045  relativeURI   = &lt;relativeURI, defined in <a href="#RFC2396" id="rfc.xref.RFC2396.8"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a>, <a href="http://tools.ietf.org/html/rfc2396#section-5">Section 5</a>&gt;
    10351046  uri-host      = &lt;host, defined in <a href="#RFC2396" id="rfc.xref.RFC2396.9"><cite title="Uniform Resource Identifiers (URI): Generic Syntax">[RFC2396]</cite></a>, <a href="http://tools.ietf.org/html/rfc2396#section-3.2.2">Section 3.2.2</a>&gt;
    1036 </pre><p id="rfc.section.3.2.1.p.3">HTTP does not place any a priori limit on the length of a URI. Servers <em class="bcp14">MUST</em> be able to handle the URI of any resource they serve, and <em class="bcp14">SHOULD</em> be able to handle URIs of unbounded length if they provide GET-based forms that could generate such URIs. A server <em class="bcp14">SHOULD</em> return 414 (Request-URI Too Long) status if a URI is longer than the server can handle (see <a href="p2-semantics.html#status.414" title="414 Request-URI Too Long">Section 9.4.15</a> of <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>).
     1047</pre><p id="rfc.section.3.2.1.p.3">HTTP does not place any a priori limit on the length of a URI. Servers <em class="bcp14">MUST</em> be able to handle the URI of any resource they serve, and <em class="bcp14">SHOULD</em> be able to handle URIs of unbounded length if they provide GET-based forms that could generate such URIs. A server <em class="bcp14">SHOULD</em> return 414 (Request-URI Too Long) status if a URI is longer than the server can handle (see <a href="p2-semantics.html#status.414" title="414 Request-URI Too Long">Section 9.4.15</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>).
    10371048      </p>
    10381049      <p id="rfc.section.3.2.1.p.4"> </p>
    … …  
    10461057         and semantics for http URLs.
    10471058      </p>
    1048       <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.31"></span>  http-URL = "http:" "//" uri-host [ ":" port ]
     1059      <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.31"></span>  http-URL = "http:" "//" uri-host [ ":" port ]
    10491060             [ path-absolute [ "?" query ]]
    10501061</pre><p id="rfc.section.3.2.2.p.3">If the port is empty or not given, port 80 is assumed. The semantics are that the identified resource is located at the server
    … …  
    10651076      </p>
    10661077      <p id="rfc.section.3.2.3.p.3">For example, the following three URIs are equivalent:</p>
    1067       <div id="rfc.figure.u.16"></div><pre class="text">   http://example.com:80/~smith/home.html
     1078      <div id="rfc.figure.u.19"></div><pre class="text">   http://example.com:80/~smith/home.html
    10681079   http://EXAMPLE.com/%7Esmith/home.html
    10691080   http://EXAMPLE.com:/%7esmith/home.html
    … …  
    10711082      <h3 id="rfc.section.3.3.1"><a href="#rfc.section.3.3.1">3.3.1</a>&nbsp;<a id="full.date" href="#full.date">Full Date</a></h3>
    10721083      <p id="rfc.section.3.3.1.p.1">HTTP applications have historically allowed three different formats for the representation of date/time stamps:</p>
    1073       <div id="rfc.figure.u.17"></div><pre class="text">   Sun, 06 Nov 1994 08:49:37 GMT  ; RFC 822, updated by RFC 1123
     1084      <div id="rfc.figure.u.20"></div><pre class="text">   Sun, 06 Nov 1994 08:49:37 GMT  ; RFC 822, updated by RFC 1123
    10741085   Sunday, 06-Nov-94 08:49:37 GMT ; obsolete RFC 850 format
    10751086   Sun Nov  6 08:49:37 1994       ; ANSI C's asctime() format
    … …  
    10861097         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 LWS beyond that specifically included as SP in the grammar.
    10871098      </p>
    1088       <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.32"></span><span id="rfc.iref.g.33"></span><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>  HTTP-date    = rfc1123-date | rfc850-date | asctime-date
     1099      <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.32"></span><span id="rfc.iref.g.33"></span><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>  HTTP-date    = rfc1123-date | rfc850-date | asctime-date
    10891100  rfc1123-date = wkday "," SP date1 SP time SP "GMT"
    10901101  rfc850-date  = weekday "," SP date2 SP time SP "GMT"
    … …  
    11131124         is a property of the message, not of the original entity.
    11141125      </p>
    1115       <div id="rfc.figure.u.19"></div><pre class="inline"><span id="rfc.iref.g.43"></span><span id="rfc.iref.g.44"></span>  transfer-coding         = "chunked" | transfer-extension
     1126      <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.43"></span><span id="rfc.iref.g.44"></span>  transfer-coding         = "chunked" | transfer-extension
    11161127  transfer-extension      = token *( ";" parameter )
    11171128</pre><p id="rfc.section.3.4.p.3">Parameters are in the form of attribute/value pairs.</p>
    1118       <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.45"></span><span id="rfc.iref.g.46"></span><span id="rfc.iref.g.47"></span>  parameter               = attribute "=" value
     1129      <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.45"></span><span id="rfc.iref.g.46"></span><span id="rfc.iref.g.47"></span>  parameter               = attribute "=" value
    11191130  attribute               = token
    11201131  value                   = token | quoted-string
    … …  
    11301141      </p>
    11311142      <p id="rfc.section.3.4.p.8">The Internet Assigned Numbers Authority (IANA) acts as a registry for transfer-coding value tokens. Initially, the registry
    1132          contains the following tokens: "chunked" (<a href="#chunked.transfer.encoding" title="Chunked Transfer Coding">Section&nbsp;3.4.1</a>), "gzip", "compress", and "deflate" (<a href="p3-payload.html#content.codings" title="Content Codings">Section 3.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>).
    1133       </p>
    1134       <p id="rfc.section.3.4.p.9">New transfer-coding value tokens <em class="bcp14">SHOULD</em> be registered in the same way as new content-coding value tokens (<a href="p3-payload.html#content.codings" title="Content Codings">Section 3.2</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>).
     1143         contains the following tokens: "chunked" (<a href="#chunked.transfer.encoding" title="Chunked Transfer Coding">Section&nbsp;3.4.1</a>), "gzip", "compress", and "deflate" (<a href="p3-payload.html#content.codings" title="Content Codings">Section 3.2</a> of <a href="#Part3" id="rfc.xref.Part3.9"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>).
     1144      </p>
     1145      <p id="rfc.section.3.4.p.9">New transfer-coding value tokens <em class="bcp14">SHOULD</em> be registered in the same way as new content-coding value tokens (<a href="p3-payload.html#content.codings" title="Content Codings">Section 3.2</a> of <a href="#Part3" id="rfc.xref.Part3.10"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>).
    11351146      </p>
    11361147      <p id="rfc.section.3.4.p.10">A server which receives an entity-body with a transfer-coding it does not understand <em class="bcp14">SHOULD</em> return 501 (Not Implemented), and close the connection. A server <em class="bcp14">MUST NOT</em> send transfer-codings to an HTTP/1.0 client.
    … …  
    11411152         necessary for the recipient to verify that it has received the full message.
    11421153      </p>
    1143       <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.48"></span><span id="rfc.iref.g.49"></span><span id="rfc.iref.g.50"></span><span id="rfc.iref.g.51"></span><span id="rfc.iref.g.52"></span><span id="rfc.iref.g.53"></span><span id="rfc.iref.g.54"></span><span id="rfc.iref.g.55"></span><span id="rfc.iref.g.56"></span>  Chunked-Body   = *chunk
     1154      <div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.48"></span><span id="rfc.iref.g.49"></span><span id="rfc.iref.g.50"></span><span id="rfc.iref.g.51"></span><span id="rfc.iref.g.52"></span><span id="rfc.iref.g.53"></span><span id="rfc.iref.g.54"></span><span id="rfc.iref.g.55"></span><span id="rfc.iref.g.56"></span>  Chunked-Body   = *chunk
    11441155                   last-chunk
    11451156                   trailer-part
    … …  
    11781189      </p>
    11791190      <p id="rfc.section.3.4.1.p.7">A process for decoding the "chunked" transfer-coding can be represented in pseudo-code as:</p>
    1180       <div id="rfc.figure.u.22"></div><pre class="text">    length := 0
     1191      <div id="rfc.figure.u.25"></div><pre class="text">    length := 0
    11811192    read chunk-size, chunk-extension (if any) and CRLF
    11821193    while (chunk-size &gt; 0) {
    … …  
    12001211         space. By convention, the products are listed in order of their significance for identifying the application.
    12011212      </p>
    1202       <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.57"></span><span id="rfc.iref.g.58"></span>  product         = token ["/" product-version]
     1213      <div id="rfc.figure.u.26"></div><pre class="inline"><span id="rfc.iref.g.57"></span><span id="rfc.iref.g.58"></span>  product         = token ["/" product-version]
    12031214  product-version = token
    12041215</pre><p id="rfc.section.3.5.p.3">Examples:</p>
    1205       <div id="rfc.figure.u.24"></div><pre class="text">    User-Agent: CERN-LineMode/2.15 libwww/2.17b3
     1216      <div id="rfc.figure.u.27"></div><pre class="text">    User-Agent: CERN-LineMode/2.15 libwww/2.17b3
    12061217    Server: Apache/0.8.4
    12071218</pre><p id="rfc.section.3.5.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 character <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).
    … …  
    12101221      <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a id="message.types" href="#message.types">Message Types</a></h2>
    12111222      <p id="rfc.section.4.1.p.1">HTTP messages consist of requests from client to server and responses from server to client.</p>
    1212       <div id="rfc.figure.u.25"></div><pre class="inline"><span id="rfc.iref.g.59"></span>  HTTP-message   = Request | Response     ; HTTP/1.1 messages
     1223      <div id="rfc.figure.u.28"></div><pre class="inline"><span id="rfc.iref.g.59"></span>  HTTP-message   = Request | Response     ; HTTP/1.1 messages
    12131224</pre><p id="rfc.section.4.1.p.3">Request (<a href="#request" title="Request">Section&nbsp;5</a>) and Response (<a href="#response" title="Response">Section&nbsp;6</a>) messages use the generic message format of <a href="#RFC2822" id="rfc.xref.RFC2822.2"><cite title="Internet Message Format">[RFC2822]</cite></a> for transferring entities (the payload of the message). Both types of message consist of a start-line, zero or more header
    12141225         fields (also known as "headers"), an empty line (i.e., a line with nothing preceding the CRLF) indicating the end of the header
    12151226         fields, and possibly a message-body.
    12161227      </p>
    1217       <div id="rfc.figure.u.26"></div><pre class="inline"><span id="rfc.iref.g.60"></span><span id="rfc.iref.g.61"></span>  generic-message = start-line
     1228      <div id="rfc.figure.u.29"></div><pre class="inline"><span id="rfc.iref.g.60"></span><span id="rfc.iref.g.61"></span>  generic-message = start-line
    12181229                    *(message-header CRLF)
    12191230                    CRLF
    … …  
    12271238      </p>
    12281239      <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a id="message.headers" href="#message.headers">Message Headers</a></h2>
    1229       <p id="rfc.section.4.2.p.1">HTTP header fields, which include general-header (<a href="#general.header.fields" title="General Header Fields">Section&nbsp;4.5</a>), request-header (<a href="p2-semantics.html#request.header.fields" title="Request Header Fields">Section 4</a> of <a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>), response-header (<a href="p2-semantics.html#response.header.fields" title="Response Header Fields">Section 6</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>), and entity-header (<a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 4.1</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>) fields, follow the same generic format as that given in <a href="http://tools.ietf.org/html/rfc2822#section-2.1">Section 2.1</a> of <a href="#RFC2822" id="rfc.xref.RFC2822.3"><cite title="Internet Message Format">[RFC2822]</cite></a>. Each header field consists of a name followed by a colon (":") and the field value. Field names are case-insensitive. The
     1240      <p id="rfc.section.4.2.p.1">HTTP header fields, which include general-header (<a href="#general.header.fields" title="General Header Fields">Section&nbsp;4.5</a>), request-header (<a href="p2-semantics.html#request.header.fields" title="Request Header Fields">Section 4</a> of <a href="#Part2" id="rfc.xref.Part2.4"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>), response-header (<a href="p2-semantics.html#response.header.fields" title="Response Header Fields">Section 6</a> of <a href="#Part2" id="rfc.xref.Part2.5"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>), and entity-header (<a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 4.1</a> of <a href="#Part3" id="rfc.xref.Part3.11"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) fields, follow the same generic format as that given in <a href="http://tools.ietf.org/html/rfc2822#section-2.1">Section 2.1</a> of <a href="#RFC2822" id="rfc.xref.RFC2822.3"><cite title="Internet Message Format">[RFC2822]</cite></a>. Each header field consists of a name followed by a colon (":") and the field value. Field names are case-insensitive. The
    12301241         field value <em class="bcp14">MAY</em> be preceded by any amount of LWS, though a single SP is preferred. Header fields can be extended over multiple lines by preceding
    12311242         each extra line with at least one SP or HTAB. Applications ought to follow "common form", where one is known or indicated,
    … …  
    12331244         forms.
    12341245      </p>
    1235       <div id="rfc.figure.u.27"></div><pre class="inline"><span id="rfc.iref.g.62"></span><span id="rfc.iref.g.63"></span><span id="rfc.iref.g.64"></span><span id="rfc.iref.g.65"></span>  message-header = field-name ":" [ field-value ]
     1246      <div id="rfc.figure.u.30"></div><pre class="inline"><span id="rfc.iref.g.62"></span><span id="rfc.iref.g.63"></span><span id="rfc.iref.g.64"></span><span id="rfc.iref.g.65"></span>  message-header = field-name ":" [ field-value ]
    12361247  field-name     = token
    12371248  field-value    = *( field-content | LWS )
    … …  
    12581269         header field (<a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.2" title="Transfer-Encoding">Section&nbsp;8.7</a>).
    12591270      </p>
    1260       <div id="rfc.figure.u.28"></div><pre class="inline"><span id="rfc.iref.g.66"></span>  message-body = entity-body
     1271      <div id="rfc.figure.u.31"></div><pre class="inline"><span id="rfc.iref.g.66"></span>  message-body = entity-body
    12611272               | &lt;entity-body encoded as per Transfer-Encoding&gt;
    12621273</pre><p id="rfc.section.4.3.p.3">Transfer-Encoding <em class="bcp14">MUST</em> be used to indicate any transfer-codings applied by an application to ensure safe and proper transfer of the message. Transfer-Encoding
    … …  
    12651276      <p id="rfc.section.4.3.p.4">The rules for when a message-body is allowed in a message differ for requests and responses.</p>
    12661277      <p id="rfc.section.4.3.p.5">The presence of a message-body in a request is signaled by the inclusion of a Content-Length or Transfer-Encoding header field
    1267          in the request's message-headers. A message-body <em class="bcp14">MUST NOT</em> be included in a request if the specification of the request method (<a href="p2-semantics.html#method" title="Method">Section 3</a> of <a href="#Part2" id="rfc.xref.Part2.4"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) explicitly disallows an entity-body in requests. When a request message contains both a message-body of non-zero length
     1278         in the request's message-headers. A message-body <em class="bcp14">MUST NOT</em> be included in a request if the specification of the request method (<a href="p2-semantics.html#method" title="Method">Section 3</a> of <a href="#Part2" id="rfc.xref.Part2.6"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) explicitly disallows an entity-body in requests. When a request message contains both a message-body of non-zero length
    12681279         and a method that does not define any semantics for that request message-body, then an origin server <em class="bcp14">SHOULD</em> either ignore the message-body or respond with an appropriate error message (e.g., 413). A proxy or gateway, when presented
    12691280         the same request, <em class="bcp14">SHOULD</em> either forward the request inbound with the message-body or ignore the message-body when determining a response.
    … …  
    13251336         to the entity being transferred. These header fields apply only to the message being transmitted.
    13261337      </p>
    1327       <div id="rfc.figure.u.29"></div><pre class="inline"><span id="rfc.iref.g.67"></span>  general-header = Cache-Control            ; <a href="#Part6" id="rfc.xref.Part6.3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 16.2</a>
     1338      <div id="rfc.figure.u.32"></div><pre class="inline"><span id="rfc.iref.g.67"></span>  general-header = Cache-Control            ; <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.cache-control" title="Cache-Control">Section 16.2</a>
    13281339                 | Connection               ; <a href="#header.connection" id="rfc.xref.header.connection.1" title="Connection">Section&nbsp;8.1</a>
    13291340                 | Date                     ; <a href="#header.date" id="rfc.xref.header.date.1" title="Date">Section&nbsp;8.3</a>
    1330                  | Pragma                   ; <a href="#Part6" id="rfc.xref.Part6.4"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.pragma" title="Pragma">Section 16.4</a>
     1341                 | Pragma                   ; <a href="#Part6" id="rfc.xref.Part6.7"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.pragma" title="Pragma">Section 16.4</a>
    13311342                 | Trailer                  ; <a href="#header.trailer" id="rfc.xref.header.trailer.2" title="Trailer">Section&nbsp;8.6</a>
    13321343                 | Transfer-Encoding        ; <a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.4" title="Transfer-Encoding">Section&nbsp;8.7</a>
    13331344                 | Upgrade                  ; <a href="#header.upgrade" id="rfc.xref.header.upgrade.1" title="Upgrade">Section&nbsp;8.8</a>
    13341345                 | Via                      ; <a href="#header.via" id="rfc.xref.header.via.1" title="Via">Section&nbsp;8.9</a>
    1335                  | Warning                  ; <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.warning" title="Warning">Section 16.6</a>
     1346                 | Warning                  ; <a href="#Part6" id="rfc.xref.Part6.8"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.warning" title="Warning">Section 16.6</a>
    13361347</pre><p id="rfc.section.4.5.p.3">General-header field names can be extended reliably only in combination with a change in the protocol version. However, new
    13371348         or experimental header fields may be given the semantics of general header fields if all parties in the communication recognize
    … …  
    13421353         resource, the identifier of the resource, and the protocol version in use.
    13431354      </p>
    1344       <div id="rfc.figure.u.30"></div><pre class="inline"><span id="rfc.iref.g.68"></span>  Request       = Request-Line              ; <a href="#request-line" title="Request-Line">Section&nbsp;5.1</a>
     1355      <div id="rfc.figure.u.33"></div><pre class="inline"><span id="rfc.iref.g.68"></span>  Request       = Request-Line              ; <a href="#request-line" title="Request-Line">Section&nbsp;5.1</a>
    13451356                  *(( general-header        ; <a href="#general.header.fields" title="General Header Fields">Section&nbsp;4.5</a>
    1346                    | request-header         ; <a href="#Part2" id="rfc.xref.Part2.5"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#request.header.fields" title="Request Header Fields">Section 4</a>
    1347                    | entity-header ) CRLF)  ; <a href="#Part3" id="rfc.xref.Part3.9"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 4.1</a>
     1357                   | request-header         ; <a href="#Part2" id="rfc.xref.Part2.7"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#request.header.fields" title="Request Header Fields">Section 4</a>
     1358                   | entity-header ) CRLF)  ; <a href="#Part3" id="rfc.xref.Part3.12"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 4.1</a>
    13481359                  CRLF
    13491360                  [ message-body ]          ; <a href="#message.body" title="Message Body">Section&nbsp;4.3</a>
    … …  
    13521363         elements are separated by SP characters. No CR or LF is allowed except in the final CRLF sequence.
    13531364      </p>
    1354       <div id="rfc.figure.u.31"></div><pre class="inline"><span id="rfc.iref.g.69"></span>  Request-Line   = Method SP Request-URI SP HTTP-Version CRLF
     1365      <div id="rfc.figure.u.34"></div><pre class="inline"><span id="rfc.iref.g.69"></span>  Request-Line   = Method SP Request-URI SP HTTP-Version CRLF
    13551366</pre><h3 id="rfc.section.5.1.1"><a href="#rfc.section.5.1.1">5.1.1</a>&nbsp;<a id="method" href="#method">Method</a></h3>
    13561367      <p id="rfc.section.5.1.1.p.1">The Method token indicates the method to be performed on the resource identified by the Request-URI. The method is case-sensitive.</p>
    1357       <div id="rfc.figure.u.32"></div><pre class="inline"><span id="rfc.iref.g.70"></span><span id="rfc.iref.g.71"></span>  Method         = token
     1368      <div id="rfc.figure.u.35"></div><pre class="inline"><span id="rfc.iref.g.70"></span><span id="rfc.iref.g.71"></span>  Method         = token
    13581369</pre><h3 id="rfc.section.5.1.2"><a href="#rfc.section.5.1.2">5.1.2</a>&nbsp;<a id="request-uri" href="#request-uri">Request-URI</a></h3>
    13591370      <p id="rfc.section.5.1.2.p.1">The Request-URI is a Uniform Resource Identifier (<a href="#uri" title="Uniform Resource Identifiers">Section&nbsp;3.2</a>) and identifies the resource upon which to apply the request.
    13601371      </p>
    1361       <div id="rfc.figure.u.33"></div><pre class="inline"><span id="rfc.iref.g.72"></span>  Request-URI    = "*"
     1372      <div id="rfc.figure.u.36"></div><pre class="inline"><span id="rfc.iref.g.72"></span>  Request-URI    = "*"
    13621373                 | absoluteURI
    13631374                 | ( path-absolute [ "?" query ] )
    … …  
    13671378         apply to a resource. One example would be
    13681379      </p>
    1369       <div id="rfc.figure.u.34"></div><pre class="text">    OPTIONS * HTTP/1.1
     1380      <div id="rfc.figure.u.37"></div><pre class="text">    OPTIONS * HTTP/1.1
    13701381</pre><p id="rfc.section.5.1.2.p.5">The absoluteURI form is <em class="bcp14">REQUIRED</em> when the request is being made to a proxy. The proxy is requested to forward the request or service it from a valid cache,
    13711382         and return the response. Note that the proxy <em class="bcp14">MAY</em> forward the request on to another proxy or directly to the server specified by the absoluteURI. In order to avoid request
    … …  
    13731384         Request-Line would be:
    13741385      </p>
    1375       <div id="rfc.figure.u.35"></div><pre class="text">    GET http://www.example.org/pub/WWW/TheProject.html HTTP/1.1
     1386      <div id="rfc.figure.u.38"></div><pre class="text">    GET http://www.example.org/pub/WWW/TheProject.html HTTP/1.1
    13761387</pre><p id="rfc.section.5.1.2.p.7">To allow for transition to absoluteURIs in all requests in future versions of HTTP, all HTTP/1.1 servers <em class="bcp14">MUST</em> accept the absoluteURI form in requests, even though HTTP/1.1 clients will only generate them in requests to proxies.
    13771388      </p>
    1378       <p id="rfc.section.5.1.2.p.8">The authority form is only used by the CONNECT method (<a href="p2-semantics.html#CONNECT" title="CONNECT">Section 8.9</a> of <a href="#Part2" id="rfc.xref.Part2.6"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>).
     1389      <p id="rfc.section.5.1.2.p.8">The authority form is only used by the CONNECT method (<a href="p2-semantics.html#CONNECT" title="CONNECT">Section 8.9</a> of <a href="#Part2" id="rfc.xref.Part2.8"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>).
    13791390      </p>
    13801391      <p id="rfc.section.5.1.2.p.9">The most common form of Request-URI is that used to identify a resource on an origin server or gateway. In this case the absolute
    … …  
    13821393         server would create a TCP connection to port 80 of the host "www.example.org" and send the lines:
    13831394      </p>
    1384       <div id="rfc.figure.u.36"></div><pre class="text">    GET /pub/WWW/TheProject.html HTTP/1.1
     1395      <div id="rfc.figure.u.39"></div><pre class="text">    GET /pub/WWW/TheProject.html HTTP/1.1
    13851396    Host: www.example.org
    13861397</pre><p id="rfc.section.5.1.2.p.11">followed by the remainder of the Request. Note that the absolute path cannot be empty; if none is present in the original
    … …  
    14201431      <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="response" href="#response">Response</a></h1>
    14211432      <p id="rfc.section.6.p.1">After receiving and interpreting a request message, a server responds with an HTTP response message.</p>
    1422       <div id="rfc.figure.u.37"></div><pre class="inline"><span id="rfc.iref.g.73"></span>  Response      = Status-Line               ; <a href="#status-line" title="Status-Line">Section&nbsp;6.1</a>
     1433      <div id="rfc.figure.u.40"></div><pre class="inline"><span id="rfc.iref.g.73"></span>  Response      = Status-Line               ; <a href="#status-line" title="Status-Line">Section&nbsp;6.1</a>
    14231434                  *(( general-header        ; <a href="#general.header.fields" title="General Header Fields">Section&nbsp;4.5</a>
    1424                    | response-header        ; <a href="#Part2" id="rfc.xref.Part2.7"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#response.header.fields" title="Response Header Fields">Section 6</a>
    1425                    | entity-header ) CRLF)  ; <a href="#Part3" id="rfc.xref.Part3.10"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 4.1</a>
     1435                   | response-header        ; <a href="#Part2" id="rfc.xref.Part2.9"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#response.header.fields" title="Response Header Fields">Section 6</a>
     1436                   | entity-header ) CRLF)  ; <a href="#Part3" id="rfc.xref.Part3.13"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 4.1</a>
    14261437                  CRLF
    14271438                  [ message-body ]          ; <a href="#message.body" title="Message Body">Section&nbsp;4.3</a>
    … …  
    14311442         CRLF sequence.
    14321443      </p>
    1433       <div id="rfc.figure.u.38"></div><pre class="inline"><span id="rfc.iref.g.74"></span>  Status-Line = HTTP-Version SP Status-Code SP Reason-Phrase CRLF
     1444      <div id="rfc.figure.u.41"></div><pre class="inline"><span id="rfc.iref.g.74"></span>  Status-Line = HTTP-Version SP Status-Code SP Reason-Phrase CRLF
    14341445</pre><h3 id="rfc.section.6.1.1"><a href="#rfc.section.6.1.1">6.1.1</a>&nbsp;<a id="status.code.and.reason.phrase" href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a></h3>
    14351446      <p id="rfc.section.6.1.1.p.1">The Status-Code element is a 3-digit integer result code of the attempt to understand and satisfy the request. These codes
    1436          are fully defined in <a href="p2-semantics.html#status.codes" title="Status Code Definitions">Section 9</a> of <a href="#Part2" id="rfc.xref.Part2.8"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>. The Reason Phrase exists for the sole purpose of providing a textual description associated with the numeric status code,
     1447         are fully defined in <a href="p2-semantics.html#status.codes" title="Status Code Definitions">Section 9</a> of <a href="#Part2" id="rfc.xref.Part2.10"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>. The Reason Phrase exists for the sole purpose of providing a textual description associated with the numeric status code,
    14371448         out of deference to earlier Internet application protocols that were more frequently used with interactive text clients. A
    14381449         client <em class="bcp14">SHOULD</em> ignore the content of the Reason Phrase.
    … …  
    14481459         <li>5xx: Server Error - The server failed to fulfill an apparently valid request</li>
    14491460      </ul>
    1450       <div id="rfc.figure.u.39"></div><pre class="inline"><span id="rfc.iref.g.75"></span><span id="rfc.iref.g.76"></span><span id="rfc.iref.g.77"></span>  Status-Code    = 3DIGIT
     1461      <div id="rfc.figure.u.42"></div><pre class="inline"><span id="rfc.iref.g.75"></span><span id="rfc.iref.g.76"></span><span id="rfc.iref.g.77"></span>  Status-Code    = 3DIGIT
    14511462  Reason-Phrase  = *&lt;TEXT, excluding CR, LF&gt;
    14521463</pre><h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="connections" href="#connections">Connections</a></h1>
    … …  
    15041515      <p id="rfc.section.7.1.2.2.p.2">Clients which assume persistent connections and pipeline immediately after connection establishment <em class="bcp14">SHOULD</em> be prepared to retry their connection if the first pipelined attempt fails. If a client does such a retry, it <em class="bcp14">MUST NOT</em> pipeline before it knows the connection is persistent. Clients <em class="bcp14">MUST</em> also be prepared to resend their requests if the server closes the connection before sending all of the corresponding responses.
    15051516      </p>
    1506       <p id="rfc.section.7.1.2.2.p.3">Clients <em class="bcp14">SHOULD NOT</em> pipeline requests using non-idempotent methods or non-idempotent sequences of methods (see <a href="p2-semantics.html#idempotent.methods" title="Idempotent Methods">Section 8.1.2</a> of <a href="#Part2" id="rfc.xref.Part2.9"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>). Otherwise, a premature termination of the transport connection could lead to indeterminate results. A client wishing to
     1517      <p id="rfc.section.7.1.2.2.p.3">Clients <em class="bcp14">SHOULD NOT</em> pipeline requests using non-idempotent methods or non-idempotent sequences of methods (see <a href="p2-semantics.html#idempotent.methods" title="Idempotent Methods">Section 8.1.2</a> of <a href="#Part2" id="rfc.xref.Part2.11"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>). Otherwise, a premature termination of the transport connection could lead to indeterminate results. A client wishing to
    15071518         send a non-idempotent request <em class="bcp14">SHOULD</em> wait to send that request until it has received the response status for the previous request.
    15081519      </p>
    … …  
    15291540      </p>
    15301541      <p id="rfc.section.7.1.4.p.4">This means that clients, servers, and proxies <em class="bcp14">MUST</em> be able to recover from asynchronous close events. Client software <em class="bcp14">SHOULD</em> reopen the transport connection and retransmit the aborted sequence of requests without user interaction so long as the request
    1531          sequence is idempotent (see <a href="p2-semantics.html#idempotent.methods" title="Idempotent Methods">Section 8.1.2</a> of <a href="#Part2" id="rfc.xref.Part2.10"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>). Non-idempotent methods or sequences <em class="bcp14">MUST NOT</em> be automatically retried, although user agents <em class="bcp14">MAY</em> offer a human operator the choice of retrying the request(s). Confirmation by user-agent software with semantic understanding
     1542         sequence is idempotent (see <a href="p2-semantics.html#idempotent.methods" title="Idempotent Methods">Section 8.1.2</a> of <a href="#Part2" id="rfc.xref.Part2.12"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>). Non-idempotent methods or sequences <em class="bcp14">MUST NOT</em> be automatically retried, although user agents <em class="bcp14">MAY</em> offer a human operator the choice of retrying the request(s). Confirmation by user-agent software with semantic understanding
    15321543         of the application <em class="bcp14">MAY</em> substitute for user confirmation. The automatic retry <em class="bcp14">SHOULD NOT</em> be repeated if the second sequence of requests fails.
    15331544      </p>
    … …  
    15471558      </p>
    15481559      <h3 id="rfc.section.7.2.3"><a href="#rfc.section.7.2.3">7.2.3</a>&nbsp;<a id="use.of.the.100.status" href="#use.of.the.100.status">Use of the 100 (Continue) Status</a></h3>
    1549       <p id="rfc.section.7.2.3.p.1">The purpose of the 100 (Continue) status (see <a href="p2-semantics.html#status.100" title="100 Continue">Section 9.1.1</a> of <a href="#Part2" id="rfc.xref.Part2.11"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) is to allow a client that is sending a request message with a request body to determine if the origin server is willing
     1560      <p id="rfc.section.7.2.3.p.1">The purpose of the 100 (Continue) status (see <a href="p2-semantics.html#status.100" title="100 Continue">Section 9.1.1</a> of <a href="#Part2" id="rfc.xref.Part2.13"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) is to allow a client that is sending a request message with a request body to determine if the origin server is willing
    15501561         to accept the request (based on the request headers) before the client sends the request body. In some cases, it might either
    15511562         be inappropriate or highly inefficient for the client to send the body if the server will reject the message without looking
    … …  
    15541565      <p id="rfc.section.7.2.3.p.2">Requirements for HTTP/1.1 clients: </p>
    15551566      <ul>
    1556          <li>If a client will wait for a 100 (Continue) response before sending the request body, it <em class="bcp14">MUST</em> send an Expect request-header field (<a href="p2-semantics.html#header.expect" title="Expect">Section 10.2</a> of <a href="#Part2" id="rfc.xref.Part2.12"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) with the "100-continue" expectation.
    1557          </li>
    1558          <li>A client <em class="bcp14">MUST NOT</em> send an Expect request-header field (<a href="p2-semantics.html#header.expect" title="Expect">Section 10.2</a> of <a href="#Part2" id="rfc.xref.Part2.13"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) with the "100-continue" expectation if it does not intend to send a request body.
     1567         <li>If a client will wait for a 100 (Continue) response before sending the request body, it <em class="bcp14">MUST</em> send an Expect request-header field (<a href="p2-semantics.html#header.expect" title="Expect">Section 10.2</a> of <a href="#Part2" id="rfc.xref.Part2.14"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) with the "100-continue" expectation.
     1568         </li>
     1569         <li>A client <em class="bcp14">MUST NOT</em> send an Expect request-header field (<a href="p2-semantics.html#header.expect" title="Expect">Section 10.2</a> of <a href="#Part2" id="rfc.xref.Part2.15"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) with the "100-continue" expectation if it does not intend to send a request body.
    15591570         </li>
    15601571      </ul>
    … …  
    16001611         <li>A proxy <em class="bcp14">MUST NOT</em> forward a 100 (Continue) response if the request message was received from an HTTP/1.0 (or earlier) client and did not include
    16011612            an Expect request-header field with the "100-continue" expectation. This requirement overrides the general rule for forwarding
    1602             of 1xx responses (see <a href="p2-semantics.html#status.1xx" title="Informational 1xx">Section 9.1</a> of <a href="#Part2" id="rfc.xref.Part2.14"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>).
     1613            of 1xx responses (see <a href="p2-semantics.html#status.1xx" title="Informational 1xx">Section 9.1</a> of <a href="#Part2" id="rfc.xref.Part2.16"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>).
    16031614         </li>
    16041615      </ul>
    … …  
    16391650      </p>
    16401651      <p id="rfc.section.8.1.p.2">The Connection header has the following grammar:</p>
    1641       <div id="rfc.figure.u.40"></div><pre class="inline"><span id="rfc.iref.g.78"></span><span id="rfc.iref.g.79"></span>  Connection = "Connection" ":" 1#(connection-token)
     1652      <div id="rfc.figure.u.43"></div><pre class="inline"><span id="rfc.iref.g.78"></span><span id="rfc.iref.g.79"></span>  Connection = "Connection" ":" 1#(connection-token)
    16421653  connection-token  = token
    16431654</pre><p id="rfc.section.8.1.p.4">HTTP/1.1 proxies <em class="bcp14">MUST</em> parse the Connection header field before a message is forwarded and, for each connection-token in this field, remove any header
    … …  
    16511662         of the response. For example,
    16521663      </p>
    1653       <div id="rfc.figure.u.41"></div><pre class="text">    Connection: close
     1664      <div id="rfc.figure.u.44"></div><pre class="text">    Connection: close
    16541665</pre><p id="rfc.section.8.1.p.8">in either the request or the response header fields indicates that the connection <em class="bcp14">SHOULD NOT</em> be considered `persistent' (<a href="#persistent.connections" title="Persistent Connections">Section&nbsp;7.1</a>) after the current request/response is complete.
    16551666      </p>
    … …  
    16671678         or, in the case of the HEAD method, the size of the entity-body that would have been sent had the request been a GET.
    16681679      </p>
    1669       <div id="rfc.figure.u.42"></div><pre class="inline"><span id="rfc.iref.g.80"></span>  Content-Length    = "Content-Length" ":" 1*DIGIT
     1680      <div id="rfc.figure.u.45"></div><pre class="inline"><span id="rfc.iref.g.80"></span>  Content-Length    = "Content-Length" ":" 1*DIGIT
    16701681</pre><p id="rfc.section.8.2.p.3">An example is</p>
    1671       <div id="rfc.figure.u.43"></div><pre class="text">    Content-Length: 3495
     1682      <div id="rfc.figure.u.46"></div><pre class="text">    Content-Length: 3495
    16721683</pre><p id="rfc.section.8.2.p.5">Applications <em class="bcp14">SHOULD</em> use this field to indicate the transfer-length of the message-body, unless this is prohibited by the rules in <a href="#message.length" title="Message Length">Section&nbsp;4.4</a>.
    16731684      </p>
    … …  
    16841695         as orig-date in <a href="http://tools.ietf.org/html/rfc2822#section-3.6.1">Section 3.6.1</a> of <a href="#RFC2822" id="rfc.xref.RFC2822.4"><cite title="Internet Message Format">[RFC2822]</cite></a>. The field value is an HTTP-date, as described in <a href="#full.date" title="Full Date">Section&nbsp;3.3.1</a>; it <em class="bcp14">MUST</em> be sent in rfc1123-date format.
    16851696      </p>
    1686       <div id="rfc.figure.u.44"></div><pre class="inline"><span id="rfc.iref.g.81"></span>  Date  = "Date" ":" HTTP-date
     1697      <div id="rfc.figure.u.47"></div><pre class="inline"><span id="rfc.iref.g.81"></span>  Date  = "Date" ":" HTTP-date
    16871698</pre><p id="rfc.section.8.3.p.3">An example is</p>
    1688       <div id="rfc.figure.u.45"></div><pre class="text">    Date: Tue, 15 Nov 1994 08:12:31 GMT
     1699      <div id="rfc.figure.u.48"></div><pre class="text">    Date: Tue, 15 Nov 1994 08:12:31 GMT
    16891700</pre><p id="rfc.section.8.3.p.5">Origin servers <em class="bcp14">MUST</em> include a Date header field in all responses, except in these cases:
    16901701      </p>
    … …  
    17221733         a single IP address.
    17231734      </p>
    1724       <div id="rfc.figure.u.46"></div><pre class="inline"><span id="rfc.iref.g.82"></span>  Host = "Host" ":" uri-host [ ":" port ] ; <a href="#http.url" title="http URL">Section&nbsp;3.2.2</a>
     1735      <div id="rfc.figure.u.49"></div><pre class="inline"><span id="rfc.iref.g.82"></span>  Host = "Host" ":" uri-host [ ":" port ] ; <a href="#http.url" title="http URL">Section&nbsp;3.2.2</a>
    17251736</pre><p id="rfc.section.8.4.p.3">A "host" without any trailing port information implies the default port for the service requested (e.g., "80" for an HTTP
    17261737         URL). For example, a request on the origin server for &lt;http://www.example.org/pub/WWW/&gt; would properly include:
    17271738      </p>
    1728       <div id="rfc.figure.u.47"></div><pre class="text">    GET /pub/WWW/ HTTP/1.1
     1739      <div id="rfc.figure.u.50"></div><pre class="text">    GET /pub/WWW/ HTTP/1.1
    17291740    Host: www.example.org
    17301741</pre><p id="rfc.section.8.4.p.5">A client <em class="bcp14">MUST</em> include a Host header field in all HTTP/1.1 request messages. If the requested URI does not include an Internet host name
    … …  
    17411752         and/or a comma-separated list of extension transfer-coding names with optional accept parameters (as described in <a href="#transfer.codings" title="Transfer Codings">Section&nbsp;3.4</a>).
    17421753      </p>
    1743       <div id="rfc.figure.u.48"></div><pre class="inline"><span id="rfc.iref.g.83"></span><span id="rfc.iref.g.84"></span>  TE        = "TE" ":" #( t-codings )
     1754      <div id="rfc.figure.u.51"></div><pre class="inline"><span id="rfc.iref.g.83"></span><span id="rfc.iref.g.84"></span>  TE        = "TE" ":" #( t-codings )
    17441755  t-codings = "trailers" | ( transfer-extension [ accept-params ] )
    17451756</pre><p id="rfc.section.8.5.p.3">The presence of the keyword "trailers" indicates that the client is willing to accept trailer fields in a chunked transfer-coding,
    … …  
    17471758      </p>
    17481759      <p id="rfc.section.8.5.p.4">Examples of its use are:</p>
    1749       <div id="rfc.figure.u.49"></div><pre class="text">    TE: deflate
     1760      <div id="rfc.figure.u.52"></div><pre class="text">    TE: deflate
    17501761    TE:
    17511762    TE: trailers, deflate;q=0.5
    … …  
    17661777         <li>
    17671778            <p>If the transfer-coding being tested is one of the transfer-codings listed in the TE field, then it is acceptable unless it
    1768                is accompanied by a qvalue of 0. (As defined in <a href="p3-payload.html#quality.values" title="Quality Values">Section 3.4</a> of <a href="#Part3" id="rfc.xref.Part3.11"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, a qvalue of 0 means "not acceptable.")
     1779               is accompanied by a qvalue of 0. (As defined in <a href="p3-payload.html#quality.values" title="Quality Values">Section 3.4</a> of <a href="#Part3" id="rfc.xref.Part3.14"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, a qvalue of 0 means "not acceptable.")
    17691780            </p>
    17701781         </li>
    … …  
    17841795         with chunked transfer-coding.
    17851796      </p>
    1786       <div id="rfc.figure.u.50"></div><pre class="inline"><span id="rfc.iref.g.85"></span>  Trailer  = "Trailer" ":" 1#field-name
     1797      <div id="rfc.figure.u.53"></div><pre class="inline"><span id="rfc.iref.g.85"></span>  Trailer  = "Trailer" ":" 1#field-name
    17871798</pre><p id="rfc.section.8.6.p.3">An HTTP/1.1 message <em class="bcp14">SHOULD</em> include a Trailer header field in a message using chunked transfer-coding with a non-empty trailer. Doing so allows the recipient
    17881799         to know which header fields to expect in the trailer.
    … …  
    18041815         transfer-coding is a property of the message, not of the entity.
    18051816      </p>
    1806       <div id="rfc.figure.u.51"></div><pre class="inline"><span id="rfc.iref.g.86"></span>  Transfer-Encoding       = "Transfer-Encoding" ":" 1#transfer-coding
     1817      <div id="rfc.figure.u.54"></div><pre class="inline"><span id="rfc.iref.g.86"></span>  Transfer-Encoding       = "Transfer-Encoding" ":" 1#transfer-coding
    18071818</pre><p id="rfc.section.8.7.p.3">Transfer-codings are defined in <a href="#transfer.codings" title="Transfer Codings">Section&nbsp;3.4</a>. An example is:
    18081819      </p>
    1809       <div id="rfc.figure.u.52"></div><pre class="text">  Transfer-Encoding: chunked
     1820      <div id="rfc.figure.u.55"></div><pre class="text">  Transfer-Encoding: chunked
    18101821</pre><p id="rfc.section.8.7.p.5">If multiple encodings have been applied to an entity, the transfer-codings <em class="bcp14">MUST</em> be listed in the order in which they were applied. Additional information about the encoding parameters <em class="bcp14">MAY</em> be provided by other entity-header fields not defined by this specification.
    18111822      </p>
    … …  
    18171828         to use if the server finds it appropriate to switch protocols. The server <em class="bcp14">MUST</em> use the Upgrade header field within a 101 (Switching Protocols) response to indicate which protocol(s) are being switched.
    18181829      </p>
    1819       <div id="rfc.figure.u.53"></div><pre class="inline"><span id="rfc.iref.g.87"></span>  Upgrade        = "Upgrade" ":" 1#product
     1830      <div id="rfc.figure.u.56"></div><pre class="inline"><span id="rfc.iref.g.87"></span>  Upgrade        = "Upgrade" ":" 1#product
    18201831</pre><p id="rfc.section.8.8.p.3">For example,</p>
    1821       <div id="rfc.figure.u.54"></div><pre class="text">    Upgrade: HTTP/2.0, SHTTP/1.3, IRC/6.9, RTA/x11
     1832      <div id="rfc.figure.u.57"></div><pre class="text">    Upgrade: HTTP/2.0, SHTTP/1.3, IRC/6.9, RTA/x11
    18221833</pre><p id="rfc.section.8.8.p.5">The Upgrade header field is intended to provide a simple mechanism for transition from HTTP/1.1 to some other, incompatible
    18231834         protocol. It does so by allowing the client to advertise its desire to use another protocol, such as a later version of HTTP
    … …  
    18481859         of all senders along the request/response chain.
    18491860      </p>
    1850       <div id="rfc.figure.u.55"></div><pre class="inline"><span id="rfc.iref.g.88"></span><span id="rfc.iref.g.89"></span><span id="rfc.iref.g.90"></span><span id="rfc.iref.g.91"></span><span id="rfc.iref.g.92"></span><span id="rfc.iref.g.93"></span>  Via =  "Via" ":" 1#( received-protocol received-by [ comment ] )
     1861      <div id="rfc.figure.u.58"></div><pre class="inline"><span id="rfc.iref.g.88"></span><span id="rfc.iref.g.89"></span><span id="rfc.iref.g.90"></span><span id="rfc.iref.g.91"></span><span id="rfc.iref.g.92"></span><span id="rfc.iref.g.93"></span>  Via =  "Via" ":" 1#( received-protocol received-by [ comment ] )
    18511862  received-protocol = [ protocol-name "/" ] protocol-version
    18521863  protocol-name     = token
    … …  
    18711882         server at www.example.com. The request received by www.example.com would then have the following Via header field:
    18721883      </p>
    1873       <div id="rfc.figure.u.56"></div><pre class="text">    Via: 1.0 fred, 1.1 p.example.net (Apache/1.1)
     1884      <div id="rfc.figure.u.59"></div><pre class="text">    Via: 1.0 fred, 1.1 p.example.net (Apache/1.1)
    18741885</pre><p id="rfc.section.8.9.p.9">Proxies and gateways used as a portal through a network firewall <em class="bcp14">SHOULD NOT</em>, by default, forward the names and ports of hosts within the firewall region. This information <em class="bcp14">SHOULD</em> only be propagated if explicitly enabled. If not enabled, the received-by host of any host behind the firewall <em class="bcp14">SHOULD</em> be replaced by an appropriate pseudonym for that host.
    18751886      </p>
    … …  
    18771888         For example,
    18781889      </p>
    1879       <div id="rfc.figure.u.57"></div><pre class="text">    Via: 1.0 ricky, 1.1 ethel, 1.1 fred, 1.0 lucy
     1890      <div id="rfc.figure.u.60"></div><pre class="text">    Via: 1.0 ricky, 1.1 ethel, 1.1 fred, 1.0 lucy
    18801891</pre><p id="rfc.section.8.9.p.12">could be collapsed to</p>
    1881       <div id="rfc.figure.u.58"></div><pre class="text">    Via: 1.0 ricky, 1.1 mertz, 1.0 lucy
     1892      <div id="rfc.figure.u.61"></div><pre class="text">    Via: 1.0 ricky, 1.1 mertz, 1.0 lucy
    18821893</pre><p id="rfc.section.8.9.p.14">Applications <em class="bcp14">SHOULD NOT</em> combine multiple entries unless they are all under the same organizational control and the hosts have already been replaced
    18831894         by pseudonyms. Applications <em class="bcp14">MUST NOT</em> combine entries which have different received-protocol values.
    … …  
    23112322      </p>
    23122323      <p id="rfc.section.B.p.4">The character set of an entity-body <em class="bcp14">SHOULD</em> be labeled as the lowest common denominator of the character codes used within that body, with the exception that not labeling
    2313          the entity is preferred over labeling the entity with the labels US-ASCII or ISO-8859-1. See <a href="#Part3" id="rfc.xref.Part3.12"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>.
     2324         the entity is preferred over labeling the entity with the labels US-ASCII or ISO-8859-1. See <a href="#Part3" id="rfc.xref.Part3.15"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>.
    23142325      </p>
    23152326      <p id="rfc.section.B.p.5">Additional rules for requirements on parsing and encoding of dates and other potential problems with date encodings include:</p>
    … …  
    23942405      <p id="rfc.section.D.3.p.2">Transfer-coding and message lengths all interact in ways that required fixing exactly when chunked encoding is used (to allow
    23952406         for transfer encoding that may not be self delimiting); it was important to straighten out exactly how message lengths are
    2396          computed. (Sections <a href="#transfer.codings" title="Transfer Codings">3.4</a>, <a href="#message.length" title="Message Length">4.4</a>, <a href="#header.content-length" id="rfc.xref.header.content-length.2" title="Content-Length">8.2</a>, see also <a href="#Part3" id="rfc.xref.Part3.13"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a> and <a href="#Part6" id="rfc.xref.Part6.6"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>)
     2407         computed. (Sections <a href="#transfer.codings" title="Transfer Codings">3.4</a>, <a href="#message.length" title="Message Length">4.4</a>, <a href="#header.content-length" id="rfc.xref.header.content-length.2" title="Content-Length">8.2</a>, see also <a href="#Part3" id="rfc.xref.Part3.16"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a> and <a href="#Part6" id="rfc.xref.Part6.9"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>)
    23972408      </p>
    23982409      <p id="rfc.section.D.3.p.3">The use and interpretation of HTTP version numbers has been clarified by <a href="#RFC2145" id="rfc.xref.RFC2145.3"><cite title="Use and Interpretation of HTTP Version Numbers">[RFC2145]</cite></a>. Require proxies to upgrade requests to highest protocol version they support to deal with problems discovered in HTTP/1.0
    … …  
    24982509         <li>Get rid of unused rules LOALPHA and UPALPHA.</li>
    24992510         <li>Move "Product Tokens" section (back) into Part 1, as "token" is used in the definition of the Upgrade header.</li>
     2511         <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li>
    25002512      </ul>
    25012513      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
    … …  
    26982710            <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind">
    26992711                  <li class="indline1"><em>Pad1995</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Pad1995.1">7.1.1</a>, <a class="iref" href="#Pad1995"><b>12.2</b></a></li>
    2700                   <li class="indline1"><em>Part2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.1">3.2.1</a>, <a class="iref" href="#rfc.xref.Part2.2">4.2</a>, <a class="iref" href="#rfc.xref.Part2.3">4.2</a>, <a class="iref" href="#rfc.xref.Part2.4">4.3</a>, <a class="iref" href="#rfc.xref.Part2.5">5</a>, <a class="iref" href="#rfc.xref.Part2.6">5.1.2</a>, <a class="iref" href="#rfc.xref.Part2.7">6</a>, <a class="iref" href="#rfc.xref.Part2.8">6.1.1</a>, <a class="iref" href="#rfc.xref.Part2.9">7.1.2.2</a>, <a class="iref" href="#rfc.xref.Part2.10">7.1.4</a>, <a class="iref" href="#rfc.xref.Part2.11">7.2.3</a>, <a class="iref" href="#rfc.xref.Part2.12">7.2.3</a>, <a class="iref" href="#rfc.xref.Part2.13">7.2.3</a>, <a class="iref" href="#rfc.xref.Part2.14">7.2.3</a>, <a class="iref" href="#Part2"><b>12.1</b></a><ul class="ind">
    2701                         <li class="indline1"><em>Section 3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.4">4.3</a></li>
    2702                         <li class="indline1"><em>Section 4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.2">4.2</a>, <a class="iref" href="#rfc.xref.Part2.5">5</a></li>
    2703                         <li class="indline1"><em>Section 6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.3">4.2</a>, <a class="iref" href="#rfc.xref.Part2.7">6</a></li>
    2704                         <li class="indline1"><em>Section 8.1.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.9">7.1.2.2</a>, <a class="iref" href="#rfc.xref.Part2.10">7.1.4</a></li>
    2705                         <li class="indline1"><em>Section 8.9</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.6">5.1.2</a></li>
    2706                         <li class="indline1"><em>Section 9</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.8">6.1.1</a></li>
    2707                         <li class="indline1"><em>Section 9.1.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.11">7.2.3</a></li>
    2708                         <li class="indline1"><em>Section 9.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.14">7.2.3</a></li>
    2709                         <li class="indline1"><em>Section 9.4.15</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.1">3.2.1</a></li>
    2710                         <li class="indline1"><em>Section 10.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.12">7.2.3</a>, <a class="iref" href="#rfc.xref.Part2.13">7.2.3</a></li>
     2712                  <li class="indline1"><em>Part2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.1">2.3</a>, <a class="iref" href="#rfc.xref.Part2.2">2.3</a>, <a class="iref" href="#rfc.xref.Part2.3">3.2.1</a>, <a class="iref" href="#rfc.xref.Part2.4">4.2</a>, <a class="iref" href="#rfc.xref.Part2.5">4.2</a>, <a class="iref" href="#rfc.xref.Part2.6">4.3</a>, <a class="iref" href="#rfc.xref.Part2.7">5</a>, <a class="iref" href="#rfc.xref.Part2.8">5.1.2</a>, <a class="iref" href="#rfc.xref.Part2.9">6</a>, <a class="iref" href="#rfc.xref.Part2.10">6.1.1</a>, <a class="iref" href="#rfc.xref.Part2.11">7.1.2.2</a>, <a class="iref" href="#rfc.xref.Part2.12">7.1.4</a>, <a class="iref" href="#rfc.xref.Part2.13">7.2.3</a>, <a class="iref" href="#rfc.xref.Part2.14">7.2.3</a>, <a class="iref" href="#rfc.xref.Part2.15">7.2.3</a>, <a class="iref" href="#rfc.xref.Part2.16">7.2.3</a>, <a class="iref" href="#Part2"><b>12.1</b></a><ul class="ind">
     2713                        <li class="indline1"><em>Section 3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.6">4.3</a></li>
     2714                        <li class="indline1"><em>Section 4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.1">2.3</a>, <a class="iref" href="#rfc.xref.Part2.4">4.2</a>, <a class="iref" href="#rfc.xref.Part2.7">5</a></li>
     2715                        <li class="indline1"><em>Section 6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.2">2.3</a>, <a class="iref" href="#rfc.xref.Part2.5">4.2</a>, <a class="iref" href="#rfc.xref.Part2.9">6</a></li>
     2716                        <li class="indline1"><em>Section 8.1.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.11">7.1.2.2</a>, <a class="iref" href="#rfc.xref.Part2.12">7.1.4</a></li>
     2717                        <li class="indline1"><em>Section 8.9</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.8">5.1.2</a></li>
     2718                        <li class="indline1"><em>Section 9</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.10">6.1.1</a></li>
     2719                        <li class="indline1"><em>Section 9.1.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.13">7.2.3</a></li>
     2720                        <li class="indline1"><em>Section 9.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.16">7.2.3</a></li>
     2721                        <li class="indline1"><em>Section 9.4.15</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.3">3.2.1</a></li>
     2722                        <li class="indline1"><em>Section 10.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part2.14">7.2.3</a>, <a class="iref" href="#rfc.xref.Part2.15">7.2.3</a></li>
    27112723                     </ul>
    27122724                  </li>
    2713                   <li class="indline1"><em>Part3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.1">1.3</a>, <a class="iref" href="#rfc.xref.Part3.2">1.3</a>, <a class="iref" href="#rfc.xref.Part3.3">1.3</a>, <a class="iref" href="#rfc.xref.Part3.4">1.4</a>, <a class="iref" href="#rfc.xref.Part3.5">2.2</a>, <a class="iref" href="#rfc.xref.Part3.6">3.4</a>, <a class="iref" href="#rfc.xref.Part3.7">3.4</a>, <a class="iref" href="#rfc.xref.Part3.8">4.2</a>, <a class="iref" href="#rfc.xref.Part3.9">5</a>, <a class="iref" href="#rfc.xref.Part3.10">6</a>, <a class="iref" href="#rfc.xref.Part3.11">8.5</a>, <a class="iref" href="#Part3"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part3.12">B</a>, <a class="iref" href="#rfc.xref.Part3.13">D.3</a><ul class="ind">
    2714                         <li class="indline1"><em>Section 3.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.6">3.4</a>, <a class="iref" href="#rfc.xref.Part3.7">3.4</a></li>
     2725                  <li class="indline1"><em>Part3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.1">1.3</a>, <a class="iref" href="#rfc.xref.Part3.2">1.3</a>, <a class="iref" href="#rfc.xref.Part3.3">1.3</a>, <a class="iref" href="#rfc.xref.Part3.4">1.4</a>, <a class="iref" href="#rfc.xref.Part3.5">2.2</a>, <a class="iref" href="#rfc.xref.Part3.6">2.3</a>, <a class="iref" href="#rfc.xref.Part3.7">2.3</a>, <a class="iref" href="#rfc.xref.Part3.8">2.3</a>, <a class="iref" href="#rfc.xref.Part3.9">3.4</a>, <a class="iref" href="#rfc.xref.Part3.10">3.4</a>, <a class="iref" href="#rfc.xref.Part3.11">4.2</a>, <a class="iref" href="#rfc.xref.Part3.12">5</a>, <a class="iref" href="#rfc.xref.Part3.13">6</a>, <a class="iref" href="#rfc.xref.Part3.14">8.5</a>, <a class="iref" href="#Part3"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part3.15">B</a>, <a class="iref" href="#rfc.xref.Part3.16">D.3</a><ul class="ind">
     2726                        <li class="indline1"><em>Section 3.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.9">3.4</a>, <a class="iref" href="#rfc.xref.Part3.10">3.4</a></li>
    27152727                        <li class="indline1"><em>Section 3.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.5">2.2</a></li>
    2716                         <li class="indline1"><em>Section 3.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.11">8.5</a></li>
     2728                        <li class="indline1"><em>Section 3.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.14">8.5</a></li>
    27172729                        <li class="indline1"><em>Section 4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.1">1.3</a></li>
    2718                         <li class="indline1"><em>Section 4.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.8">4.2</a>, <a class="iref" href="#rfc.xref.Part3.9">5</a>, <a class="iref" href="#rfc.xref.Part3.10">6</a></li>
     2730                        <li class="indline1"><em>Section 4.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.8">2.3</a>, <a class="iref" href="#rfc.xref.Part3.11">4.2</a>, <a class="iref" href="#rfc.xref.Part3.12">5</a>, <a class="iref" href="#rfc.xref.Part3.13">6</a></li>
     2731                        <li class="indline1"><em>Section 4.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.7">2.3</a></li>
    27192732                        <li class="indline1"><em>Section 5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.2">1.3</a>, <a class="iref" href="#rfc.xref.Part3.3">1.3</a></li>
     2733                        <li class="indline1"><em>Section 6.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.6">2.3</a></li>
    27202734                        <li class="indline1"><em>Section A</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part3.4">1.4</a></li>
    27212735                     </ul>
    27222736                  </li>
    27232737                  <li class="indline1"><em>Part5</em>&nbsp;&nbsp;<a class="iref" href="#Part5"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part5.1">D.3</a></li>
    2724                   <li class="indline1"><em>Part6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">1.3</a>, <a class="iref" href="#rfc.xref.Part6.2">1.4</a>, <a class="iref" href="#rfc.xref.Part6.3">4.5</a>, <a class="iref" href="#rfc.xref.Part6.4">4.5</a>, <a class="iref" href="#rfc.xref.Part6.5">4.5</a>, <a class="iref" href="#Part6"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part6.6">D.3</a><ul class="ind">
     2738                  <li class="indline1"><em>Part6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">1.3</a>, <a class="iref" href="#rfc.xref.Part6.2">1.4</a>, <a class="iref" href="#rfc.xref.Part6.3">2.3</a>, <a class="iref" href="#rfc.xref.Part6.4">2.3</a>, <a class="iref" href="#rfc.xref.Part6.5">2.3</a>, <a class="iref" href="#rfc.xref.Part6.6">4.5</a>, <a class="iref" href="#rfc.xref.Part6.7">4.5</a>, <a class="iref" href="#rfc.xref.Part6.8">4.5</a>, <a class="iref" href="#Part6"><b>12.1</b></a>, <a class="iref" href="#rfc.xref.Part6.9">D.3</a><ul class="ind">
    27252739                        <li class="indline1"><em>Section 1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">1.3</a>, <a class="iref" href="#rfc.xref.Part6.2">1.4</a></li>
    2726                         <li class="indline1"><em>Section 16.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.3">4.5</a></li>
    2727                         <li class="indline1"><em>Section 16.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.4">4.5</a></li>
    2728                         <li class="indline1"><em>Section 16.6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.5">4.5</a></li>
     2740                        <li class="indline1"><em>Section 16.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.6">4.5</a></li>
     2741                        <li class="indline1"><em>Section 16.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.3">2.3</a>, <a class="iref" href="#rfc.xref.Part6.4">2.3</a>, <a class="iref" href="#rfc.xref.Part6.7">4.5</a></li>
     2742                        <li class="indline1"><em>Section 16.6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.5">2.3</a>, <a class="iref" href="#rfc.xref.Part6.8">4.5</a></li>
    27292743                     </ul>
    27302744                  </li>

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

    r206 r207  
    2323  <!ENTITY diff2045entity         "<xref target='Part3' x:rel='#differences.between.http.entities.and.rfc.2045.entities' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2424  <!ENTITY entity                 "<xref target='Part3' x:rel='#entity' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     25  <!ENTITY entity-body            "<xref target='Part3' x:rel='#entity.body' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2526  <!ENTITY entity-header-fields   "<xref target='Part3' x:rel='#entity.header.fields' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     27  <!ENTITY header-accept          "<xref target='Part3' x:rel='#header.accept' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2628  <!ENTITY header-cache-control   "<xref target='Part6' x:rel='#header.cache-control' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    2729  <!ENTITY header-expect          "<xref target='Part2' x:rel='#header.expect' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    … …  
    939941</artwork></figure>
    940942</section>
     943
     944<section title="ABNF Rules defined in other Parts of the Specification" anchor="abnf.dependencies">
     945<t>
     946  The ABNF rules below are defined in other parts:
     947</t>
     948<figure><!-- Part2--><artwork type="abnf2616">
     949  request-header =  &lt;request-header, defined in &request-header-fields;&gt;
     950  response-header = &lt;response-header, defined in &response-header-fields;&gt;
     951</artwork></figure>
     952<figure><!-- Part3--><artwork type="abnf2616">
     953  accept-params   = &lt;accept-params, defined in &header-accept;&gt;
     954  entity-body     = &lt;entity-body, defined in &entity-body;&gt;
     955  entity-header   = &lt;entity-header, defined in &entity-header-fields;&gt;
     956</artwork></figure>
     957<figure><!-- Part6--><artwork type="abnf2616">
     958  Cache-Control   = &lt;Cache-Control, defined in &header-pragma;&gt;
     959  Pragma          = &lt;Pragma, defined in &header-pragma;&gt;
     960  Warning         = &lt;Warning, defined in &header-warning;&gt;
     961</artwork></figure>
     962</section>
     963
    941964</section>
    942965
    … …  
    42634286      in the definition of the Upgrade header.
    42644287    </t>
     4288    <t>
     4289      Add explicit references to BNF syntax and rules imported from other parts of the specification.
     4290    </t>
    42654291  </list>
    42664292</t>

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

    r206 r207  
    633633  quoted-string = &lt;quoted-string, defined in <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>&gt;
    634634  token         = &lt;token, defined in <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>&gt;
    635 </pre><p id="rfc.section.2.p.4">The ABNF rules below are defined in other parts:</p>
     635</pre><div id="abnf.dependencies">
     636         <p id="rfc.section.2.p.4">The ABNF rules below are defined in other parts:</p>
     637      </div>
    636638      <div id="rfc.figure.u.3"></div><pre class="inline">  absoluteURI   = &lt;absoluteURI, defined in <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#general.syntax" title="General Syntax">Section 3.2.1</a>&gt;
    637   Accept        = &lt;Accept, defined in <a href="#Part3" id="rfc.xref.Part3.1"><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>&gt;
     639  fragment      = &lt;fragment, defined in <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#general.syntax" title="General Syntax">Section 3.2.1</a>&gt;
     640  Host          = &lt;Host, defined in <a href="#Part1" id="rfc.xref.Part1.10"><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 8.4</a>&gt;
     641  HTTP-date     = &lt;HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#full.date" title="Full Date">Section 3.3.1</a>&gt;
     642  product       = &lt;product, defined in <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 3.5</a>&gt;
     643  relativeURI   = &lt;relativeURI, defined in <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#general.syntax" title="General Syntax">Section 3.2.1</a>&gt;
     644  TE            = &lt;TE, defined in <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 8.8</a>&gt;
     645</pre><div id="rfc.figure.u.4"></div><pre class="inline">  Accept        = &lt;Accept, defined in <a href="#Part3" id="rfc.xref.Part3.1"><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>&gt;
    638646  Accept-Charset =
    639647             &lt;Accept-Charset, defined in <a href="#Part3" id="rfc.xref.Part3.2"><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>&gt;
    … …  
    642650  Accept-Language =
    643651             &lt;Accept-Language, defined in <a href="#Part3" id="rfc.xref.Part3.4"><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>&gt;
    644   Accept-Ranges = &lt;Accept-Ranges, defined in <a href="#Part5" id="rfc.xref.Part5.1"><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 6.1</a>&gt;
    645   Age           = &lt;Age, defined in <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.age" title="Age">Section 16.1</a>&gt;
    646   Authorization = &lt;Authorization, defined in <a href="#Part7" id="rfc.xref.Part7.1"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a>&gt;
    647   delta-seconds = &lt;delta-seconds, defined in <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.age" title="Age">Section 16.1</a>&gt;
    648   ETag          = &lt;ETag, defined in <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.etag" title="ETag">Section 7.1</a>&gt;
    649   fragment      = &lt;fragment, defined in <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#general.syntax" title="General Syntax">Section 3.2.1</a>&gt;
    650   HTTP-date     = &lt;HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#full.date" title="Full Date">Section 3.3.1</a>&gt;
    651   Host          = &lt;Host, defined in <a href="#Part1" id="rfc.xref.Part1.11"><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 8.4</a>&gt;
     652</pre><div id="rfc.figure.u.5"></div><pre class="inline">  ETag          = &lt;ETag, defined in <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.etag" title="ETag">Section 7.1</a>&gt;
    652653  If-Match      = &lt;If-Match, defined in <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.if-match" title="If-Match">Section 7.2</a>&gt;
    653654  If-Modified-Since =
    654655             &lt;If-Modified-Since, defined in <a href="#Part4" id="rfc.xref.Part4.3"><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 7.3</a>&gt;
    655656  If-None-Match = &lt;If-None-Match, defined in <a href="#Part4" id="rfc.xref.Part4.4"><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 7.4</a>&gt;
    656   If-Range      = &lt;If-Range, defined in <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.if-range" title="If-Range">Section 6.3</a>&gt;
    657657  If-Unmodified-Since =
    658658             &lt;If-Unmodified-Since, defined in <a href="#Part4" id="rfc.xref.Part4.5"><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 7.5</a>&gt;
    659   product       = &lt;product, defined in <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 3.5</a>&gt;
     659</pre><div id="rfc.figure.u.6"></div><pre class="inline">  Accept-Ranges = &lt;Accept-Ranges, defined in <a href="#Part5" id="rfc.xref.Part5.1"><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 6.1</a>&gt;
     660  If-Range      = &lt;If-Range, defined in <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.if-range" title="If-Range">Section 6.3</a>&gt;
     661  Range         = &lt;Range, defined in <a href="#Part5" id="rfc.xref.Part5.3"><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 6.4</a>&gt;
     662</pre><div id="rfc.figure.u.7"></div><pre class="inline">  Age           = &lt;Age, defined in <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.age" title="Age">Section 16.1</a>&gt;
     663  delta-seconds = &lt;delta-seconds, defined in <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.age" title="Age">Section 16.1</a>&gt;
     664  Vary          = &lt;Vary, defined in <a href="#Part6" id="rfc.xref.Part6.3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.vary" title="Vary">Section 16.5</a>&gt;
     665</pre><div id="rfc.figure.u.8"></div><pre class="inline">  Authorization = &lt;Authorization, defined in <a href="#Part7" id="rfc.xref.Part7.1"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a>&gt;
    660666  Proxy-Authenticate =
    661667             &lt;Proxy-Authenticate, defined in <a href="#Part7" id="rfc.xref.Part7.2"><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>&gt;
    662668  Proxy-Authorization =
    663669             &lt;Proxy-Authorization, defined in <a href="#Part7" id="rfc.xref.Part7.3"><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>&gt;
    664   Range         = &lt;Range, defined in <a href="#Part5" id="rfc.xref.Part5.3"><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 6.4</a>&gt;
    665   relativeURI   = &lt;relativeURI, defined in <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#general.syntax" title="General Syntax">Section 3.2.1</a>&gt;
    666   TE            = &lt;TE, defined in <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 8.8</a>&gt;
    667   Vary          = &lt;Vary, defined in <a href="#Part6" id="rfc.xref.Part6.3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.vary" title="Vary">Section 16.5</a>&gt;
    668670  WWW-Authenticate =
    669671             &lt;WWW-Authenticate, defined in <a href="#Part7" id="rfc.xref.Part7.4"><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>&gt;
    670672</pre><h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="method" href="#method">Method</a></h1>
    671673      <p id="rfc.section.3.p.1">The Method token indicates the method to be performed on the resource identified by the Request-URI. The method is case-sensitive.</p>
    672       <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span>  Method         = "OPTIONS"                ; <a href="#OPTIONS" id="rfc.xref.OPTIONS.1" title="OPTIONS">Section&nbsp;8.2</a>
     674      <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span>  Method         = "OPTIONS"                ; <a href="#OPTIONS" id="rfc.xref.OPTIONS.1" title="OPTIONS">Section&nbsp;8.2</a>
    673675                 | "GET"                    ; <a href="#GET" id="rfc.xref.GET.1" title="GET">Section&nbsp;8.3</a>
    674676                 | "HEAD"                   ; <a href="#HEAD" id="rfc.xref.HEAD.1" title="HEAD">Section&nbsp;8.4</a>
    … …  
    690692         method invocation.
    691693      </p>
    692       <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.3"></span>  request-header = Accept                   ; <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>
     694      <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.3"></span>  request-header = Accept                   ; <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>
    693695                 | Accept-Charset           ; <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>
    694696                 | Accept-Encoding          ; <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>
    … …  
    721723         are presented below. The reason phrases listed here are only recommendations -- they <em class="bcp14">MAY</em> be replaced by local equivalents without affecting the protocol.
    722724      </p>
    723       <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span>  Status-Code    =
     725      <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span>  Status-Code    =
    724726         "100"  ; <a href="#status.100" id="rfc.xref.status.100.1" title="100 Continue">Section&nbsp;9.1.1</a>: Continue
    725727       | "101"  ; <a href="#status.101" id="rfc.xref.status.101.1" title="101 Switching Protocols">Section&nbsp;9.1.2</a>: Switching Protocols
    … …  
    777779         the Request-URI.
    778780      </p>
    779       <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.7"></span>  response-header = Accept-Ranges           ; <a href="#Part5" id="rfc.xref.Part5.6"><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 6.1</a>
     781      <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.7"></span>  response-header = Accept-Ranges           ; <a href="#Part5" id="rfc.xref.Part5.6"><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 6.1</a>
    780782                  | Age                     ; <a href="#Part6" id="rfc.xref.Part6.4"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.age" title="Age">Section 16.1</a>
    781783                  | ETag                    ; <a href="#Part4" id="rfc.xref.Part4.10"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.etag" title="ETag">Section 7.1</a>
    … …  
    13871389         of this field is strictly to inform the recipient of valid methods associated with the resource. An Allow header field <em class="bcp14">MUST</em> be present in a 405 (Method Not Allowed) response.
    13881390      </p>
    1389       <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.9"></span>  Allow   = "Allow" ":" #Method
     1391      <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.9"></span>  Allow   = "Allow" ":" #Method
    13901392</pre><p id="rfc.section.10.1.p.3">Example of use:</p>
    1391       <div id="rfc.figure.u.9"></div><pre class="text">       Allow: GET, HEAD, PUT
     1393      <div id="rfc.figure.u.14"></div><pre class="text">       Allow: GET, HEAD, PUT
    13921394</pre><p id="rfc.section.10.1.p.5">This field cannot prevent a client from trying other methods. However, the indications given by the Allow header field value <em class="bcp14">SHOULD</em> be followed. The actual set of allowed methods is defined by the origin server at the time of each request.
    13931395      </p>
    … …  
    14021404      <h2 id="rfc.section.10.2"><a href="#rfc.section.10.2">10.2</a>&nbsp;<a id="header.expect" href="#header.expect">Expect</a></h2>
    14031405      <p id="rfc.section.10.2.p.1">The Expect request-header field is used to indicate that particular server behaviors are required by the client.</p>
    1404       <div id="rfc.figure.u.10"></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>  Expect       =  "Expect" ":" 1#expectation
     1406      <div id="rfc.figure.u.15"></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>  Expect       =  "Expect" ":" 1#expectation
    14051407 
    14061408  expectation  =  "100-continue" | expectation-extension
    … …  
    14281430      <p id="rfc.section.10.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/rfc2822#section-3.4">Section 3.4</a> of <a href="#RFC2822" id="rfc.xref.RFC2822.1"><cite title="Internet Message Format">[RFC2822]</cite></a>:
    14291431      </p>
    1430       <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.14"></span>  From    = "From" ":" mailbox
     1432      <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.14"></span>  From    = "From" ":" mailbox
    14311433 
    14321434  mailbox = &lt;mailbox, defined in <a href="#RFC2822" id="rfc.xref.RFC2822.2"><cite title="Internet Message Format">[RFC2822]</cite></a>, <a href="http://tools.ietf.org/html/rfc2822#section-3.4">Section 3.4</a>&gt;
    14331435</pre><p id="rfc.section.10.3.p.3">An example is:</p>
    1434       <div id="rfc.figure.u.12"></div><pre class="text">    From: webmaster@example.org
     1436      <div id="rfc.figure.u.17"></div><pre class="text">    From: webmaster@example.org
    14351437</pre><p id="rfc.section.10.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
    14361438         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 so that the person responsible for running the robot can be contacted if problems occur on the receiving
    … …  
    14521454         URI.
    14531455      </p>
    1454       <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.15"></span>  Location       = "Location" ":" absoluteURI [ "#" fragment ]
     1456      <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.15"></span>  Location       = "Location" ":" absoluteURI [ "#" fragment ]
    14551457</pre><p id="rfc.section.10.4.p.3">An example is:</p>
    1456       <div id="rfc.figure.u.14"></div><pre class="text">    Location: http://www.example.org/pub/WWW/People.html
     1458      <div id="rfc.figure.u.19"></div><pre class="text">    Location: http://www.example.org/pub/WWW/People.html
    14571459</pre><p id="rfc.section.10.4.p.5"> </p>
    14581460      <dl class="empty">
    … …  
    14751477         useful when the client is attempting to trace a request chain which appears to be failing or looping in mid-chain.
    14761478      </p>
    1477       <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.16"></span>  Max-Forwards   = "Max-Forwards" ":" 1*DIGIT
     1479      <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.16"></span>  Max-Forwards   = "Max-Forwards" ":" 1*DIGIT
    14781480</pre><p id="rfc.section.10.5.p.3">The Max-Forwards value is a decimal integer indicating the remaining number of times this request message may be forwarded.</p>
    14791481      <p id="rfc.section.10.5.p.4">Each proxy or gateway recipient of a TRACE or OPTIONS request containing a Max-Forwards header field <em class="bcp14">MUST</em> check and update its value prior to forwarding the request. If the received value is zero (0), the recipient <em class="bcp14">MUST NOT</em> forward the request; instead, it <em class="bcp14">MUST</em> respond as the final recipient. If the received Max-Forwards value is greater than zero, then the forwarded message <em class="bcp14">MUST</em> contain an updated Max-Forwards field with a value decremented by one (1).
    … …  
    14901492         obsolete or mistyped links to be traced for maintenance. The Referer field <em class="bcp14">MUST NOT</em> be sent if the Request-URI was obtained from a source that does not have its own URI, such as input from the user keyboard.
    14911493      </p>
    1492       <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.17"></span>  Referer        = "Referer" ":" ( absoluteURI | relativeURI )
     1494      <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.17"></span>  Referer        = "Referer" ":" ( absoluteURI | relativeURI )
    14931495</pre><p id="rfc.section.10.6.p.3">Example:</p>
    1494       <div id="rfc.figure.u.17"></div><pre class="text">    Referer: http://www.example.org/hypertext/Overview.html
     1496      <div id="rfc.figure.u.22"></div><pre class="text">    Referer: http://www.example.org/hypertext/Overview.html
    14951497</pre><p id="rfc.section.10.6.p.5">If the field value is a relative URI, it <em class="bcp14">SHOULD</em> be interpreted relative to the 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;12.2</a> for security considerations.
    14961498      </p>
    … …  
    15031505         the time of the response.
    15041506      </p>
    1505       <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.18"></span>  Retry-After  = "Retry-After" ":" ( HTTP-date | delta-seconds )
     1507      <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.18"></span>  Retry-After  = "Retry-After" ":" ( HTTP-date | delta-seconds )
    15061508</pre><p id="rfc.section.10.7.p.3">Two examples of its use are</p>
    1507       <div id="rfc.figure.u.19"></div><pre class="text">    Retry-After: Fri, 31 Dec 1999 23:59:59 GMT
     1509      <div id="rfc.figure.u.24"></div><pre class="text">    Retry-After: Fri, 31 Dec 1999 23:59:59 GMT
    15081510    Retry-After: 120
    15091511</pre><p id="rfc.section.10.7.p.5">In the latter example, the delay is 2 minutes.</p>
    … …  
    15151517         for identifying the application.
    15161518      </p>
    1517       <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.19"></span>  Server         = "Server" ":" 1*( product | comment )
     1519      <div id="rfc.figure.u.25"></div><pre class="inline"><span id="rfc.iref.g.19"></span>  Server         = "Server" ":" 1*( product | comment )
    15181520</pre><p id="rfc.section.10.8.p.3">Example:</p>
    1519       <div id="rfc.figure.u.21"></div><pre class="text">    Server: CERN/3.0 libwww/2.17
     1521      <div id="rfc.figure.u.26"></div><pre class="text">    Server: CERN/3.0 libwww/2.17
    15201522</pre><p id="rfc.section.10.8.p.5">If the response is being forwarded through a proxy, the proxy application <em class="bcp14">MUST NOT</em> modify the Server response-header. Instead, it <em class="bcp14">MUST</em> include a Via field (as described in <a href="p1-messaging.html#header.via" title="Via">Section 8.9</a> of <a href="#Part1" id="rfc.xref.Part1.23"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
    15211523      </p>
    … …  
    15341536         product tokens are listed in order of their significance for identifying the application.
    15351537      </p>
    1536       <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.20"></span>  User-Agent     = "User-Agent" ":" 1*( product | comment )
     1538      <div id="rfc.figure.u.27"></div><pre class="inline"><span id="rfc.iref.g.20"></span>  User-Agent     = "User-Agent" ":" 1*( product | comment )
    15371539</pre><p id="rfc.section.10.9.p.3">Example:</p>
    1538       <div id="rfc.figure.u.23"></div><pre class="text">    User-Agent: CERN-LineMode/2.15 libwww/2.17b3
     1540      <div id="rfc.figure.u.28"></div><pre class="text">    User-Agent: CERN-LineMode/2.15 libwww/2.17b3
    15391541</pre><h1 id="rfc.section.11"><a href="#rfc.section.11">11.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
    15401542      <p id="rfc.section.11.p.1"> <span class="comment">[rfc.comment.1: TBD.]</span>
    … …  
    19481950                        <li class="indline1"><em>Section 3.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.20">9.5.6</a></li>
    19491951                        <li class="indline1"><em>Section 3.2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.8">2</a>, <a class="iref" href="#rfc.xref.Part1.9">2</a>, <a class="iref" href="#rfc.xref.Part1.13">2</a></li>
    1950                         <li class="indline1"><em>Section 3.3.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.10">2</a></li>
     1952                        <li class="indline1"><em>Section 3.3.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.11">2</a></li>
    19511953                        <li class="indline1"><em>Section 3.5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.12">2</a>, <a class="iref" href="#rfc.xref.Part1.22">10.8</a>, <a class="iref" href="#rfc.xref.Part1.24">10.9</a></li>
    19521954                        <li class="indline1"><em>Section 4.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.17">7</a></li>
    19531955                        <li class="indline1"><em>Section 7.2.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.19">9.1.1</a>, <a class="iref" href="#rfc.xref.Part1.21">10.2</a></li>
    1954                         <li class="indline1"><em>Section 8.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.11">2</a>, <a class="iref" href="#rfc.xref.Part1.15">4</a></li>
     1956                        <li class="indline1"><em>Section 8.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.10">2</a>, <a class="iref" href="#rfc.xref.Part1.15">4</a></li>
    19551957                        <li class="indline1"><em>Section 8.8</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.14">2</a>, <a class="iref" href="#rfc.xref.Part1.16">4</a></li>
    19561958                        <li class="indline1"><em>Section 8.9</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.18">8.8</a>, <a class="iref" href="#rfc.xref.Part1.23">10.8</a>, <a class="iref" href="#rfc.xref.Part1.25">A.2</a></li>

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

    r206 r207  
    305305  token         = &lt;token, defined in &basic-rules;&gt;
    306306</artwork></figure>
    307 <t>
     307<t anchor="abnf.dependencies">
    308308  The ABNF rules below are defined in other parts:
    309309</t>
    310 <figure><artwork type="abnf2616">
     310<figure><!--Part1--><artwork type="abnf2616">
    311311  absoluteURI   = &lt;absoluteURI, defined in &general-syntax;&gt;
     312  fragment      = &lt;fragment, defined in &general-syntax;&gt;
     313  Host          = &lt;Host, defined in &header-host;&gt;
     314  HTTP-date     = &lt;HTTP-date, defined in &full-date;&gt;
     315  product       = &lt;product, defined in &product-tokens;&gt;
     316  relativeURI   = &lt;relativeURI, defined in &general-syntax;&gt;
     317  TE            = &lt;TE, defined in &header-te;&gt;
     318</artwork></figure>
     319<figure><!--Part3--><artwork type="abnf2616">
    312320  Accept        = &lt;Accept, defined in &header-accept;&gt;
    313321  Accept-Charset =
    … …  
    317325  Accept-Language =
    318326             &lt;Accept-Language, defined in &header-accept-language;&gt;
    319   Accept-Ranges = &lt;Accept-Ranges, defined in &header-accept-ranges;&gt;
    320   Age           = &lt;Age, defined in &header-age;&gt;
    321   Authorization = &lt;Authorization, defined in &header-authorization;&gt;
    322   delta-seconds = &lt;delta-seconds, defined in &header-age;&gt;
     327</artwork></figure>
     328<figure><!--Part4--><artwork type="abnf2616">
    323329  ETag          = &lt;ETag, defined in &header-etag;&gt;
    324   fragment      = &lt;fragment, defined in &general-syntax;&gt;
    325   HTTP-date     = &lt;HTTP-date, defined in &full-date;&gt;
    326   Host          = &lt;Host, defined in &header-host;&gt;
    327330  If-Match      = &lt;If-Match, defined in &header-if-match;&gt;
    328331  If-Modified-Since =
    329332             &lt;If-Modified-Since, defined in &header-if-modified-since;&gt;
    330333  If-None-Match = &lt;If-None-Match, defined in &header-if-none-match;&gt;
    331   If-Range      = &lt;If-Range, defined in &header-if-range;&gt;
    332334  If-Unmodified-Since =
    333335             &lt;If-Unmodified-Since, defined in &header-if-unmodified-since;&gt;
    334   product       = &lt;product, defined in &product-tokens;&gt;
     336</artwork></figure>
     337<figure><!--Part5--><artwork type="abnf2616">
     338  Accept-Ranges = &lt;Accept-Ranges, defined in &header-accept-ranges;&gt;
     339  If-Range      = &lt;If-Range, defined in &header-if-range;&gt;
     340  Range         = &lt;Range, defined in &header-range;&gt;
     341</artwork></figure>
     342<figure><!--Part6--><artwork type="abnf2616">
     343  Age           = &lt;Age, defined in &header-age;&gt;
     344  delta-seconds = &lt;delta-seconds, defined in &header-age;&gt;
     345  Vary          = &lt;Vary, defined in &header-vary;&gt;
     346</artwork><!--Part7--></figure>
     347<figure><artwork type="abnf2616">
     348  Authorization = &lt;Authorization, defined in &header-authorization;&gt;
    335349  Proxy-Authenticate =
    336350             &lt;Proxy-Authenticate, defined in &header-proxy-authenticate;&gt;
    337351  Proxy-Authorization =
    338352             &lt;Proxy-Authorization, defined in &header-proxy-authorization;&gt;
    339   Range         = &lt;Range, defined in &header-range;&gt;
    340   relativeURI   = &lt;relativeURI, defined in &general-syntax;&gt;
    341   TE            = &lt;TE, defined in &header-te;&gt;
    342   Vary          = &lt;Vary, defined in &header-vary;&gt;
    343353  WWW-Authenticate =
    344354             &lt;WWW-Authenticate, defined in &header-www-authenticate;&gt;

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

    r206 r207  
    592592</pre><div id="rfc.figure.u.2"></div><pre class="inline">  quoted-string  = &lt;quoted-string, defined in <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>&gt;
    593593  token          = &lt;token, defined in <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>&gt;
    594 </pre><p id="rfc.section.2.p.4">The ABNF rules below are defined in other parts:</p>
     594</pre><div id="abnf.dependencies">
     595         <p id="rfc.section.2.p.4">The ABNF rules below are defined in other parts:</p>
     596      </div>
    595597      <div id="rfc.figure.u.3"></div><pre class="inline">  absoluteURI    = &lt;absoluteURI, defined in <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#general.syntax" title="General Syntax">Section 3.2.1</a>&gt;
    596   Allow          = &lt;Allow, defined in <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#header.allow" title="Allow">Section 10.1</a>&gt;
    597598  Content-Length = &lt;Content-Length, defined in <a href="#Part1" id="rfc.xref.Part1.9"><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 8.2</a>&gt;
    598   Content-Range  = &lt;Content-Range, defined in <a href="#Part5" id="rfc.xref.Part5.1"><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 6.2</a>&gt;
    599   Expires        = &lt;Expires, defined in <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.expires" title="Expires">Section 16.3</a>&gt;
    600   Last-Modified  = &lt;Last-Modified, defined in <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.last-modified" title="Last-Modified">Section 7.6</a>&gt;
    601   message-header = &lt;message-header, defined in <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#message.headers" title="Message Headers">Section 4.2</a>&gt;
    602   relativeURI    = &lt;relativeURI, defined in <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#general.syntax" title="General Syntax">Section 3.2.1</a>&gt;
     599  relativeURI    = &lt;relativeURI, defined in <a href="#Part1" id="rfc.xref.Part1.10"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#general.syntax" title="General Syntax">Section 3.2.1</a>&gt;
     600  message-header = &lt;message-header, defined in <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#message.headers" title="Message Headers">Section 4.2</a>&gt;
     601</pre><div id="rfc.figure.u.4"></div><pre class="inline">  Allow          = &lt;Allow, defined in <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#header.allow" title="Allow">Section 10.1</a>&gt;
     602</pre><div id="rfc.figure.u.5"></div><pre class="inline">  Last-Modified  = &lt;Last-Modified, defined in <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.last-modified" title="Last-Modified">Section 7.6</a>&gt;
     603</pre><div id="rfc.figure.u.6"></div><pre class="inline">  Content-Range  = &lt;Content-Range, defined in <a href="#Part5" id="rfc.xref.Part5.1"><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 6.2</a>&gt;
     604</pre><div id="rfc.figure.u.7"></div><pre class="inline">  Expires        = &lt;Expires, defined in <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.expires" title="Expires">Section 16.3</a>&gt;
    603605</pre><h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="protocol.parameters" href="#protocol.parameters">Protocol Parameters</a></h1>
    604606      <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="character.sets" href="#character.sets">Character Sets</a></h2>
    … …  
    620622         Set registry (&lt;<a href="http://www.iana.org/assignments/character-sets">http://www.iana.org/assignments/character-sets</a>&gt;).
    621623      </p>
    622       <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.1"></span>  charset = token
     624      <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.1"></span>  charset = token
    623625</pre><p id="rfc.section.3.1.p.6">Although HTTP allows an arbitrary token to be used as a charset value, any token that has a predefined value within the IANA
    624626         Character Set registry <em class="bcp14">MUST</em> represent the character set defined by that registry. Applications <em class="bcp14">SHOULD</em> limit their use of character sets to those defined by the IANA registry.
    … …  
    643645         decoded by the recipient.
    644646      </p>
    645       <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.2"></span>  content-coding   = token
     647      <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.2"></span>  content-coding   = token
    646648</pre><p id="rfc.section.3.2.p.3">All content-coding values are case-insensitive. HTTP/1.1 uses content-coding values in the Accept-Encoding (<a href="#header.accept-encoding" id="rfc.xref.header.accept-encoding.1" title="Accept-Encoding">Section&nbsp;6.3</a>) and Content-Encoding (<a href="#header.content-encoding" id="rfc.xref.header.content-encoding.1" title="Content-Encoding">Section&nbsp;6.5</a>) header fields. Although the value describes the content-coding, what is more important is that it indicates what decoding
    647649         mechanism will be required to remove the encoding.
    … …  
    687689      <p id="rfc.section.3.3.p.1">HTTP uses Internet Media Types <a href="#RFC2046" id="rfc.xref.RFC2046.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types">[RFC2046]</cite></a> in the Content-Type (<a href="#header.content-type" id="rfc.xref.header.content-type.1" title="Content-Type">Section&nbsp;6.9</a>) and Accept (<a href="#header.accept" id="rfc.xref.header.accept.1" title="Accept">Section&nbsp;6.1</a>) header fields in order to provide open and extensible data typing and type negotiation.
    688690      </p>
    689       <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span>  media-type     = type "/" subtype *( ";" parameter )
     691      <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span>  media-type     = type "/" subtype *( ";" parameter )
    690692  type           = token
    691693  subtype        = token
    692694</pre><p id="rfc.section.3.3.p.3">Parameters <em class="bcp14">MAY</em> follow the type/subtype in the form of attribute/value pairs.
    693695      </p>
    694       <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span>  parameter               = attribute "=" value
     696      <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span>  parameter               = attribute "=" value
    695697  attribute               = token
    696698  value                   = token | quoted-string
    … …  
    745747         a quality value of 0, then content with this parameter is `not acceptable' for the client. HTTP/1.1 applications <em class="bcp14">MUST NOT</em> generate more than three digits after the decimal point. User configuration of these values <em class="bcp14">SHOULD</em> also be limited in this fashion.
    746748      </p>
    747       <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.10"></span>  qvalue         = ( "0" [ "." 0*3DIGIT ] )
     749      <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.10"></span>  qvalue         = ( "0" [ "." 0*3DIGIT ] )
    748750                 | ( "1" [ "." 0*3("0") ] )
    749751</pre><p id="rfc.section.3.4.p.3">"Quality values" is a misnomer, since these values merely represent relative degradation in desired quality.</p>
    … …  
    755757      <p id="rfc.section.3.5.p.2">The syntax and registry of HTTP language tags is the same as that defined by <a href="#RFC1766" id="rfc.xref.RFC1766.1"><cite title="Tags for the Identification of Languages">[RFC1766]</cite></a>. In summary, a language tag is composed of 1 or more parts: A primary language tag and a possibly empty series of subtags:
    756758      </p>
    757       <div id="rfc.figure.u.9"></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>  language-tag  = primary-tag *( "-" subtag )
     759      <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>  language-tag  = primary-tag *( "-" subtag )
    758760  primary-tag   = 1*8ALPHA
    759761  subtag        = 1*8ALPHA
    … …  
    761763         by the IANA. Example tags include:
    762764      </p>
    763       <div id="rfc.figure.u.10"></div><pre class="text">    en, en-US, en-cockney, i-cherokee, x-pig-latin
     765      <div id="rfc.figure.u.14"></div><pre class="text">    en, en-US, en-cockney, i-cherokee, x-pig-latin
    764766</pre><p id="rfc.section.3.5.p.6">where any two-letter primary-tag is an ISO-639 language abbreviation and any two-letter initial subtag is an ISO-3166 country
    765767         code. (The last three tags above are not registered tags; all but the last are examples of tags which could be registered
    … …  
    777779         by the request.
    778780      </p>
    779       <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span>  entity-header  = Allow                    ; <a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#header.allow" title="Allow">Section 10.1</a>
     781      <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span>  entity-header  = Allow                    ; <a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#header.allow" title="Allow">Section 10.1</a>
    780782                 | Content-Encoding         ; <a href="#header.content-encoding" id="rfc.xref.header.content-encoding.2" title="Content-Encoding">Section&nbsp;6.5</a>
    781783                 | Content-Language         ; <a href="#header.content-language" id="rfc.xref.header.content-language.1" title="Content-Language">Section&nbsp;6.6</a>
    … …  
    795797      <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a id="entity.body" href="#entity.body">Entity Body</a></h2>
    796798      <p id="rfc.section.4.2.p.1">The entity-body (if any) sent with an HTTP request or response is in a format and encoding defined by the entity-header fields.</p>
    797       <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.16"></span>  entity-body    = *OCTET
     799      <div id="rfc.figure.u.16"></div><pre class="inline"><span id="rfc.iref.g.16"></span>  entity-body    = *OCTET
    798800</pre><p id="rfc.section.4.2.p.3">An entity-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 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. The entity-body is obtained from the message-body by decoding any Transfer-Encoding that might have been applied to ensure
    799801         safe and proper transfer of the message.
    … …  
    803805         and Content-Encoding. These define a two-layer, ordered encoding model:
    804806      </p>
    805       <div id="rfc.figure.u.13"></div><pre class="text">    entity-body := Content-Encoding( Content-Type( data ) )
     807      <div id="rfc.figure.u.17"></div><pre class="text">    entity-body := Content-Encoding( Content-Type( data ) )
    806808</pre><p id="rfc.section.4.2.1.p.3">Content-Type specifies the media type of the underlying data. Content-Encoding may be used to indicate any additional content
    807809         codings applied to the data, usually for the purpose of data compression, that are a property of the requested resource. There
    … …  
    907909         for an in-line image.
    908910      </p>
    909       <div id="rfc.figure.u.14"></div><pre class="inline"><span id="rfc.iref.g.17"></span><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></span>  Accept         = "Accept" ":"
     911      <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.17"></span><span id="rfc.iref.g.18"></span><span id="rfc.iref.g.19"></span><span id="rfc.iref.g.20"></span>  Accept         = "Accept" ":"
    910912                   #( media-range [ accept-params ] )
    911913 
    … …  
    931933      </dl>
    932934      <p id="rfc.section.6.1.p.5">The example</p>
    933       <div id="rfc.figure.u.15"></div><pre class="text">    Accept: audio/*; q=0.2, audio/basic
     935      <div id="rfc.figure.u.19"></div><pre class="text">    Accept: audio/*; q=0.2, audio/basic
    934936</pre><p id="rfc.section.6.1.p.7"> <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
    935937         quality."
    … …  
    940942      </p>
    941943      <p id="rfc.section.6.1.p.9">A more elaborate example is</p>
    942       <div id="rfc.figure.u.16"></div><pre class="text">    Accept: text/plain; q=0.5, text/html,
     944      <div id="rfc.figure.u.20"></div><pre class="text">    Accept: text/plain; q=0.5, text/html,
    943945            text/x-dvi; q=0.8, text/x-c
    944946</pre><p id="rfc.section.6.1.p.11">Verbally, this would be interpreted as "text/html and text/x-c are the preferred media types, but if they do not exist, then
    … …  
    948950         to a given type, the most specific reference has precedence. For example,
    949951      </p>
    950       <div id="rfc.figure.u.17"></div><pre class="text">    Accept: text/*, text/html, text/html;level=1, */*
     952      <div id="rfc.figure.u.21"></div><pre class="text">    Accept: text/*, text/html, text/html;level=1, */*
    951953</pre><p id="rfc.section.6.1.p.14">have the following precedence:</p>
    952       <div id="rfc.figure.u.18"></div><pre class="text">    1) text/html;level=1
     954      <div id="rfc.figure.u.22"></div><pre class="text">    1) text/html;level=1
    953955    2) text/html
    954956    3) text/*
    … …  
    957959         which matches that type. For example,
    958960      </p>
    959       <div id="rfc.figure.u.19"></div><pre class="text">    Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1,
     961      <div id="rfc.figure.u.23"></div><pre class="text">    Accept: text/*;q=0.3, text/html;q=0.7, text/html;level=1,
    960962            text/html;level=2;q=0.4, */*;q=0.5
    961963</pre><p id="rfc.section.6.1.p.18">would cause the following values to be associated:</p>
    962       <div id="rfc.figure.u.20"></div><pre class="text">    text/html;level=1         = 1
     964      <div id="rfc.figure.u.24"></div><pre class="text">    text/html;level=1         = 1
    963965    text/html                 = 0.7
    964966    text/plain                = 0.3
    … …  
    976978         to a server which is capable of representing documents in those character sets.
    977979      </p>
    978       <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.21"></span>  Accept-Charset = "Accept-Charset" ":"
     980      <div id="rfc.figure.u.25"></div><pre class="inline"><span id="rfc.iref.g.21"></span>  Accept-Charset = "Accept-Charset" ":"
    979981          1#( ( charset | "*" ) [ ";" "q" "=" qvalue ] )
    980982</pre><p id="rfc.section.6.2.p.3">Character set values are described in <a href="#character.sets" title="Character Sets">Section&nbsp;3.1</a>. Each charset <em class="bcp14">MAY</em> be given an associated quality value which represents the user's preference for that charset. The default value is q=1. An
    981983         example is
    982984      </p>
    983       <div id="rfc.figure.u.22"></div><pre class="text">   Accept-Charset: iso-8859-5, unicode-1-1;q=0.8
     985      <div id="rfc.figure.u.26"></div><pre class="text">   Accept-Charset: iso-8859-5, unicode-1-1;q=0.8
    984986</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
    985987         not mentioned elsewhere in the Accept-Charset field. If no "*" is present in an Accept-Charset field, then all character sets
    … …  
    995997      <p id="rfc.section.6.3.p.1">The Accept-Encoding request-header field is similar to Accept, but restricts the content-codings (<a href="#content.codings" title="Content Codings">Section&nbsp;3.2</a>) that are acceptable in the response.
    996998      </p>
    997       <div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span>  Accept-Encoding  = "Accept-Encoding" ":"
     999      <div id="rfc.figure.u.27"></div><pre class="inline"><span id="rfc.iref.g.22"></span><span id="rfc.iref.g.23"></span>  Accept-Encoding  = "Accept-Encoding" ":"
    9981000                     #( codings [ ";" "q" "=" qvalue ] )
    9991001  codings          = ( content-coding | "*" )
    10001002</pre><p id="rfc.section.6.3.p.3">Examples of its use are:</p>
    1001       <div id="rfc.figure.u.24"></div><pre class="text">    Accept-Encoding: compress, gzip
     1003      <div id="rfc.figure.u.28"></div><pre class="text">    Accept-Encoding: compress, gzip
    10021004    Accept-Encoding:
    10031005    Accept-Encoding: *
    … …  
    10411043         as a response to the request. Language tags are defined in <a href="#language.tags" title="Language Tags">Section&nbsp;3.5</a>.
    10421044      </p>
    1043       <div id="rfc.figure.u.25"></div><pre class="inline"><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span>  Accept-Language = "Accept-Language" ":"
     1045      <div id="rfc.figure.u.29"></div><pre class="inline"><span id="rfc.iref.g.24"></span><span id="rfc.iref.g.25"></span>  Accept-Language = "Accept-Language" ":"
    10441046                    1#( language-range [ ";" "q" "=" qvalue ] )
    10451047  language-range  = ( ( 1*8ALPHA *( "-" 1*8ALPHA ) ) | "*" )
    … …  
    10471049         that range. The quality value defaults to "q=1". For example,
    10481050      </p>
    1049       <div id="rfc.figure.u.26"></div><pre class="text">    Accept-Language: da, en-gb;q=0.8, en;q=0.7
     1051      <div id="rfc.figure.u.30"></div><pre class="text">    Accept-Language: da, en-gb;q=0.8, en;q=0.7
    10501052</pre><p id="rfc.section.6.4.p.5">would mean: "I prefer Danish, but will accept British English and other types of English." A language-range matches a language-tag
    10511053         if it exactly equals the tag, or if it exactly equals a prefix of the tag such that the first tag character following the
    … …  
    10851087         without losing the identity of its underlying media type.
    10861088      </p>
    1087       <div id="rfc.figure.u.27"></div><pre class="inline"><span id="rfc.iref.g.26"></span>  Content-Encoding  = "Content-Encoding" ":" 1#content-coding
     1089      <div id="rfc.figure.u.31"></div><pre class="inline"><span id="rfc.iref.g.26"></span>  Content-Encoding  = "Content-Encoding" ":" 1#content-coding
    10881090</pre><p id="rfc.section.6.5.p.3">Content codings are defined in <a href="#content.codings" title="Content Codings">Section&nbsp;3.2</a>. An example of its use is
    10891091      </p>
    1090       <div id="rfc.figure.u.28"></div><pre class="text">    Content-Encoding: gzip
     1092      <div id="rfc.figure.u.32"></div><pre class="text">    Content-Encoding: gzip
    10911093</pre><p id="rfc.section.6.5.p.5">The content-coding is a characteristic of the entity identified by the Request-URI. Typically, the entity-body is stored with
    10921094         this encoding and is only decoded before rendering or analogous usage. However, a non-transparent 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
    … …  
    11051107         Note that this might not be equivalent to all the languages used within the entity-body.
    11061108      </p>
    1107       <div id="rfc.figure.u.29"></div><pre class="inline"><span id="rfc.iref.g.27"></span>  Content-Language  = "Content-Language" ":" 1#language-tag
     1109      <div id="rfc.figure.u.33"></div><pre class="inline"><span id="rfc.iref.g.27"></span>  Content-Language  = "Content-Language" ":" 1#language-tag
    11081110</pre><p id="rfc.section.6.6.p.3">Language tags are defined in <a href="#language.tags" title="Language Tags">Section&nbsp;3.5</a>. The primary purpose of Content-Language is to allow a user to identify and differentiate entities according to the user's
    11091111         own preferred language. Thus, if the body content is intended only for a Danish-literate audience, the appropriate field is
    11101112      </p>
    1111       <div id="rfc.figure.u.30"></div><pre class="text">    Content-Language: da
     1113      <div id="rfc.figure.u.34"></div><pre class="text">    Content-Language: da
    11121114</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
    11131115         that the sender does not consider it to be specific to any natural language, or that the sender does not know for which language
    … …  
    11171119         simultaneously in the original Maori and English versions, would call for
    11181120      </p>
    1119       <div id="rfc.figure.u.31"></div><pre class="text">    Content-Language: mi, en
     1121      <div id="rfc.figure.u.35"></div><pre class="text">    Content-Language: mi, en
    11201122</pre><p id="rfc.section.6.6.p.8">However, just because multiple languages are present within an entity does not mean that it is intended for multiple linguistic
    11211123         audiences. An example would be a beginner's language primer, such as "A First Lesson in Latin," which is clearly intended
    … …  
    11321134         accessed, the server <em class="bcp14">SHOULD</em> provide a Content-Location for the particular variant which is returned.
    11331135      </p>
    1134       <div id="rfc.figure.u.32"></div><pre class="inline"><span id="rfc.iref.g.28"></span>  Content-Location = "Content-Location" ":"
     1136      <div id="rfc.figure.u.36"></div><pre class="inline"><span id="rfc.iref.g.28"></span>  Content-Location = "Content-Location" ":"
    11351137                    ( absoluteURI | relativeURI )
    11361138</pre><p id="rfc.section.6.7.p.3">The value of Content-Location also defines the base URI for the entity.</p>
    … …  
    11511153         attacks.)
    11521154      </p>
    1153       <div id="rfc.figure.u.33"></div><pre class="inline"><span id="rfc.iref.g.29"></span><span id="rfc.iref.g.30"></span>  Content-MD5   = "Content-MD5" ":" md5-digest
     1155      <div id="rfc.figure.u.37"></div><pre class="inline"><span id="rfc.iref.g.29"></span><span id="rfc.iref.g.30"></span>  Content-MD5   = "Content-MD5" ":" md5-digest
    11541156  md5-digest    = &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;
    11551157</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 entity-body. Only origin servers or clients <em class="bcp14">MAY</em> generate the Content-MD5 header field; proxies and gateways <em class="bcp14">MUST NOT</em> generate it, as this would defeat its value as an end-to-end integrity check. Any recipient of the entity-body, including
    … …  
    11881190         the HEAD method, the media type that would have been sent had the request been a GET.
    11891191      </p>
    1190       <div id="rfc.figure.u.34"></div><pre class="inline"><span id="rfc.iref.g.31"></span>  Content-Type   = "Content-Type" ":" media-type
     1192      <div id="rfc.figure.u.38"></div><pre class="inline"><span id="rfc.iref.g.31"></span>  Content-Type   = "Content-Type" ":" media-type
    11911193</pre><p id="rfc.section.6.9.p.3">Media types are defined in <a href="#media.types" title="Media Types">Section&nbsp;3.3</a>. An example of the field is
    11921194      </p>
    1193       <div id="rfc.figure.u.35"></div><pre class="text">    Content-Type: text/html; charset=ISO-8859-4
     1195      <div id="rfc.figure.u.39"></div><pre class="text">    Content-Type: text/html; charset=ISO-8859-4
    11941196</pre><p id="rfc.section.6.9.p.5">Further discussion of methods for identifying the media type of an entity is provided in <a href="#type" title="Type">Section&nbsp;4.2.1</a>.
    11951197      </p>
    … …  
    14071409         environments.
    14081410      </p>
    1409       <div id="rfc.figure.u.36"></div><pre class="inline"><span id="rfc.iref.g.32"></span>  MIME-Version   = "MIME-Version" ":" 1*DIGIT "." 1*DIGIT
     1411      <div id="rfc.figure.u.40"></div><pre class="inline"><span id="rfc.iref.g.32"></span>  MIME-Version   = "MIME-Version" ":" 1*DIGIT "." 1*DIGIT
    14101412</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
    14111413         document and not the MIME specification.
    … …  
    14611463         in <a href="#RFC1806" id="rfc.xref.RFC1806.3"><cite title="Communicating Presentation Information in Internet Messages: The Content-Disposition Header">[RFC1806]</cite></a>.
    14621464      </p>
    1463       <div id="rfc.figure.u.37"></div><pre class="inline"><span id="rfc.iref.g.33"></span><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>  content-disposition = "Content-Disposition" ":"
     1465      <div id="rfc.figure.u.41"></div><pre class="inline"><span id="rfc.iref.g.33"></span><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>  content-disposition = "Content-Disposition" ":"
    14641466                        disposition-type *( ";" disposition-parm )
    14651467  disposition-type = "attachment" | disp-extension-token
    … …  
    14691471  disp-extension-parm = token "=" ( token | quoted-string )
    14701472</pre><p id="rfc.section.B.1.p.3">An example is</p>
    1471       <div id="rfc.figure.u.38"></div><pre class="text">     Content-Disposition: attachment; filename="fname.ext"
     1473      <div id="rfc.figure.u.42"></div><pre class="text">     Content-Disposition: attachment; filename="fname.ext"
    14721474</pre><p id="rfc.section.B.1.p.5">The receiving user agent <em class="bcp14">SHOULD NOT</em> respect any directory path information present in the filename-parm parameter, which is the only parameter believed to apply
    14731475         to HTTP implementations at this time. The filename <em class="bcp14">SHOULD</em> be treated as a terminal component only.
    … …  
    16791681                        <li class="indline1"><em>Section 2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">2</a></li>
    16801682                        <li class="indline1"><em>Section 2.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.2">2</a>, <a class="iref" href="#rfc.xref.Part1.3">2</a>, <a class="iref" href="#rfc.xref.Part1.4">2</a>, <a class="iref" href="#rfc.xref.Part1.5">2</a>, <a class="iref" href="#rfc.xref.Part1.6">2</a>, <a class="iref" href="#rfc.xref.Part1.7">2</a></li>
    1681                         <li class="indline1"><em>Section 3.2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.8">2</a>, <a class="iref" href="#rfc.xref.Part1.11">2</a></li>
    1682                         <li class="indline1"><em>Section 4.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.10">2</a></li>
     1683                        <li class="indline1"><em>Section 3.2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.8">2</a>, <a class="iref" href="#rfc.xref.Part1.10">2</a></li>
     1684                        <li class="indline1"><em>Section 4.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.11">2</a></li>
    16831685                        <li class="indline1"><em>Section 4.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.13">4.2</a></li>
    16841686                        <li class="indline1"><em>Section 4.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.14">4.2.2</a></li>

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

    r206 r207  
    271271  token          = &lt;token, defined in &basic-rules;&gt;
    272272</artwork></figure>
    273 <t>
     273<t anchor="abnf.dependencies">
    274274  The ABNF rules below are defined in other parts:
    275275</t>
    276 <figure><artwork type="abnf2616">
     276<figure><!--Part1--><artwork type="abnf2616">
    277277  absoluteURI    = &lt;absoluteURI, defined in &general-syntax;&gt;
     278  Content-Length = &lt;Content-Length, defined in &header-content-length;&gt;
     279  relativeURI    = &lt;relativeURI, defined in &general-syntax;&gt;
     280  message-header = &lt;message-header, defined in &message-headers;&gt;
     281</artwork></figure>
     282<figure><!--Part2--><artwork type="abnf2616">
    278283  Allow          = &lt;Allow, defined in &header-allow;&gt;
    279   Content-Length = &lt;Content-Length, defined in &header-content-length;&gt;
     284</artwork></figure>
     285<figure><!--Part4--><artwork type="abnf2616">
     286  Last-Modified  = &lt;Last-Modified, defined in &header-last-modified;&gt;
     287</artwork></figure>
     288<figure><!--Part5--><artwork type="abnf2616">
    280289  Content-Range  = &lt;Content-Range, defined in &header-content-range;&gt;
     290</artwork></figure>
     291<figure><!--Part6--><artwork type="abnf2616">
    281292  Expires        = &lt;Expires, defined in &header-expires;&gt;
    282   Last-Modified  = &lt;Last-Modified, defined in &header-last-modified;&gt;
    283   message-header = &lt;message-header, defined in &message-headers;&gt;
    284   relativeURI    = &lt;relativeURI, defined in &general-syntax;&gt;
    285293</artwork></figure>
    286294</section>

  • draft-ietf-httpbis/latest/p4-conditional.html

    r205 r207  
    547547      </p>
    548548      <div id="rfc.figure.u.1"></div><pre class="inline">  quoted-string = &lt;quoted-string, defined in <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>&gt;
    549 </pre><p id="rfc.section.2.p.3">The ABNF rules below are defined in other parts:</p>
     549</pre><div id="abnf.dependencies">
     550         <p id="rfc.section.2.p.3">The ABNF rules below are defined in other parts:</p>
     551      </div>
    550552      <div id="rfc.figure.u.2"></div><pre class="inline">  HTTP-date     = &lt;HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#full.date" title="Full Date">Section 3.3.1</a>&gt;
    551553</pre><h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="entity.tags" href="#entity.tags">Entity Tags</a></h1>

  • draft-ietf-httpbis/latest/p4-conditional.xml

    r205 r207  
    263263  quoted-string = &lt;quoted-string, defined in &basic-rules;&gt;
    264264</artwork></figure>
    265 <t>
     265<t anchor="abnf.dependencies">
    266266  The ABNF rules below are defined in other parts:
    267267</t>
    268 <figure><artwork type="abnf2616">
     268<figure><!--Part1--><artwork type="abnf2616">
    269269  HTTP-date     = &lt;HTTP-date, defined in &full-date;&gt;
    270270</artwork></figure>

  • draft-ietf-httpbis/latest/p5-range.html

    r205 r207  
    553553  SP         = &lt;SP, defined in <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>&gt;
    554554</pre><div id="rfc.figure.u.2"></div><pre class="inline">  token      = &lt;token, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>&gt;
    555 </pre><p id="rfc.section.2.p.4">The ABNF rules below are defined in other parts:</p>
     555</pre><div id="abnf.dependencies">
     556         <p id="rfc.section.2.p.4">The ABNF rules below are defined in other parts:</p>
     557      </div>
    556558      <div id="rfc.figure.u.3"></div><pre class="inline">  HTTP-date  = &lt;HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#full.date" title="Full Date">Section 3.3.1</a>&gt;
    557559</pre><div id="rfc.figure.u.4"></div><pre class="inline">  entity-tag = &lt;entity-tag, defined in <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#entity.tags" title="Entity Tags">Section 3</a>&gt;

  • draft-ietf-httpbis/latest/p5-range.xml

    r205 r207  
    268268  token      = &lt;token, defined in &basic-rules;&gt;
    269269</artwork></figure>
    270 <t>
     270<t anchor="abnf.dependencies">
    271271  The ABNF rules below are defined in other parts:
    272272</t>
    273 <figure><artwork type="abnf2616">
     273<figure><!--Part1--><artwork type="abnf2616">
    274274  HTTP-date  = &lt;HTTP-date, defined in &full-date;&gt;
    275275</artwork></figure>
    276 <figure><artwork type="abnf2616">
     276<figure><!--Part4--><artwork type="abnf2616">
    277277  entity-tag = &lt;entity-tag, defined in &entity-tags;&gt;
    278278</artwork></figure>

  • draft-ietf-httpbis/latest/p6-cache.html

    r205 r207  
    685685</pre><div id="rfc.figure.u.2"></div><pre class="inline">  quoted-string = &lt;quoted-string, defined in <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>&gt;
    686686  token         = &lt;token, defined in <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>&gt;
    687 </pre><p id="rfc.section.2.p.4">The ABNF rules below are defined in other parts:</p>
     687</pre><div id="abnf.dependencies">
     688         <p id="rfc.section.2.p.4">The ABNF rules below are defined in other parts:</p>
     689      </div>
    688690      <div id="rfc.figure.u.3"></div><pre class="inline">  field-name    = &lt;field-name, defined in <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#message.headers" title="Message Headers">Section 4.2</a>&gt;
    689691  HTTP-date     = &lt;HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#full.date" title="Full Date">Section 3.3.1</a>&gt;

  • draft-ietf-httpbis/latest/p6-cache.xml

    r205 r207  
    444444  token         = &lt;token, defined in &basic-rules;&gt;
    445445</artwork></figure>
    446 <t>
     446<t anchor="abnf.dependencies">
    447447  The ABNF rules below are defined in other parts:
    448448</t>
    449 <figure><artwork type="abnf2616">
     449<figure><!--Part1--><artwork type="abnf2616">
    450450  field-name    = &lt;field-name, defined in &message-headers;&gt;
    451451  HTTP-date     = &lt;HTTP-date, defined in &full-date;&gt;

  • draft-ietf-httpbis/latest/p7-auth.html

    r205 r207  
    537537      <p id="rfc.section.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation.abnf" title="Augmented BNF">Section 2.1</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. <span class="comment">[abnf.dep: ABNF syntax and basic rules will be adopted from RFC 5234, see &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;.]</span>
    538538      </p>
    539       <p id="rfc.section.2.p.2">The ABNF rules below are defined in other specifications:</p>
     539      <div id="abnf.dependencies">
     540         <p id="rfc.section.2.p.2">The ABNF rules below are defined in other specifications:</p>
     541      </div>
    540542      <div id="rfc.figure.u.1"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span>  challenge   = &lt;challenge, defined in <a href="#RFC2617" id="rfc.xref.RFC2617.3"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>, <a href="http://tools.ietf.org/html/rfc2617#section-1.2">Section 1.2</a>&gt;
    541543  credentials = &lt;credentials, defined in <a href="#RFC2617" id="rfc.xref.RFC2617.4"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>, <a href="http://tools.ietf.org/html/rfc2617#section-1.2">Section 1.2</a>&gt;

  • draft-ietf-httpbis/latest/p7-auth.xml

    r205 r207  
    249249  <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/36"/>.</cref>
    250250</t>
    251 <t>
     251<t anchor="abnf.dependencies">
    252252  The ABNF rules below are defined in other specifications:
    253253</t>
Note: See TracChangeset for help on using the changeset viewer.