Ticket #163: 163.diff

File 163.diff, 115.9 KB (added by julian.reschke@…, 11 years ago)

proposed change for part 1

  • p1-messaging.xml

     
    838838<section title="Date/Time Formats" anchor="date.time.formats">
    839839<section title="Full Date" anchor="full.date">
    840840  <x:anchor-alias value="HTTP-date"/>
    841   <x:anchor-alias value="obsolete-date"/>
    842   <x:anchor-alias value="rfc1123-date"/>
    843   <x:anchor-alias value="rfc850-date"/>
    844   <x:anchor-alias value="asctime-date"/>
    845   <x:anchor-alias value="date1"/>
    846   <x:anchor-alias value="date2"/>
    847   <x:anchor-alias value="date3"/>
    848   <x:anchor-alias value="rfc1123-date"/>
    849   <x:anchor-alias value="time"/>
    850   <x:anchor-alias value="wkday"/>
    851   <x:anchor-alias value="weekday"/>
    852   <x:anchor-alias value="month"/>
    853841<t>
    854842   HTTP applications have historically allowed three different formats
    855843   for the representation of date/time stamps:
     
    869857   only generate the RFC 1123 format for representing HTTP-date values
    870858   in header fields. See <xref target="tolerant.applications"/> for further information.
    871859</t>
    872 <x:note>
    873   <t>
    874     <x:h>Note:</x:h> Recipients of date values are encouraged to be robust in
    875     accepting date values that may have been sent by non-HTTP
    876     applications, as is sometimes the case when retrieving or posting
    877     messages via proxies/gateways to SMTP or NNTP.
    878   </t>
    879 </x:note>
    880860<t>
    881861   All HTTP date/time stamps &MUST; be represented in Greenwich Mean Time
    882862   (GMT), without exception. For the purposes of HTTP, GMT is exactly
     
    887867   additional whitespace beyond that specifically included as SP in the
    888868   grammar.
    889869</t>
    890 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="HTTP-date"/><iref primary="true" item="Grammar" subitem="rfc1123-date"/><iref primary="true" item="Grammar" subitem="obsolete-date"/><iref primary="true" item="Grammar" subitem="rfc850-date"/><iref primary="true" item="Grammar" subitem="asctime-date"/><iref primary="true" item="Grammar" subitem="date1"/><iref primary="true" item="Grammar" subitem="date2"/><iref primary="true" item="Grammar" subitem="date3"/><iref primary="true" item="Grammar" subitem="time"/><iref primary="true" item="Grammar" subitem="wkday"/><iref primary="true" item="Grammar" subitem="weekday"/><iref primary="true" item="Grammar" subitem="month"/>
    891   <x:ref>HTTP-date</x:ref>    = <x:ref>rfc1123-date</x:ref> / <x:ref>obsolete-date</x:ref>
    892   <x:ref>obsolete-date</x:ref> = <x:ref>rfc850-date</x:ref> / <x:ref>asctime-date</x:ref>
    893   <x:ref>rfc1123-date</x:ref> = <x:ref>wkday</x:ref> "," <x:ref>SP</x:ref> date1 <x:ref>SP</x:ref> time <x:ref>SP</x:ref> GMT
    894   <x:ref>rfc850-date</x:ref>  = <x:ref>weekday</x:ref> "," <x:ref>SP</x:ref> date2 <x:ref>SP</x:ref> time <x:ref>SP</x:ref> GMT
    895   <x:ref>asctime-date</x:ref> = <x:ref>wkday</x:ref> <x:ref>SP</x:ref> <x:ref>date3</x:ref> <x:ref>SP</x:ref> <x:ref>time</x:ref> <x:ref>SP</x:ref> 4<x:ref>DIGIT</x:ref>
    896   <x:ref>date1</x:ref>        = 2<x:ref>DIGIT</x:ref> <x:ref>SP</x:ref> <x:ref>month</x:ref> <x:ref>SP</x:ref> 4<x:ref>DIGIT</x:ref>
    897                  ; day month year (e.g., 02 Jun 1982)
    898   <x:ref>date2</x:ref>        = 2<x:ref>DIGIT</x:ref> "-" <x:ref>month</x:ref> "-" 2<x:ref>DIGIT</x:ref>
    899                  ; day-month-year (e.g., 02-Jun-82)
    900   <x:ref>date3</x:ref>        = <x:ref>month</x:ref> <x:ref>SP</x:ref> ( 2<x:ref>DIGIT</x:ref> / ( <x:ref>SP</x:ref> 1<x:ref>DIGIT</x:ref> ))
    901                  ; month day (e.g., Jun  2)
    902   <x:ref>time</x:ref>         = 2<x:ref>DIGIT</x:ref> ":" 2<x:ref>DIGIT</x:ref> ":" 2<x:ref>DIGIT</x:ref>
    903                  ; 00:00:00 - 23:59:59
    904   <x:ref>wkday</x:ref>        = s-Mon / s-Tue / s-Wed
     870<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="HTTP-date"/>
     871  <x:ref>HTTP-date</x:ref>    = <x:ref>rfc1123-date</x:ref> / <x:ref>obs-date</x:ref>
     872</artwork></figure>
     873<t anchor="preferred.date.format">
     874  <x:anchor-alias value="rfc1123-date"/>
     875  <x:anchor-alias value="time-of-day"/>
     876  <x:anchor-alias value="hour"/>
     877  <x:anchor-alias value="minute"/>
     878  <x:anchor-alias value="second"/>
     879  <x:anchor-alias value="day-name"/>
     880  <x:anchor-alias value="day"/>
     881  <x:anchor-alias value="month"/>
     882  <x:anchor-alias value="year"/>
     883  <x:anchor-alias value="GMT"/>
     884  Preferred format:
     885</t>
     886<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="rfc1123-date"/><iref primary="true" item="Grammar" subitem="date1"/><iref primary="true" item="Grammar" subitem="time-of-day"/><iref primary="true" item="Grammar" subitem="hour"/><iref primary="true" item="Grammar" subitem="minute"/><iref primary="true" item="Grammar" subitem="second"/><iref primary="true" item="Grammar" subitem="day-name"/><iref primary="true" item="Grammar" subitem="day-name-l"/><iref primary="true" item="Grammar" subitem="day"/><iref primary="true" item="Grammar" subitem="month"/><iref primary="true" item="Grammar" subitem="year"/><iref primary="true" item="Grammar" subitem="GMT"/>
     887  <x:ref>rfc1123-date</x:ref> = <x:ref>day-name</x:ref> "," <x:ref>SP</x:ref> date1 <x:ref>SP</x:ref> <x:ref>time-of-day</x:ref> <x:ref>SP</x:ref> <x:ref>GMT</x:ref>
     888
     889  <x:ref>day-name</x:ref>     = s-Mon / s-Tue / s-Wed
    905890               / s-Thu / s-Fri / s-Sat / s-Sun
    906   <x:ref>weekday</x:ref>      = l-Mon / l-Tue / l-Wed
    907                / l-Thu / l-Fri / l-Sat / l-Sun
    908   <x:ref>month</x:ref>        = s-Jan / s-Feb / s-Mar / s-Apr
    909                / s-May / s-Jun / s-Jul / s-Aug
    910                / s-Sep / s-Oct / s-Nov / s-Dec
    911891               
    912   GMT   = <x:abnf-char-sequence>"GMT"</x:abnf-char-sequence> ; "GMT", case-sensitive
    913 
    914892  s-Mon = <x:abnf-char-sequence>"Mon"</x:abnf-char-sequence> ; "Mon", case-sensitive
    915893  s-Tue = <x:abnf-char-sequence>"Tue"</x:abnf-char-sequence> ; "Tue", case-sensitive
    916894  s-Wed = <x:abnf-char-sequence>"Wed"</x:abnf-char-sequence> ; "Wed", case-sensitive
     
    919897  s-Sat = <x:abnf-char-sequence>"Sat"</x:abnf-char-sequence> ; "Sat", case-sensitive
    920898  s-Sun = <x:abnf-char-sequence>"Sun"</x:abnf-char-sequence> ; "Sun", case-sensitive
    921899
    922   l-Mon = <x:abnf-char-sequence>"Monday"</x:abnf-char-sequence>          ; "Monday", case-sensitive
    923   l-Tue = <x:abnf-char-sequence>"Tuesday"</x:abnf-char-sequence>       ; "Tuesday", case-sensitive
    924   l-Wed = <x:abnf-char-sequence>"Wednesday"</x:abnf-char-sequence> ; "Wednesday", case-sensitive
    925   l-Thu = <x:abnf-char-sequence>"Thursday"</x:abnf-char-sequence>    ; "Thursday", case-sensitive
    926   l-Fri = <x:abnf-char-sequence>"Friday"</x:abnf-char-sequence>          ; "Friday", case-sensitive
    927   l-Sat = <x:abnf-char-sequence>"Saturday"</x:abnf-char-sequence>    ; "Saturday", case-sensitive
    928   l-Sun = <x:abnf-char-sequence>"Sunday"</x:abnf-char-sequence>          ; "Sunday", case-sensitive
     900  <x:ref>date1</x:ref>        = <x:ref>day</x:ref> <x:ref>SP</x:ref> <x:ref>month</x:ref> <x:ref>SP</x:ref> <x:ref>year</x:ref>
     901               ; e.g., 02 Jun 1982
    929902
     903  <x:ref>day</x:ref>          = 2<x:ref>DIGIT</x:ref>
     904  <x:ref>month</x:ref>        = s-Jan / s-Feb / s-Mar / s-Apr
     905               / s-May / s-Jun / s-Jul / s-Aug
     906               / s-Sep / s-Oct / s-Nov / s-Dec
     907  <x:ref>year</x:ref>         = 4<x:ref>DIGIT</x:ref>
     908
    930909  s-Jan = <x:abnf-char-sequence>"Jan"</x:abnf-char-sequence> ; "Jan", case-sensitive
    931910  s-Feb = <x:abnf-char-sequence>"Feb"</x:abnf-char-sequence> ; "Feb", case-sensitive
    932911  s-Mar = <x:abnf-char-sequence>"Mar"</x:abnf-char-sequence> ; "Mar", case-sensitive
     
    939918  s-Oct = <x:abnf-char-sequence>"Oct"</x:abnf-char-sequence> ; "Oct", case-sensitive
    940919  s-Nov = <x:abnf-char-sequence>"Nov"</x:abnf-char-sequence> ; "Nov", case-sensitive
    941920  s-Dec = <x:abnf-char-sequence>"Dec"</x:abnf-char-sequence> ; "Dec", case-sensitive
     921
     922  <x:ref>GMT</x:ref>   = <x:abnf-char-sequence>"GMT"</x:abnf-char-sequence> ; "GMT", case-sensitive
     923
     924  <x:ref>time-of-day</x:ref>  = <x:ref>hour</x:ref> ":" <x:ref>minute</x:ref> ":" <x:ref>second</x:ref>
     925                 ; 00:00:00 - 23:59:59
     926                 
     927  <x:ref>hour</x:ref>         = 2<x:ref>DIGIT</x:ref>               
     928  <x:ref>minute</x:ref>       = 2<x:ref>DIGIT</x:ref>               
     929  <x:ref>second</x:ref>       = 2<x:ref>DIGIT</x:ref>               
    942930</artwork></figure>
    943931<t>
    944       <x:h>Note:</x:h> HTTP requirements for the date/time stamp format apply only
    945       to their usage within the protocol stream. Clients and servers are
    946       not required to use these formats for user presentation, request
    947       logging, etc.
     932  The semantics of <x:ref>day-name</x:ref>, <x:ref>day</x:ref>,
     933  <x:ref>month</x:ref>, <x:ref>year</x:ref>, and <x:ref>time-of-day</x:ref> are the
     934  same as those defined in the RFC 5322 constructs
     935  with the corresponding name (<xref target="RFC5322" x:fmt="," x:sec="3.3"/>).
    948936</t>
     937<t anchor="obsolete.date.formats">
     938  <x:anchor-alias value="obs-date"/>
     939  <x:anchor-alias value="rfc850-date"/>
     940  <x:anchor-alias value="asctime-date"/>
     941  <x:anchor-alias value="date1"/>
     942  <x:anchor-alias value="date2"/>
     943  <x:anchor-alias value="date3"/>
     944  <x:anchor-alias value="rfc1123-date"/>
     945  <x:anchor-alias value="day-name-l"/>
     946  Obsolete formats:
     947</t>
     948<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="obs-date"/>
     949  <x:ref>obs-date</x:ref>     = <x:ref>rfc850-date</x:ref> / <x:ref>asctime-date</x:ref>
     950</artwork></figure>
     951<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="rfc850-date"/>
     952  <x:ref>rfc850-date</x:ref>  = <x:ref>day-name-l</x:ref> "," <x:ref>SP</x:ref> <x:ref>date2</x:ref> <x:ref>SP</x:ref> <x:ref>time-of-day</x:ref> <x:ref>SP</x:ref> <x:ref>GMT</x:ref>
     953  <x:ref>date2</x:ref>        = <x:ref>day</x:ref> "-" <x:ref>month</x:ref> "-" 2<x:ref>DIGIT</x:ref>
     954                 ; day-month-year (e.g., 02-Jun-82)
     955
     956  <x:ref>day-name-l</x:ref>   = l-Mon / l-Tue / l-Wed
     957               / l-Thu / l-Fri / l-Sat / l-Sun
     958
     959  l-Mon = <x:abnf-char-sequence>"Monday"</x:abnf-char-sequence>          ; "Monday", case-sensitive
     960  l-Tue = <x:abnf-char-sequence>"Tuesday"</x:abnf-char-sequence>       ; "Tuesday", case-sensitive
     961  l-Wed = <x:abnf-char-sequence>"Wednesday"</x:abnf-char-sequence> ; "Wednesday", case-sensitive
     962  l-Thu = <x:abnf-char-sequence>"Thursday"</x:abnf-char-sequence>    ; "Thursday", case-sensitive
     963  l-Fri = <x:abnf-char-sequence>"Friday"</x:abnf-char-sequence>          ; "Friday", case-sensitive
     964  l-Sat = <x:abnf-char-sequence>"Saturday"</x:abnf-char-sequence>    ; "Saturday", case-sensitive
     965  l-Sun = <x:abnf-char-sequence>"Sunday"</x:abnf-char-sequence>          ; "Sunday", case-sensitive
     966</artwork></figure>
     967<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="asctime-date"/>
     968  <x:ref>asctime-date</x:ref> = <x:ref>day-name</x:ref> <x:ref>SP</x:ref> <x:ref>date3</x:ref> <x:ref>SP</x:ref> <x:ref>time-of-day</x:ref> <x:ref>SP</x:ref> <x:ref>year</x:ref>
     969  <x:ref>date3</x:ref>        = <x:ref>month</x:ref> <x:ref>SP</x:ref> ( 2<x:ref>DIGIT</x:ref> / ( <x:ref>SP</x:ref> 1<x:ref>DIGIT</x:ref> ))
     970                 ; month day (e.g., Jun  2)
     971</artwork></figure>
     972<x:note>
     973  <t>
     974    <x:h>Note:</x:h> Recipients of date values are encouraged to be robust in
     975    accepting date values that may have been sent by non-HTTP
     976    applications, as is sometimes the case when retrieving or posting
     977    messages via proxies/gateways to SMTP or NNTP.
     978  </t>
     979</x:note>
     980<x:note>
     981  <t>
     982    <x:h>Note:</x:h> HTTP requirements for the date/time stamp format apply only
     983    to their usage within the protocol stream. Clients and servers are
     984    not required to use these formats for user presentation, request
     985    logging, etc.
     986  </t>
     987</x:note>
    949988</section>
    950989</section>
    951990
     
    9701009  <x:anchor-alias value="value"/>
    9711010   Parameters are in  the form of attribute/value pairs.
    9721011</t>
    973 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="parameter"/><iref primary="true" item="Grammar" subitem="attribute"/><iref primary="true" item="Grammar" subitem="value"/>
     1012<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="parameter"/><iref primary="true" item="Grammar" subitem="attribute"/><iref primary="true" item="Grammar" subitem="value"/><iref primary="true" item="Grammar" subitem="date2"/><iref primary="true" item="Grammar" subitem="date3"/>
    9741013  <x:ref>parameter</x:ref>               = <x:ref>attribute</x:ref> <x:ref>BWS</x:ref> "=" <x:ref>BWS</x:ref> <x:ref>value</x:ref>
    9751014  <x:ref>attribute</x:ref>               = <x:ref>token</x:ref>
    9761015  <x:ref>value</x:ref>                   = <x:ref>token</x:ref> / <x:ref>quoted-string</x:ref>
     
    43614400<x:ref>Date</x:ref> = "Date:" OWS Date-v
    43624401<x:ref>Date-v</x:ref> = HTTP-date
    43634402
    4364 GMT = %x47.4D.54
     4403<x:ref>GMT</x:ref> = %x47.4D.54
    43654404
    43664405<x:ref>HTTP-Prot-Name</x:ref> = %x48.54.54.50
    43674406<x:ref>HTTP-Version</x:ref> = HTTP-Prot-Name "/" 1*DIGIT "." 1*DIGIT
    4368 <x:ref>HTTP-date</x:ref> = rfc1123-date / obsolete-date
     4407<x:ref>HTTP-date</x:ref> = rfc1123-date / obs-date
    43694408<x:ref>HTTP-message</x:ref> = Request / Response
    43704409<x:ref>Host</x:ref> = "Host:" OWS Host-v
    43714410<x:ref>Host-v</x:ref> = uri-host [ ":" port ]
     
    44084447<x:ref>Warning</x:ref> = &lt;Warning, defined in [Part6], Section 3.6&gt;
    44094448
    44104449<x:ref>absolute-URI</x:ref> = &lt;absolute-URI, defined in [RFC3986], Section 4.3&gt;
    4411 <x:ref>asctime-date</x:ref> = wkday SP date3 SP time SP 4DIGIT
     4450<x:ref>asctime-date</x:ref> = day-name SP date3 SP time-of-day SP year
    44124451<x:ref>attribute</x:ref> = token
    44134452<x:ref>authority</x:ref> = &lt;authority, defined in [RFC3986], Section 3.2&gt;
    44144453
     
    44224461<x:ref>connection-token</x:ref> = token
    44234462<x:ref>ctext</x:ref> = OWS / %x21-27 / %x2A-5B / %x5D-7E / obs-text
    44244463
    4425 <x:ref>date1</x:ref> = 2DIGIT SP month SP 4DIGIT
    4426 <x:ref>date2</x:ref> = 2DIGIT "-" month "-" 2DIGIT
     4464<x:ref>date1</x:ref> = day SP month SP year
     4465<x:ref>date2</x:ref> = day "-" month "-" 2DIGIT
    44274466<x:ref>date3</x:ref> = month SP ( 2DIGIT / ( SP DIGIT ) )
     4467<x:ref>day</x:ref> = 2DIGIT
     4468<x:ref>day-name</x:ref> = s-Mon / s-Tue / s-Wed / s-Thu / s-Fri / s-Sat / s-Sun
     4469<x:ref>day-name-l</x:ref> = l-Mon / l-Tue / l-Wed / l-Thu / l-Fri / l-Sat / l-Sun
    44284470
    44294471<x:ref>entity-body</x:ref> = &lt;entity-body, defined in [Part3], Section 3.2&gt;
    44304472<x:ref>entity-header</x:ref> = &lt;entity-header, defined in [Part3], Section 3.1&gt;
     
    44394481<x:ref>generic-message</x:ref> = start-line *( message-header CRLF ) CRLF [
    44404482 message-body ]
    44414483
     4484<x:ref>hour</x:ref> = 2DIGIT
    44424485<x:ref>http-URI</x:ref> = "http://" authority path-abempty [ "?" query ]
    44434486
    44444487l-Fri = %x46.72.69.64.61.79
     
    44534496<x:ref>message-body</x:ref> = entity-body /
    44544497 &lt;entity-body encoded as per Transfer-Encoding&gt;
    44554498<x:ref>message-header</x:ref> = field-name ":" OWS [ field-value ] OWS
     4499<x:ref>minute</x:ref> = 2DIGIT
    44564500<x:ref>month</x:ref> = s-Jan / s-Feb / s-Mar / s-Apr / s-May / s-Jun / s-Jul / s-Aug
    44574501 / s-Sep / s-Oct / s-Nov / s-Dec
    44584502
     4503<x:ref>obs-date</x:ref> = rfc850-date / asctime-date
    44594504<x:ref>obs-fold</x:ref> = CRLF
    44604505<x:ref>obs-text</x:ref> = %x80-FF
    4461 <x:ref>obsolete-date</x:ref> = rfc850-date / asctime-date
    44624506
    44634507<x:ref>parameter</x:ref> = attribute BWS "=" BWS value
    44644508<x:ref>partial-URI</x:ref> = relative-part [ "?" query ]
     
    44854529<x:ref>request-target</x:ref> = "*" / absolute-URI / ( path-absolute [ "?" query ] )
    44864530 / authority
    44874531<x:ref>response-header</x:ref> = &lt;response-header, defined in [Part2], Section 5&gt;
    4488 <x:ref>rfc1123-date</x:ref> = wkday "," SP date1 SP time SP GMT
    4489 <x:ref>rfc850-date</x:ref> = weekday "," SP date2 SP time SP GMT
     4532<x:ref>rfc1123-date</x:ref> = day-name "," SP date1 SP time-of-day SP GMT
     4533<x:ref>rfc850-date</x:ref> = day-name-l "," SP date2 SP time-of-day SP GMT
    44904534
    44914535s-Apr = %x41.70.72
    44924536s-Aug = %x41.75.67
     
    45074551s-Thu = %x54.68.75
    45084552s-Tue = %x54.75.65
    45094553s-Wed = %x57.65.64
     4554<x:ref>second</x:ref> = 2DIGIT
    45104555<x:ref>start-line</x:ref> = Request-Line / Status-Line
    45114556
    45124557<x:ref>t-codings</x:ref> = "trailers" / ( transfer-extension [ te-params ] )
     
    45144559 "^" / "_" / "`" / "|" / "~" / DIGIT / ALPHA
    45154560<x:ref>te-ext</x:ref> = OWS ";" OWS token [ "=" ( token / quoted-string ) ]
    45164561<x:ref>te-params</x:ref> = OWS ";" OWS "q=" qvalue *te-ext
    4517 <x:ref>time</x:ref> = 2DIGIT ":" 2DIGIT ":" 2DIGIT
     4562<x:ref>time-of-day</x:ref> = hour ":" minute ":" second
    45184563<x:ref>token</x:ref> = 1*tchar
    45194564<x:ref>trailer-part</x:ref> = *( entity-header CRLF )
    45204565<x:ref>transfer-coding</x:ref> = "chunked" / transfer-extension
     
    45244569
    45254570<x:ref>value</x:ref> = token / quoted-string
    45264571
    4527 <x:ref>weekday</x:ref> = l-Mon / l-Tue / l-Wed / l-Thu / l-Fri / l-Sat / l-Sun
    4528 <x:ref>wkday</x:ref> = s-Mon / s-Tue / s-Wed / s-Thu / s-Fri / s-Sat / s-Sun
     4572<x:ref>year</x:ref> = 4DIGIT
    45294573
    45304574
    45314575</artwork>
  • p1-messaging.html

     
    978978</pre><p id="rfc.section.3.2.1.p.3">The first format is preferred as an Internet standard and represents a fixed-length subset of that defined by <a href="#RFC1123" id="rfc.xref.RFC1123.1"><cite title="Requirements for Internet Hosts - Application and Support">[RFC1123]</cite></a>. The other formats are described here only for compatibility with obsolete implementations. HTTP/1.1 clients and servers
    979979         that parse the date value <em class="bcp14">MUST</em> accept all three formats (for compatibility with HTTP/1.0), though they <em class="bcp14">MUST</em> only generate the RFC 1123 format for representing HTTP-date values in header fields. See <a href="#tolerant.applications" title="Tolerant Applications">Appendix&nbsp;A</a> for further information.
    980980      </p>
    981       <div class="note">
    982          <p> <b>Note:</b> Recipients of date values are encouraged to be robust in accepting date values that may have been sent by non-HTTP applications,
    983             as is sometimes the case when retrieving or posting messages via proxies/gateways to SMTP or NNTP.
    984          </p>
    985       </div>
    986       <p id="rfc.section.3.2.1.p.5">All HTTP date/time stamps <em class="bcp14">MUST</em> be represented in Greenwich Mean Time (GMT), without exception. For the purposes of HTTP, GMT is exactly equal to UTC (Coordinated
     981      <p id="rfc.section.3.2.1.p.4">All HTTP date/time stamps <em class="bcp14">MUST</em> be represented in Greenwich Mean Time (GMT), without exception. For the purposes of HTTP, GMT is exactly equal to UTC (Coordinated
    987982         Universal Time). This is indicated in the first two formats by the inclusion of "GMT" as the three-letter abbreviation for
    988983         time zone, and <em class="bcp14">MUST</em> be assumed when reading the asctime format. HTTP-date is case sensitive and <em class="bcp14">MUST NOT</em> include additional whitespace beyond that specifically included as SP in the grammar.
    989984      </p>
    990       <div id="rfc.figure.u.20"></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><span id="rfc.iref.g.39"></span><span id="rfc.iref.g.40"></span><span id="rfc.iref.g.41"></span><span id="rfc.iref.g.42"></span><span id="rfc.iref.g.43"></span><span id="rfc.iref.g.44"></span>  <a href="#full.date" class="smpl">HTTP-date</a>    = <a href="#full.date" class="smpl">rfc1123-date</a> / <a href="#full.date" class="smpl">obsolete-date</a>
    991   <a href="#full.date" class="smpl">obsolete-date</a> = <a href="#full.date" class="smpl">rfc850-date</a> / <a href="#full.date" class="smpl">asctime-date</a>
    992   <a href="#full.date" class="smpl">rfc1123-date</a> = <a href="#full.date" class="smpl">wkday</a> "," <a href="#core.rules" class="smpl">SP</a> date1 <a href="#core.rules" class="smpl">SP</a> time <a href="#core.rules" class="smpl">SP</a> GMT
    993   <a href="#full.date" class="smpl">rfc850-date</a>  = <a href="#full.date" class="smpl">weekday</a> "," <a href="#core.rules" class="smpl">SP</a> date2 <a href="#core.rules" class="smpl">SP</a> time <a href="#core.rules" class="smpl">SP</a> GMT
    994   <a href="#full.date" class="smpl">asctime-date</a> = <a href="#full.date" class="smpl">wkday</a> <a href="#core.rules" class="smpl">SP</a> <a href="#full.date" class="smpl">date3</a> <a href="#core.rules" class="smpl">SP</a> <a href="#full.date" class="smpl">time</a> <a href="#core.rules" class="smpl">SP</a> 4<a href="#core.rules" class="smpl">DIGIT</a>
    995   <a href="#full.date" class="smpl">date1</a>        = 2<a href="#core.rules" class="smpl">DIGIT</a> <a href="#core.rules" class="smpl">SP</a> <a href="#full.date" class="smpl">month</a> <a href="#core.rules" class="smpl">SP</a> 4<a href="#core.rules" class="smpl">DIGIT</a>
    996                  ; day month year (e.g., 02 Jun 1982)
    997   <a href="#full.date" class="smpl">date2</a>        = 2<a href="#core.rules" class="smpl">DIGIT</a> "-" <a href="#full.date" class="smpl">month</a> "-" 2<a href="#core.rules" class="smpl">DIGIT</a>
    998                  ; day-month-year (e.g., 02-Jun-82)
    999   <a href="#full.date" class="smpl">date3</a>        = <a href="#full.date" class="smpl">month</a> <a href="#core.rules" class="smpl">SP</a> ( 2<a href="#core.rules" class="smpl">DIGIT</a> / ( <a href="#core.rules" class="smpl">SP</a> 1<a href="#core.rules" class="smpl">DIGIT</a> ))
    1000                  ; month day (e.g., Jun  2)
    1001   <a href="#full.date" class="smpl">time</a>         = 2<a href="#core.rules" class="smpl">DIGIT</a> ":" 2<a href="#core.rules" class="smpl">DIGIT</a> ":" 2<a href="#core.rules" class="smpl">DIGIT</a>
    1002                  ; 00:00:00 - 23:59:59
    1003   <a href="#full.date" class="smpl">wkday</a>        = s-Mon / s-Tue / s-Wed
     985      <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.33"></span>  <a href="#full.date" class="smpl">HTTP-date</a>    = <a href="#preferred.date.format" class="smpl">rfc1123-date</a> / <a href="#obsolete.date.formats" class="smpl">obs-date</a>
     986</pre><div id="preferred.date.format">
     987         <p id="rfc.section.3.2.1.p.6">                    Preferred format:</p>
     988      </div>
     989      <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.34"></span><span id="rfc.iref.g.35"></span><span id="rfc.iref.g.36"></span><span id="rfc.iref.g.37"></span><span id="rfc.iref.g.38"></span><span id="rfc.iref.g.39"></span><span id="rfc.iref.g.40"></span><span id="rfc.iref.g.41"></span><span id="rfc.iref.g.42"></span><span id="rfc.iref.g.43"></span><span id="rfc.iref.g.44"></span><span id="rfc.iref.g.45"></span>  <a href="#preferred.date.format" class="smpl">rfc1123-date</a> = <a href="#preferred.date.format" class="smpl">day-name</a> "," <a href="#core.rules" class="smpl">SP</a> date1 <a href="#core.rules" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#core.rules" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">GMT</a>
     990
     991  <a href="#preferred.date.format" class="smpl">day-name</a>     = s-Mon / s-Tue / s-Wed
    1004992               / s-Thu / s-Fri / s-Sat / s-Sun
    1005   <a href="#full.date" class="smpl">weekday</a>      = l-Mon / l-Tue / l-Wed
    1006                / l-Thu / l-Fri / l-Sat / l-Sun
    1007   <a href="#full.date" class="smpl">month</a>        = s-Jan / s-Feb / s-Mar / s-Apr
    1008                / s-May / s-Jun / s-Jul / s-Aug
    1009                / s-Sep / s-Oct / s-Nov / s-Dec
    1010993               
    1011   GMT   = %x47.4D.54 ; "GMT", case-sensitive
    1012 
    1013994  s-Mon = %x4D.6F.6E ; "Mon", case-sensitive
    1014995  s-Tue = %x54.75.65 ; "Tue", case-sensitive
    1015996  s-Wed = %x57.65.64 ; "Wed", case-sensitive
     
    1018999  s-Sat = %x53.61.74 ; "Sat", case-sensitive
    10191000  s-Sun = %x53.75.6E ; "Sun", case-sensitive
    10201001
    1021   l-Mon = %x4D.6F.6E.64.61.79          ; "Monday", case-sensitive
    1022   l-Tue = %x54.75.65.73.64.61.79       ; "Tuesday", case-sensitive
    1023   l-Wed = %x57.65.64.6E.65.73.64.61.79 ; "Wednesday", case-sensitive
    1024   l-Thu = %x54.68.75.72.73.64.61.79    ; "Thursday", case-sensitive
    1025   l-Fri = %x46.72.69.64.61.79          ; "Friday", case-sensitive
    1026   l-Sat = %x53.61.74.75.72.64.61.79    ; "Saturday", case-sensitive
    1027   l-Sun = %x53.75.6E.64.61.79          ; "Sunday", case-sensitive
     1002  <a href="#obsolete.date.formats" class="smpl">date1</a>        = <a href="#preferred.date.format" class="smpl">day</a> <a href="#core.rules" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">month</a> <a href="#core.rules" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">year</a>
     1003               ; e.g., 02 Jun 1982
    10281004
     1005  <a href="#preferred.date.format" class="smpl">day</a>          = 2<a href="#core.rules" class="smpl">DIGIT</a>
     1006  <a href="#preferred.date.format" class="smpl">month</a>        = s-Jan / s-Feb / s-Mar / s-Apr
     1007               / s-May / s-Jun / s-Jul / s-Aug
     1008               / s-Sep / s-Oct / s-Nov / s-Dec
     1009  <a href="#preferred.date.format" class="smpl">year</a>         = 4<a href="#core.rules" class="smpl">DIGIT</a>
     1010
    10291011  s-Jan = %x4A.61.6E ; "Jan", case-sensitive
    10301012  s-Feb = %x46.65.62 ; "Feb", case-sensitive
    10311013  s-Mar = %x4D.61.72 ; "Mar", case-sensitive
     
    10381020  s-Oct = %x4F.63.74 ; "Oct", case-sensitive
    10391021  s-Nov = %x4E.6F.76 ; "Nov", case-sensitive
    10401022  s-Dec = %x44.65.63 ; "Dec", case-sensitive
    1041 </pre><p id="rfc.section.3.2.1.p.7"> <b>Note:</b> HTTP requirements for the date/time stamp format apply only to their usage within the protocol stream. Clients and servers
    1042          are not required to use these formats for user presentation, request logging, etc.
     1023
     1024  <a href="#preferred.date.format" class="smpl">GMT</a>   = %x47.4D.54 ; "GMT", case-sensitive
     1025
     1026  <a href="#preferred.date.format" class="smpl">time-of-day</a>  = <a href="#preferred.date.format" class="smpl">hour</a> ":" <a href="#preferred.date.format" class="smpl">minute</a> ":" <a href="#preferred.date.format" class="smpl">second</a>
     1027                 ; 00:00:00 - 23:59:59
     1028                 
     1029  <a href="#preferred.date.format" class="smpl">hour</a>         = 2<a href="#core.rules" class="smpl">DIGIT</a>               
     1030  <a href="#preferred.date.format" class="smpl">minute</a>       = 2<a href="#core.rules" class="smpl">DIGIT</a>               
     1031  <a href="#preferred.date.format" class="smpl">second</a>       = 2<a href="#core.rules" class="smpl">DIGIT</a>               
     1032</pre><p id="rfc.section.3.2.1.p.8">The semantics of <a href="#preferred.date.format" class="smpl">day-name</a>, <a href="#preferred.date.format" class="smpl">day</a>, <a href="#preferred.date.format" class="smpl">month</a>, <a href="#preferred.date.format" class="smpl">year</a>, and <a href="#preferred.date.format" class="smpl">time-of-day</a> are the same as those defined in the RFC 5322 constructs with the corresponding name (<a href="#RFC5322" id="rfc.xref.RFC5322.2"><cite title="Internet Message Format">[RFC5322]</cite></a>, <a href="http://tools.ietf.org/html/rfc5322#section-3.3">Section 3.3</a>).
    10431033      </p>
     1034      <div id="obsolete.date.formats">
     1035         <p id="rfc.section.3.2.1.p.9">                Obsolete formats:</p>
     1036      </div>
     1037      <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.46"></span>  <a href="#obsolete.date.formats" class="smpl">obs-date</a>     = <a href="#obsolete.date.formats" class="smpl">rfc850-date</a> / <a href="#obsolete.date.formats" class="smpl">asctime-date</a>
     1038</pre><div id="rfc.figure.u.23"></div><pre class="inline"><span id="rfc.iref.g.47"></span>  <a href="#obsolete.date.formats" class="smpl">rfc850-date</a>  = <a href="#obsolete.date.formats" class="smpl">day-name-l</a> "," <a href="#core.rules" class="smpl">SP</a> <a href="#obsolete.date.formats" class="smpl">date2</a> <a href="#core.rules" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#core.rules" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">GMT</a>
     1039  <a href="#obsolete.date.formats" class="smpl">date2</a>        = <a href="#preferred.date.format" class="smpl">day</a> "-" <a href="#preferred.date.format" class="smpl">month</a> "-" 2<a href="#core.rules" class="smpl">DIGIT</a>
     1040                 ; day-month-year (e.g., 02-Jun-82)
     1041
     1042  <a href="#obsolete.date.formats" class="smpl">day-name-l</a>   = l-Mon / l-Tue / l-Wed
     1043               / l-Thu / l-Fri / l-Sat / l-Sun
     1044
     1045  l-Mon = %x4D.6F.6E.64.61.79          ; "Monday", case-sensitive
     1046  l-Tue = %x54.75.65.73.64.61.79       ; "Tuesday", case-sensitive
     1047  l-Wed = %x57.65.64.6E.65.73.64.61.79 ; "Wednesday", case-sensitive
     1048  l-Thu = %x54.68.75.72.73.64.61.79    ; "Thursday", case-sensitive
     1049  l-Fri = %x46.72.69.64.61.79          ; "Friday", case-sensitive
     1050  l-Sat = %x53.61.74.75.72.64.61.79    ; "Saturday", case-sensitive
     1051  l-Sun = %x53.75.6E.64.61.79          ; "Sunday", case-sensitive
     1052</pre><div id="rfc.figure.u.24"></div><pre class="inline"><span id="rfc.iref.g.48"></span>  <a href="#obsolete.date.formats" class="smpl">asctime-date</a> = <a href="#preferred.date.format" class="smpl">day-name</a> <a href="#core.rules" class="smpl">SP</a> <a href="#obsolete.date.formats" class="smpl">date3</a> <a href="#core.rules" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#core.rules" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">year</a>
     1053  <a href="#obsolete.date.formats" class="smpl">date3</a>        = <a href="#preferred.date.format" class="smpl">month</a> <a href="#core.rules" class="smpl">SP</a> ( 2<a href="#core.rules" class="smpl">DIGIT</a> / ( <a href="#core.rules" class="smpl">SP</a> 1<a href="#core.rules" class="smpl">DIGIT</a> ))
     1054                 ; month day (e.g., Jun  2)
     1055</pre><div class="note">
     1056         <p> <b>Note:</b> Recipients of date values are encouraged to be robust in accepting date values that may have been sent by non-HTTP applications,
     1057            as is sometimes the case when retrieving or posting messages via proxies/gateways to SMTP or NNTP.
     1058         </p>
     1059      </div>
     1060      <div class="note">
     1061         <p> <b>Note:</b> HTTP requirements for the date/time stamp format apply only to their usage within the protocol stream. Clients and servers
     1062            are not required to use these formats for user presentation, request logging, etc.
     1063         </p>
     1064      </div>
    10441065      <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;<a id="transfer.codings" href="#transfer.codings">Transfer Codings</a></h2>
    10451066      <p id="rfc.section.3.3.p.1">Transfer-coding values are used to indicate an encoding transformation that has been, can be, or may need to be applied to
    10461067         an entity-body in order to ensure "safe transport" through the network. This differs from a content coding in that the transfer-coding
    10471068         is a property of the message, not of the original entity.
    10481069      </p>
    1049       <div id="rfc.figure.u.21"></div><pre class="inline"><span id="rfc.iref.g.45"></span><span id="rfc.iref.g.46"></span>  <a href="#transfer.codings" class="smpl">transfer-coding</a>         = "chunked" / <a href="#transfer.codings" class="smpl">transfer-extension</a>
     1070      <div id="rfc.figure.u.25"></div><pre class="inline"><span id="rfc.iref.g.49"></span><span id="rfc.iref.g.50"></span>  <a href="#transfer.codings" class="smpl">transfer-coding</a>         = "chunked" / <a href="#transfer.codings" class="smpl">transfer-extension</a>
    10501071  <a href="#transfer.codings" class="smpl">transfer-extension</a>      = <a href="#rule.token.separators" class="smpl">token</a> *( <a href="#rule.whitespace" class="smpl">OWS</a> ";" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#transfer.codings" class="smpl">parameter</a> )
    10511072</pre><div id="rule.parameter">
    10521073         <p id="rfc.section.3.3.p.3">      Parameters are in the form of attribute/value pairs.</p>
    10531074      </div>
    1054       <div id="rfc.figure.u.22"></div><pre class="inline"><span id="rfc.iref.g.47"></span><span id="rfc.iref.g.48"></span><span id="rfc.iref.g.49"></span>  <a href="#transfer.codings" class="smpl">parameter</a>               = <a href="#rule.parameter" class="smpl">attribute</a> <a href="#rule.whitespace" class="smpl">BWS</a> "=" <a href="#rule.whitespace" class="smpl">BWS</a> <a href="#rule.parameter" class="smpl">value</a>
     1075      <div id="rfc.figure.u.26"></div><pre class="inline"><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>  <a href="#transfer.codings" class="smpl">parameter</a>               = <a href="#rule.parameter" class="smpl">attribute</a> <a href="#rule.whitespace" class="smpl">BWS</a> "=" <a href="#rule.whitespace" class="smpl">BWS</a> <a href="#rule.parameter" class="smpl">value</a>
    10551076  <a href="#rule.parameter" class="smpl">attribute</a>               = <a href="#rule.token.separators" class="smpl">token</a>
    10561077  <a href="#rule.parameter" class="smpl">value</a>                   = <a href="#rule.token.separators" class="smpl">token</a> / <a href="#rule.quoted-string" class="smpl">quoted-string</a>
    10571078</pre><p id="rfc.section.3.3.p.5">All transfer-coding values are case-insensitive. HTTP/1.1 uses transfer-coding values in the TE header field (<a href="#header.te" id="rfc.xref.header.te.1" title="TE">Section&nbsp;8.5</a>) and in the Transfer-Encoding header field (<a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.1" title="Transfer-Encoding">Section&nbsp;8.7</a>).
     
    10761097         indicator, followed by an <em class="bcp14">OPTIONAL</em> trailer containing entity-header fields. This allows dynamically produced content to be transferred along with the information
    10771098         necessary for the recipient to verify that it has received the full message.
    10781099      </p>
    1079       <div id="rfc.figure.u.23"></div><pre class="inline"><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><span id="rfc.iref.g.57"></span><span id="rfc.iref.g.58"></span>  <a href="#chunked.transfer.encoding" class="smpl">Chunked-Body</a>   = *<a href="#chunked.transfer.encoding" class="smpl">chunk</a>
     1100      <div id="rfc.figure.u.27"></div><pre class="inline"><span id="rfc.iref.g.56"></span><span id="rfc.iref.g.57"></span><span id="rfc.iref.g.58"></span><span id="rfc.iref.g.59"></span><span id="rfc.iref.g.60"></span><span id="rfc.iref.g.61"></span><span id="rfc.iref.g.62"></span><span id="rfc.iref.g.63"></span><span id="rfc.iref.g.64"></span>  <a href="#chunked.transfer.encoding" class="smpl">Chunked-Body</a>   = *<a href="#chunked.transfer.encoding" class="smpl">chunk</a>
    10801101                   <a href="#chunked.transfer.encoding" class="smpl">last-chunk</a>
    10811102                   <a href="#chunked.transfer.encoding" class="smpl">trailer-part</a>
    10821103                   <a href="#core.rules" class="smpl">CRLF</a>
     
    11141135         infinite buffer on the proxy.
    11151136      </p>
    11161137      <p id="rfc.section.3.3.1.p.7">A process for decoding the "chunked" transfer-coding can be represented in pseudo-code as:</p>
    1117       <div id="rfc.figure.u.24"></div><pre class="text">  length := 0
     1138      <div id="rfc.figure.u.28"></div><pre class="text">  length := 0
    11181139  read chunk-size, chunk-ext (if any) and CRLF
    11191140  while (chunk-size &gt; 0) {
    11201141     read chunk-data and CRLF
     
    11361157         using product tokens also allow sub-products which form a significant part of the application to be listed, separated by whitespace.
    11371158         By convention, the products are listed in order of their significance for identifying the application.
    11381159      </p>
    1139       <div id="rfc.figure.u.25"></div><pre class="inline"><span id="rfc.iref.g.59"></span><span id="rfc.iref.g.60"></span>  <a href="#product.tokens" class="smpl">product</a>         = <a href="#rule.token.separators" class="smpl">token</a> ["/" <a href="#product.tokens" class="smpl">product-version</a>]
     1160      <div id="rfc.figure.u.29"></div><pre class="inline"><span id="rfc.iref.g.65"></span><span id="rfc.iref.g.66"></span>  <a href="#product.tokens" class="smpl">product</a>         = <a href="#rule.token.separators" class="smpl">token</a> ["/" <a href="#product.tokens" class="smpl">product-version</a>]
    11401161  <a href="#product.tokens" class="smpl">product-version</a> = <a href="#rule.token.separators" class="smpl">token</a>
    11411162</pre><p id="rfc.section.3.4.p.3">Examples:</p>
    1142       <div id="rfc.figure.u.26"></div><pre class="text">  User-Agent: CERN-LineMode/2.15 libwww/2.17b3
     1163      <div id="rfc.figure.u.30"></div><pre class="text">  User-Agent: CERN-LineMode/2.15 libwww/2.17b3
    11431164  Server: Apache/0.8.4
    11441165</pre><p id="rfc.section.3.4.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).
    11451166      </p>
     
    11481169         is normalized to a real number in the range 0 through 1, where 0 is the minimum and 1 the maximum value. If a parameter has
    11491170         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.
    11501171      </p>
    1151       <div id="rfc.figure.u.27"></div><pre class="inline"><span id="rfc.iref.g.61"></span>  <a href="#quality.values" class="smpl">qvalue</a>         = ( "0" [ "." 0*3<a href="#core.rules" class="smpl">DIGIT</a> ] )
     1172      <div id="rfc.figure.u.31"></div><pre class="inline"><span id="rfc.iref.g.67"></span>  <a href="#quality.values" class="smpl">qvalue</a>         = ( "0" [ "." 0*3<a href="#core.rules" class="smpl">DIGIT</a> ] )
    11521173                 / ( "1" [ "." 0*3("0") ] )
    11531174</pre><div class="note">
    11541175         <p> <b>Note:</b> "Quality values" is a misnomer, since these values merely represent relative degradation in desired quality.
     
    11571178      <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="http.message" href="#http.message">HTTP Message</a></h1>
    11581179      <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>
    11591180      <p id="rfc.section.4.1.p.1">HTTP messages consist of requests from client to server and responses from server to client.</p>
    1160       <div id="rfc.figure.u.28"></div><pre class="inline"><span id="rfc.iref.g.62"></span>  <a href="#message.types" class="smpl">HTTP-message</a>   = <a href="#request" class="smpl">Request</a> / <a href="#response" class="smpl">Response</a>     ; HTTP/1.1 messages
    1161 </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="#RFC5322" id="rfc.xref.RFC5322.2"><cite title="Internet Message Format">[RFC5322]</cite></a> for transferring entities (the payload of the message). Both types of message consist of a start-line, zero or more header
     1181      <div id="rfc.figure.u.32"></div><pre class="inline"><span id="rfc.iref.g.68"></span>  <a href="#message.types" class="smpl">HTTP-message</a>   = <a href="#request" class="smpl">Request</a> / <a href="#response" class="smpl">Response</a>     ; HTTP/1.1 messages
     1182</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="#RFC5322" id="rfc.xref.RFC5322.3"><cite title="Internet Message Format">[RFC5322]</cite></a> for transferring entities (the payload of the message). Both types of message consist of a start-line, zero or more header
    11621183         fields (also known as "headers"), an empty line (i.e., a line with nothing preceding the CRLF) indicating the end of the header
    11631184         fields, and possibly a message-body.
    11641185      </p>
    1165       <div id="rfc.figure.u.29"></div><pre class="inline"><span id="rfc.iref.g.63"></span><span id="rfc.iref.g.64"></span>  <a href="#message.types" class="smpl">generic-message</a> = <a href="#message.types" class="smpl">start-line</a>
     1186      <div id="rfc.figure.u.33"></div><pre class="inline"><span id="rfc.iref.g.69"></span><span id="rfc.iref.g.70"></span>  <a href="#message.types" class="smpl">generic-message</a> = <a href="#message.types" class="smpl">start-line</a>
    11661187                    *( <a href="#message.headers" class="smpl">message-header</a> <a href="#core.rules" class="smpl">CRLF</a> )
    11671188                    <a href="#core.rules" class="smpl">CRLF</a>
    11681189                    [ <a href="#message.body" class="smpl">message-body</a> ]
     
    11781199         security issues when implementations within the request chain interpret the same message differently. HTTP/1.1 servers <em class="bcp14">MUST</em> reject such a message with a 400 (Bad Request) response.
    11791200      </p>
    11801201      <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>
    1181       <p id="rfc.section.4.2.p.1">HTTP header fields follow the same general format as Internet messages in <a href="http://tools.ietf.org/html/rfc5322#section-2.1">Section 2.1</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.3"><cite title="Internet Message Format">[RFC5322]</cite></a>. Each header field consists of a name followed by a colon (":"), optional whitespace, and the field value. Field names are
     1202      <p id="rfc.section.4.2.p.1">HTTP header fields follow the same general format as Internet messages in <a href="http://tools.ietf.org/html/rfc5322#section-2.1">Section 2.1</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.4"><cite title="Internet Message Format">[RFC5322]</cite></a>. Each header field consists of a name followed by a colon (":"), optional whitespace, and the field value. Field names are
    11821203         case-insensitive.
    11831204      </p>
    1184       <div id="rfc.figure.u.30"></div><pre class="inline"><span id="rfc.iref.g.65"></span><span id="rfc.iref.g.66"></span><span id="rfc.iref.g.67"></span><span id="rfc.iref.g.68"></span>  <a href="#message.headers" class="smpl">message-header</a> = <a href="#message.headers" class="smpl">field-name</a> ":" OWS [ <a href="#message.headers" class="smpl">field-value</a> ] OWS
     1205      <div id="rfc.figure.u.34"></div><pre class="inline"><span id="rfc.iref.g.71"></span><span id="rfc.iref.g.72"></span><span id="rfc.iref.g.73"></span><span id="rfc.iref.g.74"></span>  <a href="#message.headers" class="smpl">message-header</a> = <a href="#message.headers" class="smpl">field-name</a> ":" OWS [ <a href="#message.headers" class="smpl">field-value</a> ] OWS
    11851206  <a href="#message.headers" class="smpl">field-name</a>     = <a href="#rule.token.separators" class="smpl">token</a>
    11861207  <a href="#message.headers" class="smpl">field-value</a>    = *( <a href="#message.headers" class="smpl">field-content</a> / <a href="#rule.whitespace" class="smpl">OWS</a> )
    11871208  <a href="#message.headers" class="smpl">field-content</a>  = *( <a href="#core.rules" class="smpl">WSP</a> / <a href="#core.rules" class="smpl">VCHAR</a> / <a href="#rule.quoted-string" class="smpl">obs-text</a> )
     
    12061227            of the field value.
    12071228         </p>
    12081229      </div>
    1209       <div id="rfc.figure.u.31"></div><pre class="inline"><span id="rfc.iref.g.69"></span><span id="rfc.iref.g.70"></span>  <a href="#rule.comment" class="smpl">comment</a>        = "(" *( <a href="#rule.comment" class="smpl">ctext</a> / <a href="#rule.quoted-pair" class="smpl">quoted-pair</a> / <a href="#rule.comment" class="smpl">comment</a> ) ")"
     1230      <div id="rfc.figure.u.35"></div><pre class="inline"><span id="rfc.iref.g.75"></span><span id="rfc.iref.g.76"></span>  <a href="#rule.comment" class="smpl">comment</a>        = "(" *( <a href="#rule.comment" class="smpl">ctext</a> / <a href="#rule.quoted-pair" class="smpl">quoted-pair</a> / <a href="#rule.comment" class="smpl">comment</a> ) ")"
    12101231  <a href="#rule.comment" class="smpl">ctext</a>          = <a href="#rule.whitespace" class="smpl">OWS</a> / %x21-27 / %x2A-5B / %x5D-7E / <a href="#rule.quoted-string" class="smpl">obs-text</a>
    12111232                 ; <a href="#rule.whitespace" class="smpl">OWS</a> / &lt;<a href="#core.rules" class="smpl">VCHAR</a> except "(", ")", and "\"&gt; / <a href="#rule.quoted-string" class="smpl">obs-text</a>
    12121233</pre><p id="rfc.section.4.2.p.9">The order in which header fields with differing field names are received is not significant. However, it is "good practice"
     
    12291250         message-body differs from the entity-body only when a transfer-coding has been applied, as indicated by the Transfer-Encoding
    12301251         header field (<a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.2" title="Transfer-Encoding">Section&nbsp;8.7</a>).
    12311252      </p>
    1232       <div id="rfc.figure.u.32"></div><pre class="inline"><span id="rfc.iref.g.71"></span>  <a href="#message.body" class="smpl">message-body</a> = <a href="#abnf.dependencies" class="smpl">entity-body</a>
     1253      <div id="rfc.figure.u.36"></div><pre class="inline"><span id="rfc.iref.g.77"></span>  <a href="#message.body" class="smpl">message-body</a> = <a href="#abnf.dependencies" class="smpl">entity-body</a>
    12331254               / &lt;entity-body encoded as per <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a>&gt;
    12341255</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
    12351256         is a property of the message, not of the entity, and thus <em class="bcp14">MAY</em> be added or removed by any application along the request/response chain. (However, <a href="#transfer.codings" title="Transfer Codings">Section&nbsp;3.3</a> places restrictions on when certain transfer-codings may be used.)
     
    12961317      <p id="rfc.section.4.5.p.1">There are a few header fields which have general applicability for both request and response messages, but which do not apply
    12971318         to the entity being transferred. These header fields apply only to the message being transmitted.
    12981319      </p>
    1299       <div id="rfc.figure.u.33"></div><pre class="inline"><span id="rfc.iref.g.72"></span>  <a href="#general.header.fields" class="smpl">general-header</a> = <a href="#abnf.dependencies" class="smpl">Cache-Control</a>            ; <a href="#Part6" id="rfc.xref.Part6.5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 3.2</a>
     1320      <div id="rfc.figure.u.37"></div><pre class="inline"><span id="rfc.iref.g.78"></span>  <a href="#general.header.fields" class="smpl">general-header</a> = <a href="#abnf.dependencies" class="smpl">Cache-Control</a>            ; <a href="#Part6" id="rfc.xref.Part6.5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 3.2</a>
    13001321                 / <a href="#header.connection" class="smpl">Connection</a>               ; <a href="#header.connection" id="rfc.xref.header.connection.1" title="Connection">Section&nbsp;8.1</a>
    13011322                 / <a href="#header.date" class="smpl">Date</a>                     ; <a href="#header.date" id="rfc.xref.header.date.1" title="Date">Section&nbsp;8.3</a>
    13021323                 / <a href="#abnf.dependencies" class="smpl">Pragma</a>                   ; <a href="#Part6" id="rfc.xref.Part6.6"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.pragma" title="Pragma">Section 3.4</a>
     
    13131334      <p id="rfc.section.5.p.1">A request message from a client to a server includes, within the first line of that message, the method to be applied to the
    13141335         resource, the identifier of the resource, and the protocol version in use.
    13151336      </p>
    1316       <div id="rfc.figure.u.34"></div><pre class="inline"><span id="rfc.iref.g.73"></span>  <a href="#request" class="smpl">Request</a>       = <a href="#request-line" class="smpl">Request-Line</a>              ; <a href="#request-line" title="Request-Line">Section&nbsp;5.1</a>
     1337      <div id="rfc.figure.u.38"></div><pre class="inline"><span id="rfc.iref.g.79"></span>  <a href="#request" class="smpl">Request</a>       = <a href="#request-line" class="smpl">Request-Line</a>              ; <a href="#request-line" title="Request-Line">Section&nbsp;5.1</a>
    13171338                  *(( <a href="#general.header.fields" class="smpl">general-header</a>        ; <a href="#general.header.fields" title="General Header Fields">Section&nbsp;4.5</a>
    13181339                   / <a href="#abnf.dependencies" class="smpl">request-header</a>         ; <a href="#Part2" id="rfc.xref.Part2.4"><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 3</a>
    13191340                   / <a href="#abnf.dependencies" class="smpl">entity-header</a> ) <a href="#core.rules" class="smpl">CRLF</a> )  ; <a href="#Part3" id="rfc.xref.Part3.8"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>, <a href="p3-payload.html#entity.header.fields" title="Entity Header Fields">Section 3.1</a>
     
    13231344      <p id="rfc.section.5.1.p.1">The Request-Line begins with a method token, followed by the request-target and the protocol version, and ending with CRLF.
    13241345         The elements are separated by SP characters. No CR or LF is allowed except in the final CRLF sequence.
    13251346      </p>
    1326       <div id="rfc.figure.u.35"></div><pre class="inline"><span id="rfc.iref.g.74"></span>  <a href="#request-line" class="smpl">Request-Line</a>   = <a href="#method" class="smpl">Method</a> <a href="#core.rules" class="smpl">SP</a> <a href="#request-target" class="smpl">request-target</a> <a href="#core.rules" class="smpl">SP</a> <a href="#http.version" class="smpl">HTTP-Version</a> <a href="#core.rules" class="smpl">CRLF</a>
     1347      <div id="rfc.figure.u.39"></div><pre class="inline"><span id="rfc.iref.g.80"></span>  <a href="#request-line" class="smpl">Request-Line</a>   = <a href="#method" class="smpl">Method</a> <a href="#core.rules" class="smpl">SP</a> <a href="#request-target" class="smpl">request-target</a> <a href="#core.rules" class="smpl">SP</a> <a href="#http.version" class="smpl">HTTP-Version</a> <a href="#core.rules" class="smpl">CRLF</a>
    13271348</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>
    13281349      <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-target. The method is case-sensitive.</p>
    1329       <div id="rfc.figure.u.36"></div><pre class="inline"><span id="rfc.iref.g.75"></span><span id="rfc.iref.g.76"></span>  <a href="#method" class="smpl">Method</a>         = <a href="#rule.token.separators" class="smpl">token</a>
     1350      <div id="rfc.figure.u.40"></div><pre class="inline"><span id="rfc.iref.g.81"></span><span id="rfc.iref.g.82"></span>  <a href="#method" class="smpl">Method</a>         = <a href="#rule.token.separators" class="smpl">token</a>
    13301351</pre><h3 id="rfc.section.5.1.2"><a href="#rfc.section.5.1.2">5.1.2</a>&nbsp;<a id="request-target" href="#request-target">request-target</a></h3>
    13311352      <p id="rfc.section.5.1.2.p.1">The request-target identifies the resource upon which to apply the request.</p>
    1332       <div id="rfc.figure.u.37"></div><pre class="inline"><span id="rfc.iref.g.77"></span>  <a href="#request-target" class="smpl">request-target</a> = "*"
     1353      <div id="rfc.figure.u.41"></div><pre class="inline"><span id="rfc.iref.g.83"></span>  <a href="#request-target" class="smpl">request-target</a> = "*"
    13331354                 / <a href="#uri" class="smpl">absolute-URI</a>
    13341355                 / ( <a href="#uri" class="smpl">path-absolute</a> [ "?" <a href="#uri" class="smpl">query</a> ] )
    13351356                 / <a href="#uri" class="smpl">authority</a>
     
    13371358         not apply to a particular resource, but to the server itself, and is only allowed when the method used does not necessarily
    13381359         apply to a resource. One example would be
    13391360      </p>
    1340       <div id="rfc.figure.u.38"></div><pre class="text">  OPTIONS * HTTP/1.1
     1361      <div id="rfc.figure.u.42"></div><pre class="text">  OPTIONS * HTTP/1.1
    13411362</pre><p id="rfc.section.5.1.2.p.5">The absolute-URI 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,
    13421363         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 absolute-URI. In order to avoid request
    13431364         loops, a proxy <em class="bcp14">MUST</em> be able to recognize all of its server names, including any aliases, local variations, and the numeric IP address. An example
    13441365         Request-Line would be:
    13451366      </p>
    1346       <div id="rfc.figure.u.39"></div><pre class="text">  GET http://www.example.org/pub/WWW/TheProject.html HTTP/1.1
     1367      <div id="rfc.figure.u.43"></div><pre class="text">  GET http://www.example.org/pub/WWW/TheProject.html HTTP/1.1
    13471368</pre><p id="rfc.section.5.1.2.p.7">To allow for transition to absolute-URIs in all requests in future versions of HTTP, all HTTP/1.1 servers <em class="bcp14">MUST</em> accept the absolute-URI form in requests, even though HTTP/1.1 clients will only generate them in requests to proxies.
    13481369      </p>
    13491370      <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 7.9</a> of <a href="#Part2" id="rfc.xref.Part2.5"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>).
     
    13521373         absolute path of the URI <em class="bcp14">MUST</em> be transmitted (see <a href="#http.uri" title="http URI scheme">Section&nbsp;2.1.1</a>, path-absolute) as the request-target, and the network location of the URI (authority) <em class="bcp14">MUST</em> be transmitted in a Host header field. For example, a client wishing to retrieve the resource above directly from the origin
    13531374         server would create a TCP connection to port 80 of the host "www.example.org" and send the lines:
    13541375      </p>
    1355       <div id="rfc.figure.u.40"></div><pre class="text">  GET /pub/WWW/TheProject.html HTTP/1.1
     1376      <div id="rfc.figure.u.44"></div><pre class="text">  GET /pub/WWW/TheProject.html HTTP/1.1
    13561377  Host: www.example.org
    13571378</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
    13581379         URI, it <em class="bcp14">MUST</em> be given as "/" (the server root).
     
    13601381      <p id="rfc.section.5.1.2.p.12">If a proxy receives a request without any path in the request-target and the method specified is capable of supporting the
    13611382         asterisk form of request-target, then the last proxy on the request chain <em class="bcp14">MUST</em> forward the request with "*" as the final request-target.
    13621383      </p>
    1363       <div id="rfc.figure.u.41"></div>
     1384      <div id="rfc.figure.u.45"></div>
    13641385      <p>For example, the request</p><pre class="text">  OPTIONS http://www.example.org:8001 HTTP/1.1
    1365 </pre><div id="rfc.figure.u.42"></div>
     1386</pre><div id="rfc.figure.u.46"></div>
    13661387      <p>would be forwarded by the proxy as</p><pre class="text">  OPTIONS * HTTP/1.1
    13671388  Host: www.example.org:8001
    13681389</pre>  <p>after connecting to port 8001 of host "www.example.org".</p>
     
    14051426      </p>
    14061427      <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="response" href="#response">Response</a></h1>
    14071428      <p id="rfc.section.6.p.1">After receiving and interpreting a request message, a server responds with an HTTP response message.</p>
    1408       <div id="rfc.figure.u.43"></div><pre class="inline"><span id="rfc.iref.g.78"></span>  <a href="#response" class="smpl">Response</a>      = <a href="#status-line" class="smpl">Status-Line</a>               ; <a href="#status-line" title="Status-Line">Section&nbsp;6.1</a>
     1429      <div id="rfc.figure.u.47"></div><pre class="inline"><span id="rfc.iref.g.84"></span>  <a href="#response" class="smpl">Response</a>      = <a href="#status-line" class="smpl">Status-Line</a>               ; <a href="#status-line" title="Status-Line">Section&nbsp;6.1</a>
    14091430                  *(( <a href="#general.header.fields" class="smpl">general-header</a>        ; <a href="#general.header.fields" title="General Header Fields">Section&nbsp;4.5</a>
    14101431                   / <a href="#abnf.dependencies" class="smpl">response-header</a>        ; <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 5</a>
    14111432                   / <a href="#abnf.dependencies" class="smpl">entity-header</a> ) <a href="#core.rules" class="smpl">CRLF</a> )  ; <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 3.1</a>
     
    14161437         and its associated textual phrase, with each element separated by SP characters. No CR or LF is allowed except in the final
    14171438         CRLF sequence.
    14181439      </p>
    1419       <div id="rfc.figure.u.44"></div><pre class="inline"><span id="rfc.iref.g.79"></span>  <a href="#status-line" class="smpl">Status-Line</a> = <a href="#http.version" class="smpl">HTTP-Version</a> <a href="#core.rules" class="smpl">SP</a> <a href="#status.code.and.reason.phrase" class="smpl">Status-Code</a> <a href="#core.rules" class="smpl">SP</a> <a href="#status.code.and.reason.phrase" class="smpl">Reason-Phrase</a> <a href="#core.rules" class="smpl">CRLF</a>
     1440      <div id="rfc.figure.u.48"></div><pre class="inline"><span id="rfc.iref.g.85"></span>  <a href="#status-line" class="smpl">Status-Line</a> = <a href="#http.version" class="smpl">HTTP-Version</a> <a href="#core.rules" class="smpl">SP</a> <a href="#status.code.and.reason.phrase" class="smpl">Status-Code</a> <a href="#core.rules" class="smpl">SP</a> <a href="#status.code.and.reason.phrase" class="smpl">Reason-Phrase</a> <a href="#core.rules" class="smpl">CRLF</a>
    14201441</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>
    14211442      <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
    14221443         are fully defined in <a href="p2-semantics.html#status.codes" title="Status Code Definitions">Section 8</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,
     
    14331454         <li>4xx: Client Error - The request contains bad syntax or cannot be fulfilled</li>
    14341455         <li>5xx: Server Error - The server failed to fulfill an apparently valid request</li>
    14351456      </ul>
    1436       <div id="rfc.figure.u.45"></div><pre class="inline"><span id="rfc.iref.g.80"></span><span id="rfc.iref.g.81"></span><span id="rfc.iref.g.82"></span>  <a href="#status.code.and.reason.phrase" class="smpl">Status-Code</a>    = 3<a href="#core.rules" class="smpl">DIGIT</a>
     1457      <div id="rfc.figure.u.49"></div><pre class="inline"><span id="rfc.iref.g.86"></span><span id="rfc.iref.g.87"></span><span id="rfc.iref.g.88"></span>  <a href="#status.code.and.reason.phrase" class="smpl">Status-Code</a>    = 3<a href="#core.rules" class="smpl">DIGIT</a>
    14371458  <a href="#status.code.and.reason.phrase" class="smpl">Reason-Phrase</a>  = *( <a href="#core.rules" class="smpl">WSP</a> / <a href="#core.rules" class="smpl">VCHAR</a> / <a href="#rule.quoted-string" class="smpl">obs-text</a> )
    14381459</pre><h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="connections" href="#connections">Connections</a></h1>
    14391460      <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a id="persistent.connections" href="#persistent.connections">Persistent Connections</a></h2>
     
    16251646         and <em class="bcp14">MUST NOT</em> be communicated by proxies over further connections.
    16261647      </p>
    16271648      <p id="rfc.section.8.1.p.2">The Connection header's value has the following grammar:</p>
    1628       <div id="rfc.figure.u.46"></div><pre class="inline"><span id="rfc.iref.g.83"></span><span id="rfc.iref.g.84"></span><span id="rfc.iref.g.85"></span>  <a href="#header.connection" class="smpl">Connection</a>       = "Connection" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.connection" class="smpl">Connection-v</a>
     1649      <div id="rfc.figure.u.50"></div><pre class="inline"><span id="rfc.iref.g.89"></span><span id="rfc.iref.g.90"></span><span id="rfc.iref.g.91"></span>  <a href="#header.connection" class="smpl">Connection</a>       = "Connection" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.connection" class="smpl">Connection-v</a>
    16291650  <a href="#header.connection" class="smpl">Connection-v</a>     = 1#<a href="#header.connection" class="smpl">connection-token</a>
    16301651  <a href="#header.connection" class="smpl">connection-token</a> = <a href="#rule.token.separators" class="smpl">token</a>
    16311652</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
     
    16381659      <p id="rfc.section.8.1.p.6">HTTP/1.1 defines the "close" connection option for the sender to signal that the connection will be closed after completion
    16391660         of the response. For example,
    16401661      </p>
    1641       <div id="rfc.figure.u.47"></div><pre class="text">  Connection: close
     1662      <div id="rfc.figure.u.51"></div><pre class="text">  Connection: close
    16421663</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.
    16431664      </p>
    16441665      <p id="rfc.section.8.1.p.9">An HTTP/1.1 client that does not support persistent connections <em class="bcp14">MUST</em> include the "close" connection option in every request message.
     
    16541675      <p id="rfc.section.8.2.p.1">The entity-header field "Content-Length" indicates the size of the entity-body, in number of OCTETs, sent to the recipient
    16551676         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.
    16561677      </p>
    1657       <div id="rfc.figure.u.48"></div><pre class="inline"><span id="rfc.iref.g.86"></span><span id="rfc.iref.g.87"></span>  <a href="#header.content-length" class="smpl">Content-Length</a>   = "Content-Length" ":" <a href="#rule.whitespace" class="smpl">OWS</a> 1*<a href="#header.content-length" class="smpl">Content-Length-v</a>
     1678      <div id="rfc.figure.u.52"></div><pre class="inline"><span id="rfc.iref.g.92"></span><span id="rfc.iref.g.93"></span>  <a href="#header.content-length" class="smpl">Content-Length</a>   = "Content-Length" ":" <a href="#rule.whitespace" class="smpl">OWS</a> 1*<a href="#header.content-length" class="smpl">Content-Length-v</a>
    16581679  <a href="#header.content-length" class="smpl">Content-Length-v</a> = 1*<a href="#core.rules" class="smpl">DIGIT</a>
    16591680</pre><p id="rfc.section.8.2.p.3">An example is</p>
    1660       <div id="rfc.figure.u.49"></div><pre class="text">  Content-Length: 3495
     1681      <div id="rfc.figure.u.53"></div><pre class="text">  Content-Length: 3495
    16611682</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>.
    16621683      </p>
    16631684      <p id="rfc.section.8.2.p.6">Any Content-Length greater than or equal to zero is a valid value. <a href="#message.length" title="Message Length">Section&nbsp;4.4</a> describes how to determine the length of a message-body if a Content-Length is not given.
     
    16701691      <div id="rfc.iref.h.5"></div>
    16711692      <h2 id="rfc.section.8.3"><a href="#rfc.section.8.3">8.3</a>&nbsp;<a id="header.date" href="#header.date">Date</a></h2>
    16721693      <p id="rfc.section.8.3.p.1">The general-header field "Date" represents the date and time at which the message was originated, having the same semantics
    1673          as orig-date in <a href="http://tools.ietf.org/html/rfc5322#section-3.6.1">Section 3.6.1</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.4"><cite title="Internet Message Format">[RFC5322]</cite></a>. The field value is an HTTP-date, as described in <a href="#full.date" title="Full Date">Section&nbsp;3.2.1</a>; it <em class="bcp14">MUST</em> be sent in rfc1123-date format.
     1694         as orig-date in <a href="http://tools.ietf.org/html/rfc5322#section-3.6.1">Section 3.6.1</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.5"><cite title="Internet Message Format">[RFC5322]</cite></a>. The field value is an HTTP-date, as described in <a href="#full.date" title="Full Date">Section&nbsp;3.2.1</a>; it <em class="bcp14">MUST</em> be sent in rfc1123-date format.
    16741695      </p>
    1675       <div id="rfc.figure.u.50"></div><pre class="inline"><span id="rfc.iref.g.88"></span><span id="rfc.iref.g.89"></span>  <a href="#header.date" class="smpl">Date</a>   = "Date" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.date" class="smpl">Date-v</a>
     1696      <div id="rfc.figure.u.54"></div><pre class="inline"><span id="rfc.iref.g.94"></span><span id="rfc.iref.g.95"></span>  <a href="#header.date" class="smpl">Date</a>   = "Date" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.date" class="smpl">Date-v</a>
    16761697  <a href="#header.date" class="smpl">Date-v</a> = <a href="#full.date" class="smpl">HTTP-date</a>
    16771698</pre><p id="rfc.section.8.3.p.3">An example is</p>
    1678       <div id="rfc.figure.u.51"></div><pre class="text">  Date: Tue, 15 Nov 1994 08:12:31 GMT
     1699      <div id="rfc.figure.u.55"></div><pre class="text">  Date: Tue, 15 Nov 1994 08:12:31 GMT
    16791700</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:
    16801701      </p>
    16811702      <ol>
     
    17111732         gateway to differentiate between internally-ambiguous URLs, such as the root "/" URL of a server for multiple host names on
    17121733         a single IP address.
    17131734      </p>
    1714       <div id="rfc.figure.u.52"></div><pre class="inline"><span id="rfc.iref.g.90"></span><span id="rfc.iref.g.91"></span>  <a href="#header.host" class="smpl">Host</a>   = "Host" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.host" class="smpl">Host-v</a>
     1735      <div id="rfc.figure.u.56"></div><pre class="inline"><span id="rfc.iref.g.96"></span><span id="rfc.iref.g.97"></span>  <a href="#header.host" class="smpl">Host</a>   = "Host" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.host" class="smpl">Host-v</a>
    17151736  <a href="#header.host" class="smpl">Host-v</a> = <a href="#uri" class="smpl">uri-host</a> [ ":" <a href="#uri" class="smpl">port</a> ] ; <a href="#http.uri" title="http URI scheme">Section&nbsp;2.1.1</a>
    17161737</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
    17171738         URL). For example, a request on the origin server for &lt;http://www.example.org/pub/WWW/&gt; would properly include:
    17181739      </p>
    1719       <div id="rfc.figure.u.53"></div><pre class="text">  GET /pub/WWW/ HTTP/1.1
     1740      <div id="rfc.figure.u.57"></div><pre class="text">  GET /pub/WWW/ HTTP/1.1
    17201741  Host: www.example.org
    17211742</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
    17221743         for the service being requested, then the Host header field <em class="bcp14">MUST</em> be given with an empty value. An HTTP/1.1 proxy <em class="bcp14">MUST</em> ensure that any request message it forwards does contain an appropriate Host header field that identifies the service being
     
    17311752         or not it is willing to accept trailer fields in a chunked transfer-coding. Its value may consist of the keyword "trailers"
    17321753         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.3</a>).
    17331754      </p>
    1734       <div id="rfc.figure.u.54"></div><pre class="inline"><span id="rfc.iref.g.92"></span><span id="rfc.iref.g.93"></span><span id="rfc.iref.g.94"></span><span id="rfc.iref.g.95"></span><span id="rfc.iref.g.96"></span>  <a href="#header.te" class="smpl">TE</a>        = "TE" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.te" class="smpl">TE-v</a>
     1755      <div id="rfc.figure.u.58"></div><pre class="inline"><span id="rfc.iref.g.98"></span><span id="rfc.iref.g.99"></span><span id="rfc.iref.g.100"></span><span id="rfc.iref.g.101"></span><span id="rfc.iref.g.102"></span>  <a href="#header.te" class="smpl">TE</a>        = "TE" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.te" class="smpl">TE-v</a>
    17351756  <a href="#header.te" class="smpl">TE-v</a>      = #<a href="#header.te" class="smpl">t-codings</a>
    17361757  <a href="#header.te" class="smpl">t-codings</a> = "trailers" / ( <a href="#transfer.codings" class="smpl">transfer-extension</a> [ <a href="#header.te" class="smpl">te-params</a> ] )
    17371758  <a href="#header.te" class="smpl">te-params</a> = <a href="#rule.whitespace" class="smpl">OWS</a> ";" <a href="#rule.whitespace" class="smpl">OWS</a> "q=" <a href="#quality.values" class="smpl">qvalue</a> *( <a href="#header.te" class="smpl">te-ext</a> )
     
    17401761         as defined in <a href="#chunked.transfer.encoding" title="Chunked Transfer Coding">Section&nbsp;3.3.1</a>. This keyword is reserved for use with transfer-coding values even though it does not itself represent a transfer-coding.
    17411762      </p>
    17421763      <p id="rfc.section.8.5.p.4">Examples of its use are:</p>
    1743       <div id="rfc.figure.u.55"></div><pre class="text">  TE: deflate
     1764      <div id="rfc.figure.u.59"></div><pre class="text">  TE: deflate
    17441765  TE:
    17451766  TE: trailers, deflate;q=0.5
    17461767</pre><p id="rfc.section.8.5.p.6">The TE header field only applies to the immediate connection. Therefore, the keyword <em class="bcp14">MUST</em> be supplied within a Connection header field (<a href="#header.connection" id="rfc.xref.header.connection.4" title="Connection">Section&nbsp;8.1</a>) whenever TE is present in an HTTP/1.1 message.
     
    17771798      <p id="rfc.section.8.6.p.1">The general field "Trailer" indicates that the given set of header fields is present in the trailer of a message encoded with
    17781799         chunked transfer-coding.
    17791800      </p>
    1780       <div id="rfc.figure.u.56"></div><pre class="inline"><span id="rfc.iref.g.97"></span><span id="rfc.iref.g.98"></span>  <a href="#header.trailer" class="smpl">Trailer</a>   = "Trailer" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.trailer" class="smpl">Trailer-v</a>
     1801      <div id="rfc.figure.u.60"></div><pre class="inline"><span id="rfc.iref.g.103"></span><span id="rfc.iref.g.104"></span>  <a href="#header.trailer" class="smpl">Trailer</a>   = "Trailer" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.trailer" class="smpl">Trailer-v</a>
    17811802  <a href="#header.trailer" class="smpl">Trailer-v</a> = 1#<a href="#message.headers" class="smpl">field-name</a>
    17821803</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
    17831804         to know which header fields to expect in the trailer.
     
    17981819         body in order to safely transfer it between the sender and the recipient. This differs from the content-coding in that the
    17991820         transfer-coding is a property of the message, not of the entity.
    18001821      </p>
    1801       <div id="rfc.figure.u.57"></div><pre class="inline"><span id="rfc.iref.g.99"></span><span id="rfc.iref.g.100"></span>  <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a>   = "Transfer-Encoding" ":" <a href="#rule.whitespace" class="smpl">OWS</a>
     1822      <div id="rfc.figure.u.61"></div><pre class="inline"><span id="rfc.iref.g.105"></span><span id="rfc.iref.g.106"></span>  <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a>   = "Transfer-Encoding" ":" <a href="#rule.whitespace" class="smpl">OWS</a>
    18021823                        <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding-v</a>
    18031824  <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding-v</a> = 1#<a href="#transfer.codings" class="smpl">transfer-coding</a>
    18041825</pre><p id="rfc.section.8.7.p.3">Transfer-codings are defined in <a href="#transfer.codings" title="Transfer Codings">Section&nbsp;3.3</a>. An example is:
    18051826      </p>
    1806       <div id="rfc.figure.u.58"></div><pre class="text">  Transfer-Encoding: chunked
     1827      <div id="rfc.figure.u.62"></div><pre class="text">  Transfer-Encoding: chunked
    18071828</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.
    18081829      </p>
    18091830      <p id="rfc.section.8.7.p.6">Many older HTTP/1.0 applications do not understand the Transfer-Encoding header.</p>
     
    18131834      <p id="rfc.section.8.8.p.1">The general-header "Upgrade" allows the client to specify what additional communication protocols it supports and would like
    18141835         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.
    18151836      </p>
    1816       <div id="rfc.figure.u.59"></div><pre class="inline"><span id="rfc.iref.g.101"></span><span id="rfc.iref.g.102"></span>  <a href="#header.upgrade" class="smpl">Upgrade</a>   = "Upgrade" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.upgrade" class="smpl">Upgrade-v</a>
     1837      <div id="rfc.figure.u.63"></div><pre class="inline"><span id="rfc.iref.g.107"></span><span id="rfc.iref.g.108"></span>  <a href="#header.upgrade" class="smpl">Upgrade</a>   = "Upgrade" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.upgrade" class="smpl">Upgrade-v</a>
    18171838  <a href="#header.upgrade" class="smpl">Upgrade-v</a> = 1#<a href="#product.tokens" class="smpl">product</a>
    18181839</pre><p id="rfc.section.8.8.p.3">For example,</p>
    1819       <div id="rfc.figure.u.60"></div><pre class="text">  Upgrade: HTTP/2.0, SHTTP/1.3, IRC/6.9, RTA/x11
     1840      <div id="rfc.figure.u.64"></div><pre class="text">  Upgrade: HTTP/2.0, SHTTP/1.3, IRC/6.9, RTA/x11
    18201841</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
    18211842         protocol. It does so by allowing the client to advertise its desire to use another protocol, such as a later version of HTTP
    18221843         with a higher major version number, even though the current request has been made using HTTP/1.1. This eases the difficult
     
    18421863      <div id="rfc.iref.h.12"></div>
    18431864      <h2 id="rfc.section.8.9"><a href="#rfc.section.8.9">8.9</a>&nbsp;<a id="header.via" href="#header.via">Via</a></h2>
    18441865      <p id="rfc.section.8.9.p.1">The general-header field "Via" <em class="bcp14">MUST</em> be used by gateways and proxies to indicate the intermediate protocols and recipients between the user agent and the server
    1845          on requests, and between the origin server and the client on responses. It is analogous to the "Received" field defined in <a href="http://tools.ietf.org/html/rfc5322#section-3.6.7">Section 3.6.7</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.5"><cite title="Internet Message Format">[RFC5322]</cite></a> and is intended to be used for tracking message forwards, avoiding request loops, and identifying the protocol capabilities
     1866         on requests, and between the origin server and the client on responses. It is analogous to the "Received" field defined in <a href="http://tools.ietf.org/html/rfc5322#section-3.6.7">Section 3.6.7</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.6"><cite title="Internet Message Format">[RFC5322]</cite></a> and is intended to be used for tracking message forwards, avoiding request loops, and identifying the protocol capabilities
    18461867         of all senders along the request/response chain.
    18471868      </p>
    1848       <div id="rfc.figure.u.61"></div><pre class="inline"><span id="rfc.iref.g.103"></span><span id="rfc.iref.g.104"></span><span id="rfc.iref.g.105"></span><span id="rfc.iref.g.106"></span><span id="rfc.iref.g.107"></span><span id="rfc.iref.g.108"></span><span id="rfc.iref.g.109"></span>  <a href="#header.via" class="smpl">Via</a>               = "Via" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.via" class="smpl">Via-v</a>
     1869      <div id="rfc.figure.u.65"></div><pre class="inline"><span id="rfc.iref.g.109"></span><span id="rfc.iref.g.110"></span><span id="rfc.iref.g.111"></span><span id="rfc.iref.g.112"></span><span id="rfc.iref.g.113"></span><span id="rfc.iref.g.114"></span><span id="rfc.iref.g.115"></span>  <a href="#header.via" class="smpl">Via</a>               = "Via" ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.via" class="smpl">Via-v</a>
    18491870  <a href="#header.via" class="smpl">Via-v</a>             = 1#( <a href="#header.via" class="smpl">received-protocol</a> <a href="#rule.whitespace" class="smpl">RWS</a> <a href="#header.via" class="smpl">received-by</a>
    18501871                          [ <a href="#rule.whitespace" class="smpl">RWS</a> <a href="#rule.comment" class="smpl">comment</a> ] )
    18511872  <a href="#header.via" class="smpl">received-protocol</a> = [ <a href="#header.via" class="smpl">protocol-name</a> "/" ] <a href="#header.via" class="smpl">protocol-version</a>
     
    18701891         HTTP/1.1 to forward the request to a public proxy at p.example.net, which completes the request by forwarding it to the origin
    18711892         server at www.example.com. The request received by www.example.com would then have the following Via header field:
    18721893      </p>
    1873       <div id="rfc.figure.u.62"></div><pre class="text">  Via: 1.0 fred, 1.1 p.example.net (Apache/1.1)
     1894      <div id="rfc.figure.u.66"></div><pre class="text">  Via: 1.0 fred, 1.1 p.example.net (Apache/1.1)
    18741895</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.
    18751896      </p>
    18761897      <p id="rfc.section.8.9.p.10">For organizations that have strong privacy requirements for hiding internal structures, a proxy <em class="bcp14">MAY</em> combine an ordered subsequence of Via header field entries with identical received-protocol values into a single such entry.
    18771898         For example,
    18781899      </p>
    1879       <div id="rfc.figure.u.63"></div><pre class="text">  Via: 1.0 ricky, 1.1 ethel, 1.1 fred, 1.0 lucy
     1900      <div id="rfc.figure.u.67"></div><pre class="text">  Via: 1.0 ricky, 1.1 ethel, 1.1 fred, 1.0 lucy
    18801901</pre><p id="rfc.section.8.9.p.12">could be collapsed to</p>
    1881       <div id="rfc.figure.u.64"></div><pre class="text">  Via: 1.0 ricky, 1.1 mertz, 1.0 lucy
     1902      <div id="rfc.figure.u.68"></div><pre class="text">  Via: 1.0 ricky, 1.1 mertz, 1.0 lucy
    18821903</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
    18831904         by pseudonyms. Applications <em class="bcp14">MUST NOT</em> combine entries which have different received-protocol values.
    18841905      </p>
     
    25302551            entity-header fields and content in the form of an entity-body, as described in <a href="p3-payload.html#entity" title="Entity">Section 3</a> of <a href="#Part3" id="rfc.xref.Part3.13"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>.
    25312552         </dd>
    25322553      </dl>
    2533       <p id="rfc.section.C.p.8"> <span id="rfc.iref.g.110"></span>  <dfn>gateway</dfn> 
     2554      <p id="rfc.section.C.p.8"> <span id="rfc.iref.g.116"></span>  <dfn>gateway</dfn> 
    25342555      </p>
    25352556      <dl class="empty">
    25362557         <dd>A server which acts as an intermediary for some other server. Unlike a proxy, a gateway receives requests as if it were the
     
    26282649         </dd>
    26292650      </dl>
    26302651      <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
    2631       <div id="rfc.figure.u.65"></div> <pre class="inline"><a href="#rule.whitespace" class="smpl">BWS</a> = OWS
     2652      <div id="rfc.figure.u.69"></div> <pre class="inline"><a href="#rule.whitespace" class="smpl">BWS</a> = OWS
    26322653
    26332654<a href="#abnf.dependencies" class="smpl">Cache-Control</a> = &lt;Cache-Control, defined in [Part6], Section 3.4&gt;
    26342655<a href="#chunked.transfer.encoding" class="smpl">Chunked-Body</a> = *chunk last-chunk trailer-part CRLF
     
    26412662<a href="#header.date" class="smpl">Date</a> = "Date:" OWS Date-v
    26422663<a href="#header.date" class="smpl">Date-v</a> = HTTP-date
    26432664
    2644 GMT = %x47.4D.54
     2665<a href="#preferred.date.format" class="smpl">GMT</a> = %x47.4D.54
    26452666
    26462667<a href="#http.version" class="smpl">HTTP-Prot-Name</a> = %x48.54.54.50
    26472668<a href="#http.version" class="smpl">HTTP-Version</a> = HTTP-Prot-Name "/" 1*DIGIT "." 1*DIGIT
    2648 <a href="#full.date" class="smpl">HTTP-date</a> = rfc1123-date / obsolete-date
     2669<a href="#full.date" class="smpl">HTTP-date</a> = rfc1123-date / obs-date
    26492670<a href="#message.types" class="smpl">HTTP-message</a> = Request / Response
    26502671<a href="#header.host" class="smpl">Host</a> = "Host:" OWS Host-v
    26512672<a href="#header.host" class="smpl">Host-v</a> = uri-host [ ":" port ]
     
    26882709<a href="#abnf.dependencies" class="smpl">Warning</a> = &lt;Warning, defined in [Part6], Section 3.6&gt;
    26892710
    26902711<a href="#uri" class="smpl">absolute-URI</a> = &lt;absolute-URI, defined in [RFC3986], Section 4.3&gt;
    2691 <a href="#full.date" class="smpl">asctime-date</a> = wkday SP date3 SP time SP 4DIGIT
     2712<a href="#obsolete.date.formats" class="smpl">asctime-date</a> = day-name SP date3 SP time-of-day SP year
    26922713<a href="#rule.parameter" class="smpl">attribute</a> = token
    26932714<a href="#uri" class="smpl">authority</a> = &lt;authority, defined in [RFC3986], Section 3.2&gt;
    26942715
     
    27022723<a href="#header.connection" class="smpl">connection-token</a> = token
    27032724<a href="#rule.comment" class="smpl">ctext</a> = OWS / %x21-27 / %x2A-5B / %x5D-7E / obs-text
    27042725
    2705 <a href="#full.date" class="smpl">date1</a> = 2DIGIT SP month SP 4DIGIT
    2706 <a href="#full.date" class="smpl">date2</a> = 2DIGIT "-" month "-" 2DIGIT
    2707 <a href="#full.date" class="smpl">date3</a> = month SP ( 2DIGIT / ( SP DIGIT ) )
     2726<a href="#obsolete.date.formats" class="smpl">date1</a> = day SP month SP year
     2727<a href="#obsolete.date.formats" class="smpl">date2</a> = day "-" month "-" 2DIGIT
     2728<a href="#obsolete.date.formats" class="smpl">date3</a> = month SP ( 2DIGIT / ( SP DIGIT ) )
     2729<a href="#preferred.date.format" class="smpl">day</a> = 2DIGIT
     2730<a href="#preferred.date.format" class="smpl">day-name</a> = s-Mon / s-Tue / s-Wed / s-Thu / s-Fri / s-Sat / s-Sun
     2731<a href="#obsolete.date.formats" class="smpl">day-name-l</a> = l-Mon / l-Tue / l-Wed / l-Thu / l-Fri / l-Sat / l-Sun
    27082732
    27092733<a href="#abnf.dependencies" class="smpl">entity-body</a> = &lt;entity-body, defined in [Part3], Section 3.2&gt;
    27102734<a href="#abnf.dependencies" class="smpl">entity-header</a> = &lt;entity-header, defined in [Part3], Section 3.1&gt;
     
    27192743<a href="#message.types" class="smpl">generic-message</a> = start-line *( message-header CRLF ) CRLF [
    27202744 message-body ]
    27212745
     2746<a href="#preferred.date.format" class="smpl">hour</a> = 2DIGIT
    27222747<a href="#http.uri" class="smpl">http-URI</a> = "http://" authority path-abempty [ "?" query ]
    27232748
    27242749l-Fri = %x46.72.69.64.61.79
     
    27332758<a href="#message.body" class="smpl">message-body</a> = entity-body /
    27342759 &lt;entity-body encoded as per Transfer-Encoding&gt;
    27352760<a href="#message.headers" class="smpl">message-header</a> = field-name ":" OWS [ field-value ] OWS
    2736 <a href="#full.date" class="smpl">month</a> = s-Jan / s-Feb / s-Mar / s-Apr / s-May / s-Jun / s-Jul / s-Aug
     2761<a href="#preferred.date.format" class="smpl">minute</a> = 2DIGIT
     2762<a href="#preferred.date.format" class="smpl">month</a> = s-Jan / s-Feb / s-Mar / s-Apr / s-May / s-Jun / s-Jul / s-Aug
    27372763 / s-Sep / s-Oct / s-Nov / s-Dec
    27382764
     2765<a href="#obsolete.date.formats" class="smpl">obs-date</a> = rfc850-date / asctime-date
    27392766<a href="#rule.whitespace" class="smpl">obs-fold</a> = CRLF
    27402767<a href="#rule.quoted-string" class="smpl">obs-text</a> = %x80-FF
    2741 <a href="#full.date" class="smpl">obsolete-date</a> = rfc850-date / asctime-date
    27422768
    27432769<a href="#transfer.codings" class="smpl">parameter</a> = attribute BWS "=" BWS value
    27442770<a href="#uri" class="smpl">partial-URI</a> = relative-part [ "?" query ]
     
    27652791<a href="#request-target" class="smpl">request-target</a> = "*" / absolute-URI / ( path-absolute [ "?" query ] )
    27662792 / authority
    27672793<a href="#abnf.dependencies" class="smpl">response-header</a> = &lt;response-header, defined in [Part2], Section 5&gt;
    2768 <a href="#full.date" class="smpl">rfc1123-date</a> = wkday "," SP date1 SP time SP GMT
    2769 <a href="#full.date" class="smpl">rfc850-date</a> = weekday "," SP date2 SP time SP GMT
     2794<a href="#preferred.date.format" class="smpl">rfc1123-date</a> = day-name "," SP date1 SP time-of-day SP GMT
     2795<a href="#obsolete.date.formats" class="smpl">rfc850-date</a> = day-name-l "," SP date2 SP time-of-day SP GMT
    27702796
    27712797s-Apr = %x41.70.72
    27722798s-Aug = %x41.75.67
     
    27872813s-Thu = %x54.68.75
    27882814s-Tue = %x54.75.65
    27892815s-Wed = %x57.65.64
     2816<a href="#preferred.date.format" class="smpl">second</a> = 2DIGIT
    27902817<a href="#message.types" class="smpl">start-line</a> = Request-Line / Status-Line
    27912818
    27922819<a href="#header.te" class="smpl">t-codings</a> = "trailers" / ( transfer-extension [ te-params ] )
     
    27942821 "^" / "_" / "`" / "|" / "~" / DIGIT / ALPHA
    27952822<a href="#header.te" class="smpl">te-ext</a> = OWS ";" OWS token [ "=" ( token / quoted-string ) ]
    27962823<a href="#header.te" class="smpl">te-params</a> = OWS ";" OWS "q=" qvalue *te-ext
    2797 <a href="#full.date" class="smpl">time</a> = 2DIGIT ":" 2DIGIT ":" 2DIGIT
     2824<a href="#preferred.date.format" class="smpl">time-of-day</a> = hour ":" minute ":" second
    27982825<a href="#rule.token.separators" class="smpl">token</a> = 1*tchar
    27992826<a href="#chunked.transfer.encoding" class="smpl">trailer-part</a> = *( entity-header CRLF )
    28002827<a href="#transfer.codings" class="smpl">transfer-coding</a> = "chunked" / transfer-extension
     
    28042831
    28052832<a href="#rule.parameter" class="smpl">value</a> = token / quoted-string
    28062833
    2807 <a href="#full.date" class="smpl">weekday</a> = l-Mon / l-Tue / l-Wed / l-Thu / l-Fri / l-Sat / l-Sun
    2808 <a href="#full.date" class="smpl">wkday</a> = s-Mon / s-Tue / s-Wed / s-Thu / s-Fri / s-Sat / s-Sun
     2834<a href="#preferred.date.format" class="smpl">year</a> = 4DIGIT
    28092835
    28102836
    2811 </pre> <div id="rfc.figure.u.66"></div>
     2837</pre> <div id="rfc.figure.u.70"></div>
    28122838      <p>ABNF diagnostics:</p><pre class="inline">; Chunked-Body defined but not used
    28132839; Content-Length defined but not used
    28142840; HTTP-message defined but not used
     
    30333059               </ul>
    30343060            </li>
    30353061            <li class="indline0"><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul class="ind">
    3036                   <li class="indline1">gateway&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.110">C</a></li>
     3062                  <li class="indline1">gateway&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.116">C</a></li>
    30373063                  <li class="indline1"><tt>Grammar</tt>&nbsp;&nbsp;
    30383064                     <ul class="ind">
    30393065                        <li class="indline1"><tt>absolute-URI</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.24"><b>2.1</b></a></li>
    30403066                        <li class="indline1">ALPHA&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.1"><b>1.2</b></a></li>
    3041                         <li class="indline1"><tt>asctime-date</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.37"><b>3.2.1</b></a></li>
    3042                         <li class="indline1"><tt>attribute</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.48"><b>3.3</b></a></li>
     3067                        <li class="indline1"><tt>asctime-date</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.48"><b>3.2.1</b></a></li>
     3068                        <li class="indline1"><tt>attribute</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.52"><b>3.3</b></a></li>
    30433069                        <li class="indline1"><tt>authority</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.25"><b>2.1</b></a></li>
    30443070                        <li class="indline1"><tt>BWS</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.15"><b>1.2.2</b></a></li>
    3045                         <li class="indline1"><tt>chunk</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.51"><b>3.3.1</b></a></li>
    3046                         <li class="indline1"><tt>chunk-data</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.57"><b>3.3.1</b></a></li>
    3047                         <li class="indline1"><tt>chunk-ext</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.54"><b>3.3.1</b></a></li>
    3048                         <li class="indline1"><tt>chunk-ext-name</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.55"><b>3.3.1</b></a></li>
    3049                         <li class="indline1"><tt>chunk-ext-val</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.56"><b>3.3.1</b></a></li>
    3050                         <li class="indline1"><tt>chunk-size</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.52"><b>3.3.1</b></a></li>
    3051                         <li class="indline1"><tt>Chunked-Body</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.50"><b>3.3.1</b></a></li>
    3052                         <li class="indline1"><tt>comment</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.69"><b>4.2</b></a></li>
    3053                         <li class="indline1"><tt>Connection</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.83"><b>8.1</b></a></li>
    3054                         <li class="indline1"><tt>connection-token</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.85"><b>8.1</b></a></li>
    3055                         <li class="indline1"><tt>Connection-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.84"><b>8.1</b></a></li>
    3056                         <li class="indline1"><tt>Content-Length</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.86"><b>8.2</b></a></li>
    3057                         <li class="indline1"><tt>Content-Length-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.87"><b>8.2</b></a></li>
     3071                        <li class="indline1"><tt>chunk</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.57"><b>3.3.1</b></a></li>
     3072                        <li class="indline1"><tt>chunk-data</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.63"><b>3.3.1</b></a></li>
     3073                        <li class="indline1"><tt>chunk-ext</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.60"><b>3.3.1</b></a></li>
     3074                        <li class="indline1"><tt>chunk-ext-name</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.61"><b>3.3.1</b></a></li>
     3075                        <li class="indline1"><tt>chunk-ext-val</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.62"><b>3.3.1</b></a></li>
     3076                        <li class="indline1"><tt>chunk-size</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.58"><b>3.3.1</b></a></li>
     3077                        <li class="indline1"><tt>Chunked-Body</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.56"><b>3.3.1</b></a></li>
     3078                        <li class="indline1"><tt>comment</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.75"><b>4.2</b></a></li>
     3079                        <li class="indline1"><tt>Connection</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.89"><b>8.1</b></a></li>
     3080                        <li class="indline1"><tt>connection-token</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.91"><b>8.1</b></a></li>
     3081                        <li class="indline1"><tt>Connection-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.90"><b>8.1</b></a></li>
     3082                        <li class="indline1"><tt>Content-Length</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.92"><b>8.2</b></a></li>
     3083                        <li class="indline1"><tt>Content-Length-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.93"><b>8.2</b></a></li>
    30583084                        <li class="indline1">CR&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.2"><b>1.2</b></a></li>
    30593085                        <li class="indline1">CRLF&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.3"><b>1.2</b></a></li>
    3060                         <li class="indline1"><tt>ctext</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.70"><b>4.2</b></a></li>
     3086                        <li class="indline1"><tt>ctext</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.76"><b>4.2</b></a></li>
    30613087                        <li class="indline1">CTL&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.4"><b>1.2</b></a></li>
    3062                         <li class="indline1"><tt>Date</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.88"><b>8.3</b></a></li>
    3063                         <li class="indline1"><tt>Date-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.89"><b>8.3</b></a></li>
    3064                         <li class="indline1"><tt>date1</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.38"><b>3.2.1</b></a></li>
    3065                         <li class="indline1"><tt>date2</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.39"><b>3.2.1</b></a></li>
    3066                         <li class="indline1"><tt>date3</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.40"><b>3.2.1</b></a></li>
     3088                        <li class="indline1"><tt>Date</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.94"><b>8.3</b></a></li>
     3089                        <li class="indline1"><tt>Date-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.95"><b>8.3</b></a></li>
     3090                        <li class="indline1"><tt>date1</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.35"><b>3.2.1</b></a></li>
     3091                        <li class="indline1"><tt>date2</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.54"><b>3.3</b></a></li>
     3092                        <li class="indline1"><tt>date3</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.55"><b>3.3</b></a></li>
     3093                        <li class="indline1"><tt>day</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.42"><b>3.2.1</b></a></li>
     3094                        <li class="indline1"><tt>day-name</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.40"><b>3.2.1</b></a></li>
     3095                        <li class="indline1"><tt>day-name-l</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.41"><b>3.2.1</b></a></li>
    30673096                        <li class="indline1">DIGIT&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.5"><b>1.2</b></a></li>
    30683097                        <li class="indline1">DQUOTE&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.6"><b>1.2</b></a></li>
    3069                         <li class="indline1"><tt>extension-code</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.81"><b>6.1.1</b></a></li>
    3070                         <li class="indline1"><tt>extension-method</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.76"><b>5.1.1</b></a></li>
    3071                         <li class="indline1"><tt>field-content</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.68"><b>4.2</b></a></li>
    3072                         <li class="indline1"><tt>field-name</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.66"><b>4.2</b></a></li>
    3073                         <li class="indline1"><tt>field-value</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.67"><b>4.2</b></a></li>
    3074                         <li class="indline1"><tt>general-header</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.72"><b>4.5</b></a></li>
    3075                         <li class="indline1"><tt>generic-message</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.63"><b>4.1</b></a></li>
     3098                        <li class="indline1"><tt>extension-code</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.87"><b>6.1.1</b></a></li>
     3099                        <li class="indline1"><tt>extension-method</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.82"><b>5.1.1</b></a></li>
     3100                        <li class="indline1"><tt>field-content</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.74"><b>4.2</b></a></li>
     3101                        <li class="indline1"><tt>field-name</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.72"><b>4.2</b></a></li>
     3102                        <li class="indline1"><tt>field-value</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.73"><b>4.2</b></a></li>
     3103                        <li class="indline1"><tt>general-header</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.78"><b>4.5</b></a></li>
     3104                        <li class="indline1"><tt>generic-message</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.69"><b>4.1</b></a></li>
     3105                        <li class="indline1"><tt>GMT</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.45"><b>3.2.1</b></a></li>
    30763106                        <li class="indline1">HEXDIG&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.7"><b>1.2</b></a></li>
    3077                         <li class="indline1"><tt>Host</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.90"><b>8.4</b></a></li>
    3078                         <li class="indline1"><tt>Host-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.91"><b>8.4</b></a></li>
     3107                        <li class="indline1"><tt>Host</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.96"><b>8.4</b></a></li>
     3108                        <li class="indline1"><tt>Host-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.97"><b>8.4</b></a></li>
     3109                        <li class="indline1"><tt>hour</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.37"><b>3.2.1</b></a></li>
    30793110                        <li class="indline1"><tt>HTTP-date</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.33"><b>3.2.1</b></a></li>
    3080                         <li class="indline1"><tt>HTTP-message</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.62"><b>4.1</b></a></li>
     3111                        <li class="indline1"><tt>HTTP-message</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.68"><b>4.1</b></a></li>
    30813112                        <li class="indline1"><tt>HTTP-Prot-Name</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.32"><b>3.1</b></a></li>
    30823113                        <li class="indline1"><tt>http-URI</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.30"><b>2.1.1</b></a></li>
    30833114                        <li class="indline1"><tt>HTTP-Version</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.31"><b>3.1</b></a></li>
    3084                         <li class="indline1"><tt>last-chunk</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.53"><b>3.3.1</b></a></li>
     3115                        <li class="indline1"><tt>last-chunk</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.59"><b>3.3.1</b></a></li>
    30853116                        <li class="indline1">LF&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.8"><b>1.2</b></a></li>
    3086                         <li class="indline1"><tt>message-body</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.71"><b>4.3</b></a></li>
    3087                         <li class="indline1"><tt>message-header</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.65"><b>4.2</b></a></li>
    3088                         <li class="indline1"><tt>Method</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.75"><b>5.1.1</b></a></li>
    3089                         <li class="indline1"><tt>month</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.44"><b>3.2.1</b></a></li>
     3117                        <li class="indline1"><tt>message-body</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.77"><b>4.3</b></a></li>
     3118                        <li class="indline1"><tt>message-header</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.71"><b>4.2</b></a></li>
     3119                        <li class="indline1"><tt>Method</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.81"><b>5.1.1</b></a></li>
     3120                        <li class="indline1"><tt>minute</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.38"><b>3.2.1</b></a></li>
     3121                        <li class="indline1"><tt>month</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.43"><b>3.2.1</b></a></li>
     3122                        <li class="indline1"><tt>obs-date</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.46"><b>3.2.1</b></a></li>
    30903123                        <li class="indline1"><tt>obs-text</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.20"><b>1.2.2</b></a></li>
    3091                         <li class="indline1"><tt>obsolete-date</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.35"><b>3.2.1</b></a></li>
    30923124                        <li class="indline1">OCTET&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.9"><b>1.2</b></a></li>
    30933125                        <li class="indline1"><tt>OWS</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.13"><b>1.2.2</b></a></li>
    3094                         <li class="indline1"><tt>parameter</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.47"><b>3.3</b></a></li>
     3126                        <li class="indline1"><tt>parameter</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.51"><b>3.3</b></a></li>
    30953127                        <li class="indline1"><tt>path-absolute</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.26"><b>2.1</b></a></li>
    30963128                        <li class="indline1"><tt>port</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.27"><b>2.1</b></a></li>
    3097                         <li class="indline1"><tt>product</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.59"><b>3.4</b></a></li>
    3098                         <li class="indline1"><tt>product-version</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.60"><b>3.4</b></a></li>
    3099                         <li class="indline1"><tt>protocol-name</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.106"><b>8.9</b></a></li>
    3100                         <li class="indline1"><tt>protocol-version</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.107"><b>8.9</b></a></li>
    3101                         <li class="indline1"><tt>pseudonym</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.109"><b>8.9</b></a></li>
     3129                        <li class="indline1"><tt>product</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.65"><b>3.4</b></a></li>
     3130                        <li class="indline1"><tt>product-version</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.66"><b>3.4</b></a></li>
     3131                        <li class="indline1"><tt>protocol-name</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.112"><b>8.9</b></a></li>
     3132                        <li class="indline1"><tt>protocol-version</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.113"><b>8.9</b></a></li>
     3133                        <li class="indline1"><tt>pseudonym</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.115"><b>8.9</b></a></li>
    31023134                        <li class="indline1"><tt>qdtext</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.19"><b>1.2.2</b></a></li>
    31033135                        <li class="indline1"><tt>query</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.28"><b>2.1</b></a></li>
    31043136                        <li class="indline1"><tt>quoted-pair</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.22"><b>1.2.2</b></a></li>
    31053137                        <li class="indline1"><tt>quoted-string</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.18"><b>1.2.2</b></a></li>
    31063138                        <li class="indline1"><tt>quoted-text</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.21"><b>1.2.2</b></a></li>
    3107                         <li class="indline1"><tt>qvalue</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.61"><b>3.5</b></a></li>
    3108                         <li class="indline1"><tt>Reason-Phrase</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.82"><b>6.1.1</b></a></li>
    3109                         <li class="indline1"><tt>received-by</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.108"><b>8.9</b></a></li>
    3110                         <li class="indline1"><tt>received-protocol</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.105"><b>8.9</b></a></li>
    3111                         <li class="indline1"><tt>Request</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.73"><b>5</b></a></li>
    3112                         <li class="indline1"><tt>Request-Line</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.74"><b>5.1</b></a></li>
    3113                         <li class="indline1"><tt>request-target</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.77"><b>5.1.2</b></a></li>
    3114                         <li class="indline1"><tt>Response</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.78"><b>6</b></a></li>
     3139                        <li class="indline1"><tt>qvalue</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.67"><b>3.5</b></a></li>
     3140                        <li class="indline1"><tt>Reason-Phrase</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.88"><b>6.1.1</b></a></li>
     3141                        <li class="indline1"><tt>received-by</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.114"><b>8.9</b></a></li>
     3142                        <li class="indline1"><tt>received-protocol</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.111"><b>8.9</b></a></li>
     3143                        <li class="indline1"><tt>Request</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.79"><b>5</b></a></li>
     3144                        <li class="indline1"><tt>Request-Line</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.80"><b>5.1</b></a></li>
     3145                        <li class="indline1"><tt>request-target</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.83"><b>5.1.2</b></a></li>
     3146                        <li class="indline1"><tt>Response</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.84"><b>6</b></a></li>
    31153147                        <li class="indline1"><tt>rfc1123-date</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.34"><b>3.2.1</b></a></li>
    3116                         <li class="indline1"><tt>rfc850-date</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.36"><b>3.2.1</b></a></li>
     3148                        <li class="indline1"><tt>rfc850-date</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.47"><b>3.2.1</b></a></li>
    31173149                        <li class="indline1"><tt>RWS</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.14"><b>1.2.2</b></a></li>
     3150                        <li class="indline1"><tt>second</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.39"><b>3.2.1</b></a></li>
    31183151                        <li class="indline1">SP&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.10"><b>1.2</b></a></li>
    3119                         <li class="indline1"><tt>start-line</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.64"><b>4.1</b></a></li>
    3120                         <li class="indline1"><tt>Status-Code</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.80"><b>6.1.1</b></a></li>
    3121                         <li class="indline1"><tt>Status-Line</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.79"><b>6.1</b></a></li>
    3122                         <li class="indline1"><tt>t-codings</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.94"><b>8.5</b></a></li>
     3152                        <li class="indline1"><tt>start-line</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.70"><b>4.1</b></a></li>
     3153                        <li class="indline1"><tt>Status-Code</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.86"><b>6.1.1</b></a></li>
     3154                        <li class="indline1"><tt>Status-Line</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.85"><b>6.1</b></a></li>
     3155                        <li class="indline1"><tt>t-codings</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.100"><b>8.5</b></a></li>
    31233156                        <li class="indline1"><tt>tchar</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.17"><b>1.2.2</b></a></li>
    3124                         <li class="indline1"><tt>TE</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.92"><b>8.5</b></a></li>
    3125                         <li class="indline1"><tt>te-ext</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.96"><b>8.5</b></a></li>
    3126                         <li class="indline1"><tt>te-params</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.95"><b>8.5</b></a></li>
    3127                         <li class="indline1"><tt>TE-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.93"><b>8.5</b></a></li>
    3128                         <li class="indline1"><tt>time</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.41"><b>3.2.1</b></a></li>
     3157                        <li class="indline1"><tt>TE</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.98"><b>8.5</b></a></li>
     3158                        <li class="indline1"><tt>te-ext</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.102"><b>8.5</b></a></li>
     3159                        <li class="indline1"><tt>te-params</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.101"><b>8.5</b></a></li>
     3160                        <li class="indline1"><tt>TE-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.99"><b>8.5</b></a></li>
     3161                        <li class="indline1"><tt>time-of-day</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.36"><b>3.2.1</b></a></li>
    31293162                        <li class="indline1"><tt>token</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.16"><b>1.2.2</b></a></li>
    3130                         <li class="indline1"><tt>Trailer</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.97"><b>8.6</b></a></li>
    3131                         <li class="indline1"><tt>trailer-part</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.58"><b>3.3.1</b></a></li>
    3132                         <li class="indline1"><tt>Trailer-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.98"><b>8.6</b></a></li>
    3133                         <li class="indline1"><tt>transfer-coding</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.45"><b>3.3</b></a></li>
    3134                         <li class="indline1"><tt>Transfer-Encoding</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.99"><b>8.7</b></a></li>
    3135                         <li class="indline1"><tt>Transfer-Encoding-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.100"><b>8.7</b></a></li>
    3136                         <li class="indline1"><tt>transfer-extension</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.46"><b>3.3</b></a></li>
    3137                         <li class="indline1"><tt>Upgrade</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.101"><b>8.8</b></a></li>
    3138                         <li class="indline1"><tt>Upgrade-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.102"><b>8.8</b></a></li>
     3163                        <li class="indline1"><tt>Trailer</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.103"><b>8.6</b></a></li>
     3164                        <li class="indline1"><tt>trailer-part</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.64"><b>3.3.1</b></a></li>
     3165                        <li class="indline1"><tt>Trailer-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.104"><b>8.6</b></a></li>
     3166                        <li class="indline1"><tt>transfer-coding</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.49"><b>3.3</b></a></li>
     3167                        <li class="indline1"><tt>Transfer-Encoding</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.105"><b>8.7</b></a></li>
     3168                        <li class="indline1"><tt>Transfer-Encoding-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.106"><b>8.7</b></a></li>
     3169                        <li class="indline1"><tt>transfer-extension</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.50"><b>3.3</b></a></li>
     3170                        <li class="indline1"><tt>Upgrade</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.107"><b>8.8</b></a></li>
     3171                        <li class="indline1"><tt>Upgrade-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.108"><b>8.8</b></a></li>
    31393172                        <li class="indline1"><tt>uri-host</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.29"><b>2.1</b></a></li>
    31403173                        <li class="indline1"><tt>URI-reference</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.23"><b>2.1</b></a></li>
    3141                         <li class="indline1"><tt>value</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.49"><b>3.3</b></a></li>
     3174                        <li class="indline1"><tt>value</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.53"><b>3.3</b></a></li>
    31423175                        <li class="indline1">VCHAR&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.11"><b>1.2</b></a></li>
    3143                         <li class="indline1"><tt>Via</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.103"><b>8.9</b></a></li>
    3144                         <li class="indline1"><tt>Via-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.104"><b>8.9</b></a></li>
    3145                         <li class="indline1"><tt>weekday</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.43"><b>3.2.1</b></a></li>
    3146                         <li class="indline1"><tt>wkday</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.42"><b>3.2.1</b></a></li>
     3176                        <li class="indline1"><tt>Via</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.109"><b>8.9</b></a></li>
     3177                        <li class="indline1"><tt>Via-v</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.110"><b>8.9</b></a></li>
    31473178                        <li class="indline1">WSP&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.12"><b>1.2</b></a></li>
     3179                        <li class="indline1"><tt>year</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.44"><b>3.2.1</b></a></li>
    31483180                     </ul>
    31493181                  </li>
    31503182               </ul>
     
    32753307                        <li class="indline1"><em>Appendix B.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5234.2">1.2</a></li>
    32763308                     </ul>
    32773309                  </li>
    3278                   <li class="indline1"><em>RFC5322</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5322.1">1</a>, <a class="iref" href="#rfc.xref.RFC5322.2">4.1</a>, <a class="iref" href="#rfc.xref.RFC5322.3">4.2</a>, <a class="iref" href="#rfc.xref.RFC5322.4">8.3</a>, <a class="iref" href="#rfc.xref.RFC5322.5">8.9</a>, <a class="iref" href="#RFC5322"><b>12.2</b></a><ul class="ind">
    3279                         <li class="indline1"><em>Section 2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5322.3">4.2</a></li>
    3280                         <li class="indline1"><em>Section 3.6.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5322.4">8.3</a></li>
    3281                         <li class="indline1"><em>Section 3.6.7</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5322.5">8.9</a></li>
     3310                  <li class="indline1"><em>RFC5322</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5322.1">1</a>, <a class="iref" href="#rfc.xref.RFC5322.2">3.2.1</a>, <a class="iref" href="#rfc.xref.RFC5322.3">4.1</a>, <a class="iref" href="#rfc.xref.RFC5322.4">4.2</a>, <a class="iref" href="#rfc.xref.RFC5322.5">8.3</a>, <a class="iref" href="#rfc.xref.RFC5322.6">8.9</a>, <a class="iref" href="#RFC5322"><b>12.2</b></a><ul class="ind">
     3311                        <li class="indline1"><em>Section 2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5322.4">4.2</a></li>
     3312                        <li class="indline1"><em>Section 3.6.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5322.5">8.3</a></li>
     3313                        <li class="indline1"><em>Section 3.6.7</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5322.6">8.9</a></li>
     3314                        <li class="indline1"><em>Section 3.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5322.2">3.2.1</a></li>
    32823315                     </ul>
    32833316                  </li>
    32843317               </ul>