Changeset 580
- Timestamp:
- 10/05/09 10:42:16 (13 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 12 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r578 r580 471 471 <tr> 472 472 <td class="header left"></td> 473 <td class="header right">May 8, 2009</td>473 <td class="header right">May 10, 2009</td> 474 474 </tr> 475 475 </table> … … 545 545 <li class="tocline0">3. <a href="#protocol.parameters">Protocol Parameters</a><ul class="toc"> 546 546 <li class="tocline1">3.1 <a href="#http.version">HTTP Version</a></li> 547 <li class="tocline1">3.2 <a href="#date.time.formats">Date/Time Formats</a><ul class="toc"> 548 <li class="tocline1">3.2.1 <a href="#full.date">Full Date</a></li> 549 </ul> 550 </li> 547 <li class="tocline1">3.2 <a href="#date.time.formats.full.date">Date/Time Formats: Full Date</a></li> 551 548 <li class="tocline1">3.3 <a href="#transfer.codings">Transfer Codings</a><ul class="toc"> 552 549 <li class="tocline1">3.3.1 <a href="#chunked.transfer.encoding">Chunked Transfer Coding</a></li> … … 970 967 </p> 971 968 </div> 972 <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a> <a id="date.time.formats" href="#date.time.formats">Date/Time Formats</a></h2> 973 <h3 id="rfc.section.3.2.1"><a href="#rfc.section.3.2.1">3.2.1</a> <a id="full.date" href="#full.date">Full Date</a></h3> 974 <p id="rfc.section.3.2.1.p.1">HTTP applications have historically allowed three different formats for the representation of date/time stamps:</p> 969 <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a> <a id="date.time.formats.full.date" href="#date.time.formats.full.date">Date/Time Formats: Full Date</a></h2> 970 <p id="rfc.section.3.2.p.1">HTTP applications have historically allowed three different formats for the representation of date/time stamps:</p> 975 971 <div id="rfc.figure.u.19"></div><pre class="text"> Sun, 06 Nov 1994 08:49:37 GMT ; RFC 1123 976 972 Sunday, 06-Nov-94 08:49:37 GMT ; obsolete RFC 850 format 977 973 Sun Nov 6 08:49:37 1994 ; ANSI C's asctime() format 978 </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 servers974 </pre><p id="rfc.section.3.2.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 979 975 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 A</a> for further information. 980 976 </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 977 <p id="rfc.section.3.2.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 987 978 Universal Time). This is indicated in the first two formats by the inclusion of "GMT" as the three-letter abbreviation for 988 979 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. 989 980 </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 981 <div id="rfc.figure.u.20"></div><pre class="inline"><span id="rfc.iref.g.33"></span> <a href="#date.time.formats.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> 982 </pre><div id="preferred.date.format"> 983 <p id="rfc.section.3.2.p.6"> Preferred format:</p> 984 </div> 985 <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> 986 987 <a href="#preferred.date.format" class="smpl">day-name</a> = s-Mon / s-Tue / s-Wed 1004 988 / s-Thu / s-Fri / s-Sat / s-Sun 1005 <a href="#full.date" class="smpl">weekday</a> = l-Mon / l-Tue / l-Wed1006 / l-Thu / l-Fri / l-Sat / l-Sun1007 <a href="#full.date" class="smpl">month</a> = s-Jan / s-Feb / s-Mar / s-Apr1008 / s-May / s-Jun / s-Jul / s-Aug1009 / s-Sep / s-Oct / s-Nov / s-Dec1010 989 1011 GMT = %x47.4D.54 ; "GMT", case-sensitive1012 1013 990 s-Mon = %x4D.6F.6E ; "Mon", case-sensitive 1014 991 s-Tue = %x54.75.65 ; "Tue", case-sensitive … … 1019 996 s-Sun = %x53.75.6E ; "Sun", case-sensitive 1020 997 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 998 <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> 999 ; e.g., 02 Jun 1982 1000 1001 <a href="#preferred.date.format" class="smpl">day</a> = 2<a href="#core.rules" class="smpl">DIGIT</a> 1002 <a href="#preferred.date.format" class="smpl">month</a> = s-Jan / s-Feb / s-Mar / s-Apr 1003 / s-May / s-Jun / s-Jul / s-Aug 1004 / s-Sep / s-Oct / s-Nov / s-Dec 1005 <a href="#preferred.date.format" class="smpl">year</a> = 4<a href="#core.rules" class="smpl">DIGIT</a> 1028 1006 1029 1007 s-Jan = %x4A.61.6E ; "Jan", case-sensitive … … 1039 1017 s-Nov = %x4E.6F.76 ; "Nov", case-sensitive 1040 1018 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. 1043 </p> 1019 1020 <a href="#preferred.date.format" class="smpl">GMT</a> = %x47.4D.54 ; "GMT", case-sensitive 1021 1022 <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> 1023 ; 00:00:00 - 23:59:59 1024 1025 <a href="#preferred.date.format" class="smpl">hour</a> = 2<a href="#core.rules" class="smpl">DIGIT</a> 1026 <a href="#preferred.date.format" class="smpl">minute</a> = 2<a href="#core.rules" class="smpl">DIGIT</a> 1027 <a href="#preferred.date.format" class="smpl">second</a> = 2<a href="#core.rules" class="smpl">DIGIT</a> 1028 </pre><p id="rfc.section.3.2.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>). 1029 </p> 1030 <div id="obsolete.date.formats"> 1031 <p id="rfc.section.3.2.p.9"> Obsolete formats:</p> 1032 </div> 1033 <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> 1034 </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> 1035 <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> 1036 ; day-month-year (e.g., 02-Jun-82) 1037 1038 <a href="#obsolete.date.formats" class="smpl">day-name-l</a> = l-Mon / l-Tue / l-Wed 1039 / l-Thu / l-Fri / l-Sat / l-Sun 1040 1041 l-Mon = %x4D.6F.6E.64.61.79 ; "Monday", case-sensitive 1042 l-Tue = %x54.75.65.73.64.61.79 ; "Tuesday", case-sensitive 1043 l-Wed = %x57.65.64.6E.65.73.64.61.79 ; "Wednesday", case-sensitive 1044 l-Thu = %x54.68.75.72.73.64.61.79 ; "Thursday", case-sensitive 1045 l-Fri = %x46.72.69.64.61.79 ; "Friday", case-sensitive 1046 l-Sat = %x53.61.74.75.72.64.61.79 ; "Saturday", case-sensitive 1047 l-Sun = %x53.75.6E.64.61.79 ; "Sunday", case-sensitive 1048 </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> 1049 <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> )) 1050 ; month day (e.g., Jun 2) 1051 </pre><div class="note"> 1052 <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, 1053 as is sometimes the case when retrieving or posting messages via proxies/gateways to SMTP or NNTP. 1054 </p> 1055 </div> 1056 <div class="note"> 1057 <p> <b>Note:</b> HTTP requirements for the date/time stamp format apply only to their usage within the protocol stream. Clients and servers 1058 are not required to use these formats for user presentation, request logging, etc. 1059 </p> 1060 </div> 1044 1061 <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a> <a id="transfer.codings" href="#transfer.codings">Transfer Codings</a></h2> 1045 1062 <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 … … 1047 1064 is a property of the message, not of the original entity. 1048 1065 </p> 1049 <div id="rfc.figure.u.2 1"></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>1066 <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> 1050 1067 <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> ) 1051 1068 </pre><div id="rule.parameter"> 1052 1069 <p id="rfc.section.3.3.p.3"> Parameters are in the form of attribute/value pairs.</p> 1053 1070 </div> 1054 <div id="rfc.figure.u.2 2"></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>1071 <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> 1055 1072 <a href="#rule.parameter" class="smpl">attribute</a> = <a href="#rule.token.separators" class="smpl">token</a> 1056 1073 <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> … … 1077 1094 necessary for the recipient to verify that it has received the full message. 1078 1095 </p> 1079 <div id="rfc.figure.u.2 3"></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>1096 <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> 1080 1097 <a href="#chunked.transfer.encoding" class="smpl">last-chunk</a> 1081 1098 <a href="#chunked.transfer.encoding" class="smpl">trailer-part</a> … … 1115 1132 </p> 1116 1133 <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.2 4"></div><pre class="text"> length := 01134 <div id="rfc.figure.u.28"></div><pre class="text"> length := 0 1118 1135 read chunk-size, chunk-ext (if any) and CRLF 1119 1136 while (chunk-size > 0) { … … 1137 1154 By convention, the products are listed in order of their significance for identifying the application. 1138 1155 </p> 1139 <div id="rfc.figure.u.2 5"></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>]1156 <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>] 1140 1157 <a href="#product.tokens" class="smpl">product-version</a> = <a href="#rule.token.separators" class="smpl">token</a> 1141 1158 </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.17b31159 <div id="rfc.figure.u.30"></div><pre class="text"> User-Agent: CERN-LineMode/2.15 libwww/2.17b3 1143 1160 Server: Apache/0.8.4 1144 1161 </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). … … 1149 1166 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. 1150 1167 </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> ] )1168 <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> ] ) 1152 1169 / ( "1" [ "." 0*3("0") ] ) 1153 1170 </pre><div class="note"> … … 1158 1175 <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a> <a id="message.types" href="#message.types">Message Types</a></h2> 1159 1176 <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 messages1161 </pre><p id="rfc.section.4.1.p.3">Request (<a href="#request" title="Request">Section 5</a>) and Response (<a href="#response" title="Response">Section 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 header1177 <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 1178 </pre><p id="rfc.section.4.1.p.3">Request (<a href="#request" title="Request">Section 5</a>) and Response (<a href="#response" title="Response">Section 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 1162 1179 fields (also known as "headers"), an empty line (i.e., a line with nothing preceding the CRLF) indicating the end of the header 1163 1180 fields, and possibly a message-body. 1164 1181 </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>1182 <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> 1166 1183 *( <a href="#message.headers" class="smpl">message-header</a> <a href="#core.rules" class="smpl">CRLF</a> ) 1167 1184 <a href="#core.rules" class="smpl">CRLF</a> … … 1179 1196 </p> 1180 1197 <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a> <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 are1198 <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 1182 1199 case-insensitive. 1183 1200 </p> 1184 <div id="rfc.figure.u.3 0"></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> ] OWS1201 <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 1185 1202 <a href="#message.headers" class="smpl">field-name</a> = <a href="#rule.token.separators" class="smpl">token</a> 1186 1203 <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> ) … … 1207 1224 </p> 1208 1225 </div> 1209 <div id="rfc.figure.u.3 1"></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> ) ")"1226 <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> ) ")" 1210 1227 <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> 1211 1228 ; <a href="#rule.whitespace" class="smpl">OWS</a> / <<a href="#core.rules" class="smpl">VCHAR</a> except "(", ")", and "\"> / <a href="#rule.quoted-string" class="smpl">obs-text</a> … … 1230 1247 header field (<a href="#header.transfer-encoding" id="rfc.xref.header.transfer-encoding.2" title="Transfer-Encoding">Section 8.7</a>). 1231 1248 </p> 1232 <div id="rfc.figure.u.3 2"></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>1249 <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> 1233 1250 / <entity-body encoded as per <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding</a>> 1234 1251 </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 … … 1297 1314 to the entity being transferred. These header fields apply only to the message being transmitted. 1298 1315 </p> 1299 <div id="rfc.figure.u.3 3"></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>1316 <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> 1300 1317 / <a href="#header.connection" class="smpl">Connection</a> ; <a href="#header.connection" id="rfc.xref.header.connection.1" title="Connection">Section 8.1</a> 1301 1318 / <a href="#header.date" class="smpl">Date</a> ; <a href="#header.date" id="rfc.xref.header.date.1" title="Date">Section 8.3</a> … … 1314 1331 resource, the identifier of the resource, and the protocol version in use. 1315 1332 </p> 1316 <div id="rfc.figure.u.3 4"></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 5.1</a>1333 <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 5.1</a> 1317 1334 *(( <a href="#general.header.fields" class="smpl">general-header</a> ; <a href="#general.header.fields" title="General Header Fields">Section 4.5</a> 1318 1335 / <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> … … 1324 1341 The elements are separated by SP characters. No CR or LF is allowed except in the final CRLF sequence. 1325 1342 </p> 1326 <div id="rfc.figure.u.3 5"></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>1343 <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> 1327 1344 </pre><h3 id="rfc.section.5.1.1"><a href="#rfc.section.5.1.1">5.1.1</a> <a id="method" href="#method">Method</a></h3> 1328 1345 <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>1346 <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> 1330 1347 </pre><h3 id="rfc.section.5.1.2"><a href="#rfc.section.5.1.2">5.1.2</a> <a id="request-target" href="#request-target">request-target</a></h3> 1331 1348 <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> = "*"1349 <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> = "*" 1333 1350 / <a href="#uri" class="smpl">absolute-URI</a> 1334 1351 / ( <a href="#uri" class="smpl">path-absolute</a> [ "?" <a href="#uri" class="smpl">query</a> ] ) … … 1338 1355 apply to a resource. One example would be 1339 1356 </p> 1340 <div id="rfc.figure.u. 38"></div><pre class="text"> OPTIONS * HTTP/1.11357 <div id="rfc.figure.u.42"></div><pre class="text"> OPTIONS * HTTP/1.1 1341 1358 </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, 1342 1359 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 … … 1344 1361 Request-Line would be: 1345 1362 </p> 1346 <div id="rfc.figure.u. 39"></div><pre class="text"> GET http://www.example.org/pub/WWW/TheProject.html HTTP/1.11363 <div id="rfc.figure.u.43"></div><pre class="text"> GET http://www.example.org/pub/WWW/TheProject.html HTTP/1.1 1347 1364 </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. 1348 1365 </p> … … 1353 1370 server would create a TCP connection to port 80 of the host "www.example.org" and send the lines: 1354 1371 </p> 1355 <div id="rfc.figure.u.4 0"></div><pre class="text"> GET /pub/WWW/TheProject.html HTTP/1.11372 <div id="rfc.figure.u.44"></div><pre class="text"> GET /pub/WWW/TheProject.html HTTP/1.1 1356 1373 Host: www.example.org 1357 1374 </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 … … 1361 1378 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. 1362 1379 </p> 1363 <div id="rfc.figure.u.4 1"></div>1380 <div id="rfc.figure.u.45"></div> 1364 1381 <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.4 2"></div>1382 </pre><div id="rfc.figure.u.46"></div> 1366 1383 <p>would be forwarded by the proxy as</p><pre class="text"> OPTIONS * HTTP/1.1 1367 1384 Host: www.example.org:8001 … … 1406 1423 <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a> <a id="response" href="#response">Response</a></h1> 1407 1424 <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.4 3"></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 6.1</a>1425 <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 6.1</a> 1409 1426 *(( <a href="#general.header.fields" class="smpl">general-header</a> ; <a href="#general.header.fields" title="General Header Fields">Section 4.5</a> 1410 1427 / <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> … … 1417 1434 CRLF sequence. 1418 1435 </p> 1419 <div id="rfc.figure.u.4 4"></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>1436 <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> 1420 1437 </pre><h3 id="rfc.section.6.1.1"><a href="#rfc.section.6.1.1">6.1.1</a> <a id="status.code.and.reason.phrase" href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a></h3> 1421 1438 <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 … … 1434 1451 <li>5xx: Server Error - The server failed to fulfill an apparently valid request</li> 1435 1452 </ul> 1436 <div id="rfc.figure.u.4 5"></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>1453 <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> 1437 1454 <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> ) 1438 1455 </pre><h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a> <a id="connections" href="#connections">Connections</a></h1> … … 1626 1643 </p> 1627 1644 <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>1645 <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> 1629 1646 <a href="#header.connection" class="smpl">Connection-v</a> = 1#<a href="#header.connection" class="smpl">connection-token</a> 1630 1647 <a href="#header.connection" class="smpl">connection-token</a> = <a href="#rule.token.separators" class="smpl">token</a> … … 1639 1656 of the response. For example, 1640 1657 </p> 1641 <div id="rfc.figure.u. 47"></div><pre class="text"> Connection: close1658 <div id="rfc.figure.u.51"></div><pre class="text"> Connection: close 1642 1659 </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 7.1</a>) after the current request/response is complete. 1643 1660 </p> … … 1655 1672 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. 1656 1673 </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>1674 <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> 1658 1675 <a href="#header.content-length" class="smpl">Content-Length-v</a> = 1*<a href="#core.rules" class="smpl">DIGIT</a> 1659 1676 </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: 34951677 <div id="rfc.figure.u.53"></div><pre class="text"> Content-Length: 3495 1661 1678 </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 4.4</a>. 1662 1679 </p> … … 1671 1688 <h2 id="rfc.section.8.3"><a href="#rfc.section.8.3">8.3</a> <a id="header.date" href="#header.date">Date</a></h2> 1672 1689 <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 3.2.1</a>; it <em class="bcp14">MUST</em> be sent in rfc1123-date format.1674 </p> 1675 <div id="rfc.figure.u.5 0"></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>1676 <a href="#header.date" class="smpl">Date-v</a> = <a href="# full.date" class="smpl">HTTP-date</a>1690 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="#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 3.2</a>; it <em class="bcp14">MUST</em> be sent in rfc1123-date format. 1691 </p> 1692 <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> 1693 <a href="#header.date" class="smpl">Date-v</a> = <a href="#date.time.formats.full.date" class="smpl">HTTP-date</a> 1677 1694 </pre><p id="rfc.section.8.3.p.3">An example is</p> 1678 <div id="rfc.figure.u.5 1"></div><pre class="text"> Date: Tue, 15 Nov 1994 08:12:31 GMT1695 <div id="rfc.figure.u.55"></div><pre class="text"> Date: Tue, 15 Nov 1994 08:12:31 GMT 1679 1696 </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: 1680 1697 </p> … … 1712 1729 a single IP address. 1713 1730 </p> 1714 <div id="rfc.figure.u.5 2"></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>1731 <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> 1715 1732 <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 2.1.1</a> 1716 1733 </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 1717 1734 URL). For example, a request on the origin server for <http://www.example.org/pub/WWW/> would properly include: 1718 1735 </p> 1719 <div id="rfc.figure.u.5 3"></div><pre class="text"> GET /pub/WWW/ HTTP/1.11736 <div id="rfc.figure.u.57"></div><pre class="text"> GET /pub/WWW/ HTTP/1.1 1720 1737 Host: www.example.org 1721 1738 </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 … … 1732 1749 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 3.3</a>). 1733 1750 </p> 1734 <div id="rfc.figure.u.5 4"></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>1751 <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> 1735 1752 <a href="#header.te" class="smpl">TE-v</a> = #<a href="#header.te" class="smpl">t-codings</a> 1736 1753 <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> ] ) … … 1741 1758 </p> 1742 1759 <p id="rfc.section.8.5.p.4">Examples of its use are:</p> 1743 <div id="rfc.figure.u.5 5"></div><pre class="text"> TE: deflate1760 <div id="rfc.figure.u.59"></div><pre class="text"> TE: deflate 1744 1761 TE: 1745 1762 TE: trailers, deflate;q=0.5 … … 1778 1795 chunked transfer-coding. 1779 1796 </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>1797 <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> 1781 1798 <a href="#header.trailer" class="smpl">Trailer-v</a> = 1#<a href="#message.headers" class="smpl">field-name</a> 1782 1799 </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 … … 1799 1816 transfer-coding is a property of the message, not of the entity. 1800 1817 </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>1818 <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> 1802 1819 <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding-v</a> 1803 1820 <a href="#header.transfer-encoding" class="smpl">Transfer-Encoding-v</a> = 1#<a href="#transfer.codings" class="smpl">transfer-coding</a> 1804 1821 </pre><p id="rfc.section.8.7.p.3">Transfer-codings are defined in <a href="#transfer.codings" title="Transfer Codings">Section 3.3</a>. An example is: 1805 1822 </p> 1806 <div id="rfc.figure.u. 58"></div><pre class="text"> Transfer-Encoding: chunked1823 <div id="rfc.figure.u.62"></div><pre class="text"> Transfer-Encoding: chunked 1807 1824 </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. 1808 1825 </p> … … 1814 1831 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. 1815 1832 </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>1833 <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> 1817 1834 <a href="#header.upgrade" class="smpl">Upgrade-v</a> = 1#<a href="#product.tokens" class="smpl">product</a> 1818 1835 </pre><p id="rfc.section.8.8.p.3">For example,</p> 1819 <div id="rfc.figure.u.6 0"></div><pre class="text"> Upgrade: HTTP/2.0, SHTTP/1.3, IRC/6.9, RTA/x111836 <div id="rfc.figure.u.64"></div><pre class="text"> Upgrade: HTTP/2.0, SHTTP/1.3, IRC/6.9, RTA/x11 1820 1837 </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 1821 1838 protocol. It does so by allowing the client to advertise its desire to use another protocol, such as a later version of HTTP … … 1843 1860 <h2 id="rfc.section.8.9"><a href="#rfc.section.8.9">8.9</a> <a id="header.via" href="#header.via">Via</a></h2> 1844 1861 <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 capabilities1862 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 1846 1863 of all senders along the request/response chain. 1847 1864 </p> 1848 <div id="rfc.figure.u.6 1"></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>1865 <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> 1849 1866 <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> 1850 1867 [ <a href="#rule.whitespace" class="smpl">RWS</a> <a href="#rule.comment" class="smpl">comment</a> ] ) … … 1871 1888 server at www.example.com. The request received by www.example.com would then have the following Via header field: 1872 1889 </p> 1873 <div id="rfc.figure.u.6 2"></div><pre class="text"> Via: 1.0 fred, 1.1 p.example.net (Apache/1.1)1890 <div id="rfc.figure.u.66"></div><pre class="text"> Via: 1.0 fred, 1.1 p.example.net (Apache/1.1) 1874 1891 </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. 1875 1892 </p> … … 1877 1894 For example, 1878 1895 </p> 1879 <div id="rfc.figure.u.6 3"></div><pre class="text"> Via: 1.0 ricky, 1.1 ethel, 1.1 fred, 1.0 lucy1896 <div id="rfc.figure.u.67"></div><pre class="text"> Via: 1.0 ricky, 1.1 ethel, 1.1 fred, 1.0 lucy 1880 1897 </pre><p id="rfc.section.8.9.p.12">could be collapsed to</p> 1881 <div id="rfc.figure.u.6 4"></div><pre class="text"> Via: 1.0 ricky, 1.1 mertz, 1.0 lucy1898 <div id="rfc.figure.u.68"></div><pre class="text"> Via: 1.0 ricky, 1.1 mertz, 1.0 lucy 1882 1899 </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 1883 1900 by pseudonyms. Applications <em class="bcp14">MUST NOT</em> combine entries which have different received-protocol values. … … 2531 2548 </dd> 2532 2549 </dl> 2533 <p id="rfc.section.C.p.8"> <span id="rfc.iref.g.11 0"></span> <dfn>gateway</dfn>2550 <p id="rfc.section.C.p.8"> <span id="rfc.iref.g.116"></span> <dfn>gateway</dfn> 2534 2551 </p> 2535 2552 <dl class="empty"> … … 2629 2646 </dl> 2630 2647 <h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a> <a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1> 2631 <div id="rfc.figure.u.6 5"></div> <pre class="inline"><a href="#rule.whitespace" class="smpl">BWS</a> = OWS2648 <div id="rfc.figure.u.69"></div> <pre class="inline"><a href="#rule.whitespace" class="smpl">BWS</a> = OWS 2632 2649 2633 2650 <a href="#abnf.dependencies" class="smpl">Cache-Control</a> = <Cache-Control, defined in [Part6], Section 3.4> … … 2642 2659 <a href="#header.date" class="smpl">Date-v</a> = HTTP-date 2643 2660 2644 GMT= %x47.4D.542661 <a href="#preferred.date.format" class="smpl">GMT</a> = %x47.4D.54 2645 2662 2646 2663 <a href="#http.version" class="smpl">HTTP-Prot-Name</a> = %x48.54.54.50 2647 2664 <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-date2665 <a href="#date.time.formats.full.date" class="smpl">HTTP-date</a> = rfc1123-date / obs-date 2649 2666 <a href="#message.types" class="smpl">HTTP-message</a> = Request / Response 2650 2667 <a href="#header.host" class="smpl">Host</a> = "Host:" OWS Host-v … … 2689 2706 2690 2707 <a href="#uri" class="smpl">absolute-URI</a> = <absolute-URI, defined in [RFC3986], Section 4.3> 2691 <a href="# full.date" class="smpl">asctime-date</a> = wkday SP date3 SP time SP 4DIGIT2708 <a href="#obsolete.date.formats" class="smpl">asctime-date</a> = day-name SP date3 SP time-of-day SP year 2692 2709 <a href="#rule.parameter" class="smpl">attribute</a> = token 2693 2710 <a href="#uri" class="smpl">authority</a> = <authority, defined in [RFC3986], Section 3.2> … … 2703 2720 <a href="#rule.comment" class="smpl">ctext</a> = OWS / %x21-27 / %x2A-5B / %x5D-7E / obs-text 2704 2721 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 ) ) 2722 <a href="#obsolete.date.formats" class="smpl">date1</a> = day SP month SP year 2723 <a href="#obsolete.date.formats" class="smpl">date2</a> = day "-" month "-" 2DIGIT 2724 <a href="#obsolete.date.formats" class="smpl">date3</a> = month SP ( 2DIGIT / ( SP DIGIT ) ) 2725 <a href="#preferred.date.format" class="smpl">day</a> = 2DIGIT 2726 <a href="#preferred.date.format" class="smpl">day-name</a> = s-Mon / s-Tue / s-Wed / s-Thu / s-Fri / s-Sat / s-Sun 2727 <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 2708 2728 2709 2729 <a href="#abnf.dependencies" class="smpl">entity-body</a> = <entity-body, defined in [Part3], Section 3.2> … … 2720 2740 message-body ] 2721 2741 2742 <a href="#preferred.date.format" class="smpl">hour</a> = 2DIGIT 2722 2743 <a href="#http.uri" class="smpl">http-URI</a> = "http://" authority path-abempty [ "?" query ] 2723 2744 … … 2734 2755 <entity-body encoded as per Transfer-Encoding> 2735 2756 <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 2757 <a href="#preferred.date.format" class="smpl">minute</a> = 2DIGIT 2758 <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 2737 2759 / s-Sep / s-Oct / s-Nov / s-Dec 2738 2760 2761 <a href="#obsolete.date.formats" class="smpl">obs-date</a> = rfc850-date / asctime-date 2739 2762 <a href="#rule.whitespace" class="smpl">obs-fold</a> = CRLF 2740 2763 <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-date2742 2764 2743 2765 <a href="#transfer.codings" class="smpl">parameter</a> = attribute BWS "=" BWS value … … 2766 2788 / authority 2767 2789 <a href="#abnf.dependencies" class="smpl">response-header</a> = <response-header, defined in [Part2], Section 5> 2768 <a href="# full.date" class="smpl">rfc1123-date</a> = wkday "," SP date1 SP timeSP GMT2769 <a href="# full.date" class="smpl">rfc850-date</a> = weekday "," SP date2 SP timeSP GMT2790 <a href="#preferred.date.format" class="smpl">rfc1123-date</a> = day-name "," SP date1 SP time-of-day SP GMT 2791 <a href="#obsolete.date.formats" class="smpl">rfc850-date</a> = day-name-l "," SP date2 SP time-of-day SP GMT 2770 2792 2771 2793 s-Apr = %x41.70.72 … … 2788 2810 s-Tue = %x54.75.65 2789 2811 s-Wed = %x57.65.64 2812 <a href="#preferred.date.format" class="smpl">second</a> = 2DIGIT 2790 2813 <a href="#message.types" class="smpl">start-line</a> = Request-Line / Status-Line 2791 2814 … … 2795 2818 <a href="#header.te" class="smpl">te-ext</a> = OWS ";" OWS token [ "=" ( token / quoted-string ) ] 2796 2819 <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 ":" 2DIGIT2820 <a href="#preferred.date.format" class="smpl">time-of-day</a> = hour ":" minute ":" second 2798 2821 <a href="#rule.token.separators" class="smpl">token</a> = 1*tchar 2799 2822 <a href="#chunked.transfer.encoding" class="smpl">trailer-part</a> = *( entity-header CRLF ) … … 2805 2828 <a href="#rule.parameter" class="smpl">value</a> = token / quoted-string 2806 2829 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 2809 2810 2811 </pre> <div id="rfc.figure.u.66"></div> 2830 <a href="#preferred.date.format" class="smpl">year</a> = 4DIGIT 2831 2832 2833 </pre> <div id="rfc.figure.u.70"></div> 2812 2834 <p>ABNF diagnostics:</p><pre class="inline">; Chunked-Body defined but not used 2813 2835 ; Content-Length defined but not used … … 3003 3025 </li> 3004 3026 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/162">http://tools.ietf.org/wg/httpbis/trac/ticket/162</a>>: "comment ABNF" 3027 </li> 3028 </ul> 3029 <p id="rfc.section.E.8.p.2">Partly resolved issues: </p> 3030 <ul> 3031 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/163">http://tools.ietf.org/wg/httpbis/trac/ticket/163</a>>: "editorial improvements around HTTP-date" 3005 3032 </li> 3006 3033 </ul> … … 3034 3061 </li> 3035 3062 <li class="indline0"><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul class="ind"> 3036 <li class="indline1">gateway <a class="iref" href="#rfc.iref.g.11 0">C</a></li>3063 <li class="indline1">gateway <a class="iref" href="#rfc.iref.g.116">C</a></li> 3037 3064 <li class="indline1"><tt>Grammar</tt> 3038 3065 <ul class="ind"> 3039 3066 <li class="indline1"><tt>absolute-URI</tt> <a class="iref" href="#rfc.iref.g.24"><b>2.1</b></a></li> 3040 3067 <li class="indline1">ALPHA <a class="iref" href="#rfc.iref.g.1"><b>1.2</b></a></li> 3041 <li class="indline1"><tt>asctime-date</tt> <a class="iref" href="#rfc.iref.g. 37"><b>3.2.1</b></a></li>3042 <li class="indline1"><tt>attribute</tt> <a class="iref" href="#rfc.iref.g. 48"><b>3.3</b></a></li>3068 <li class="indline1"><tt>asctime-date</tt> <a class="iref" href="#rfc.iref.g.48"><b>3.2</b></a></li> 3069 <li class="indline1"><tt>attribute</tt> <a class="iref" href="#rfc.iref.g.52"><b>3.3</b></a></li> 3043 3070 <li class="indline1"><tt>authority</tt> <a class="iref" href="#rfc.iref.g.25"><b>2.1</b></a></li> 3044 3071 <li class="indline1"><tt>BWS</tt> <a class="iref" href="#rfc.iref.g.15"><b>1.2.2</b></a></li> 3045 <li class="indline1"><tt>chunk</tt> <a class="iref" href="#rfc.iref.g.5 1"><b>3.3.1</b></a></li>3046 <li class="indline1"><tt>chunk-data</tt> <a class="iref" href="#rfc.iref.g. 57"><b>3.3.1</b></a></li>3047 <li class="indline1"><tt>chunk-ext</tt> <a class="iref" href="#rfc.iref.g. 54"><b>3.3.1</b></a></li>3048 <li class="indline1"><tt>chunk-ext-name</tt> <a class="iref" href="#rfc.iref.g. 55"><b>3.3.1</b></a></li>3049 <li class="indline1"><tt>chunk-ext-val</tt> <a class="iref" href="#rfc.iref.g. 56"><b>3.3.1</b></a></li>3050 <li class="indline1"><tt>chunk-size</tt> <a class="iref" href="#rfc.iref.g.5 2"><b>3.3.1</b></a></li>3051 <li class="indline1"><tt>Chunked-Body</tt> <a class="iref" href="#rfc.iref.g.5 0"><b>3.3.1</b></a></li>3052 <li class="indline1"><tt>comment</tt> <a class="iref" href="#rfc.iref.g. 69"><b>4.2</b></a></li>3053 <li class="indline1"><tt>Connection</tt> <a class="iref" href="#rfc.iref.g.8 3"><b>8.1</b></a></li>3054 <li class="indline1"><tt>connection-token</tt> <a class="iref" href="#rfc.iref.g. 85"><b>8.1</b></a></li>3055 <li class="indline1"><tt>Connection-v</tt> <a class="iref" href="#rfc.iref.g. 84"><b>8.1</b></a></li>3056 <li class="indline1"><tt>Content-Length</tt> <a class="iref" href="#rfc.iref.g. 86"><b>8.2</b></a></li>3057 <li class="indline1"><tt>Content-Length-v</tt> <a class="iref" href="#rfc.iref.g. 87"><b>8.2</b></a></li>3072 <li class="indline1"><tt>chunk</tt> <a class="iref" href="#rfc.iref.g.57"><b>3.3.1</b></a></li> 3073 <li class="indline1"><tt>chunk-data</tt> <a class="iref" href="#rfc.iref.g.63"><b>3.3.1</b></a></li> 3074 <li class="indline1"><tt>chunk-ext</tt> <a class="iref" href="#rfc.iref.g.60"><b>3.3.1</b></a></li> 3075 <li class="indline1"><tt>chunk-ext-name</tt> <a class="iref" href="#rfc.iref.g.61"><b>3.3.1</b></a></li> 3076 <li class="indline1"><tt>chunk-ext-val</tt> <a class="iref" href="#rfc.iref.g.62"><b>3.3.1</b></a></li> 3077 <li class="indline1"><tt>chunk-size</tt> <a class="iref" href="#rfc.iref.g.58"><b>3.3.1</b></a></li> 3078 <li class="indline1"><tt>Chunked-Body</tt> <a class="iref" href="#rfc.iref.g.56"><b>3.3.1</b></a></li> 3079 <li class="indline1"><tt>comment</tt> <a class="iref" href="#rfc.iref.g.75"><b>4.2</b></a></li> 3080 <li class="indline1"><tt>Connection</tt> <a class="iref" href="#rfc.iref.g.89"><b>8.1</b></a></li> 3081 <li class="indline1"><tt>connection-token</tt> <a class="iref" href="#rfc.iref.g.91"><b>8.1</b></a></li> 3082 <li class="indline1"><tt>Connection-v</tt> <a class="iref" href="#rfc.iref.g.90"><b>8.1</b></a></li> 3083 <li class="indline1"><tt>Content-Length</tt> <a class="iref" href="#rfc.iref.g.92"><b>8.2</b></a></li> 3084 <li class="indline1"><tt>Content-Length-v</tt> <a class="iref" href="#rfc.iref.g.93"><b>8.2</b></a></li> 3058 3085 <li class="indline1">CR <a class="iref" href="#rfc.iref.g.2"><b>1.2</b></a></li> 3059 3086 <li class="indline1">CRLF <a class="iref" href="#rfc.iref.g.3"><b>1.2</b></a></li> 3060 <li class="indline1"><tt>ctext</tt> <a class="iref" href="#rfc.iref.g.7 0"><b>4.2</b></a></li>3087 <li class="indline1"><tt>ctext</tt> <a class="iref" href="#rfc.iref.g.76"><b>4.2</b></a></li> 3061 3088 <li class="indline1">CTL <a class="iref" href="#rfc.iref.g.4"><b>1.2</b></a></li> 3062 <li class="indline1"><tt>Date</tt> <a class="iref" href="#rfc.iref.g.88"><b>8.3</b></a></li> 3063 <li class="indline1"><tt>Date-v</tt> <a class="iref" href="#rfc.iref.g.89"><b>8.3</b></a></li> 3064 <li class="indline1"><tt>date1</tt> <a class="iref" href="#rfc.iref.g.38"><b>3.2.1</b></a></li> 3065 <li class="indline1"><tt>date2</tt> <a class="iref" href="#rfc.iref.g.39"><b>3.2.1</b></a></li> 3066 <li class="indline1"><tt>date3</tt> <a class="iref" href="#rfc.iref.g.40"><b>3.2.1</b></a></li> 3089 <li class="indline1"><tt>Date</tt> <a class="iref" href="#rfc.iref.g.94"><b>8.3</b></a></li> 3090 <li class="indline1"><tt>Date-v</tt> <a class="iref" href="#rfc.iref.g.95"><b>8.3</b></a></li> 3091 <li class="indline1"><tt>date1</tt> <a class="iref" href="#rfc.iref.g.35"><b>3.2</b></a></li> 3092 <li class="indline1"><tt>date2</tt> <a class="iref" href="#rfc.iref.g.54"><b>3.3</b></a></li> 3093 <li class="indline1"><tt>date3</tt> <a class="iref" href="#rfc.iref.g.55"><b>3.3</b></a></li> 3094 <li class="indline1"><tt>day</tt> <a class="iref" href="#rfc.iref.g.42"><b>3.2</b></a></li> 3095 <li class="indline1"><tt>day-name</tt> <a class="iref" href="#rfc.iref.g.40"><b>3.2</b></a></li> 3096 <li class="indline1"><tt>day-name-l</tt> <a class="iref" href="#rfc.iref.g.41"><b>3.2</b></a></li> 3067 3097 <li class="indline1">DIGIT <a class="iref" href="#rfc.iref.g.5"><b>1.2</b></a></li> 3068 3098 <li class="indline1">DQUOTE <a class="iref" href="#rfc.iref.g.6"><b>1.2</b></a></li> 3069 <li class="indline1"><tt>extension-code</tt> <a class="iref" href="#rfc.iref.g.81"><b>6.1.1</b></a></li> 3070 <li class="indline1"><tt>extension-method</tt> <a class="iref" href="#rfc.iref.g.76"><b>5.1.1</b></a></li> 3071 <li class="indline1"><tt>field-content</tt> <a class="iref" href="#rfc.iref.g.68"><b>4.2</b></a></li> 3072 <li class="indline1"><tt>field-name</tt> <a class="iref" href="#rfc.iref.g.66"><b>4.2</b></a></li> 3073 <li class="indline1"><tt>field-value</tt> <a class="iref" href="#rfc.iref.g.67"><b>4.2</b></a></li> 3074 <li class="indline1"><tt>general-header</tt> <a class="iref" href="#rfc.iref.g.72"><b>4.5</b></a></li> 3075 <li class="indline1"><tt>generic-message</tt> <a class="iref" href="#rfc.iref.g.63"><b>4.1</b></a></li> 3099 <li class="indline1"><tt>extension-code</tt> <a class="iref" href="#rfc.iref.g.87"><b>6.1.1</b></a></li> 3100 <li class="indline1"><tt>extension-method</tt> <a class="iref" href="#rfc.iref.g.82"><b>5.1.1</b></a></li> 3101 <li class="indline1"><tt>field-content</tt> <a class="iref" href="#rfc.iref.g.74"><b>4.2</b></a></li> 3102 <li class="indline1"><tt>field-name</tt> <a class="iref" href="#rfc.iref.g.72"><b>4.2</b></a></li> 3103 <li class="indline1"><tt>field-value</tt> <a class="iref" href="#rfc.iref.g.73"><b>4.2</b></a></li> 3104 <li class="indline1"><tt>general-header</tt> <a class="iref" href="#rfc.iref.g.78"><b>4.5</b></a></li> 3105 <li class="indline1"><tt>generic-message</tt> <a class="iref" href="#rfc.iref.g.69"><b>4.1</b></a></li> 3106 <li class="indline1"><tt>GMT</tt> <a class="iref" href="#rfc.iref.g.45"><b>3.2</b></a></li> 3076 3107 <li class="indline1">HEXDIG <a class="iref" href="#rfc.iref.g.7"><b>1.2</b></a></li> 3077 <li class="indline1"><tt>Host</tt> <a class="iref" href="#rfc.iref.g.90"><b>8.4</b></a></li> 3078 <li class="indline1"><tt>Host-v</tt> <a class="iref" href="#rfc.iref.g.91"><b>8.4</b></a></li> 3079 <li class="indline1"><tt>HTTP-date</tt> <a class="iref" href="#rfc.iref.g.33"><b>3.2.1</b></a></li> 3080 <li class="indline1"><tt>HTTP-message</tt> <a class="iref" href="#rfc.iref.g.62"><b>4.1</b></a></li> 3108 <li class="indline1"><tt>Host</tt> <a class="iref" href="#rfc.iref.g.96"><b>8.4</b></a></li> 3109 <li class="indline1"><tt>Host-v</tt> <a class="iref" href="#rfc.iref.g.97"><b>8.4</b></a></li> 3110 <li class="indline1"><tt>hour</tt> <a class="iref" href="#rfc.iref.g.37"><b>3.2</b></a></li> 3111 <li class="indline1"><tt>HTTP-date</tt> <a class="iref" href="#rfc.iref.g.33"><b>3.2</b></a></li> 3112 <li class="indline1"><tt>HTTP-message</tt> <a class="iref" href="#rfc.iref.g.68"><b>4.1</b></a></li> 3081 3113 <li class="indline1"><tt>HTTP-Prot-Name</tt> <a class="iref" href="#rfc.iref.g.32"><b>3.1</b></a></li> 3082 3114 <li class="indline1"><tt>http-URI</tt> <a class="iref" href="#rfc.iref.g.30"><b>2.1.1</b></a></li> 3083 3115 <li class="indline1"><tt>HTTP-Version</tt> <a class="iref" href="#rfc.iref.g.31"><b>3.1</b></a></li> 3084 <li class="indline1"><tt>last-chunk</tt> <a class="iref" href="#rfc.iref.g.5 3"><b>3.3.1</b></a></li>3116 <li class="indline1"><tt>last-chunk</tt> <a class="iref" href="#rfc.iref.g.59"><b>3.3.1</b></a></li> 3085 3117 <li class="indline1">LF <a class="iref" href="#rfc.iref.g.8"><b>1.2</b></a></li> 3086 <li class="indline1"><tt>message-body</tt> <a class="iref" href="#rfc.iref.g.71"><b>4.3</b></a></li> 3087 <li class="indline1"><tt>message-header</tt> <a class="iref" href="#rfc.iref.g.65"><b>4.2</b></a></li> 3088 <li class="indline1"><tt>Method</tt> <a class="iref" href="#rfc.iref.g.75"><b>5.1.1</b></a></li> 3089 <li class="indline1"><tt>month</tt> <a class="iref" href="#rfc.iref.g.44"><b>3.2.1</b></a></li> 3118 <li class="indline1"><tt>message-body</tt> <a class="iref" href="#rfc.iref.g.77"><b>4.3</b></a></li> 3119 <li class="indline1"><tt>message-header</tt> <a class="iref" href="#rfc.iref.g.71"><b>4.2</b></a></li> 3120 <li class="indline1"><tt>Method</tt> <a class="iref" href="#rfc.iref.g.81"><b>5.1.1</b></a></li> 3121 <li class="indline1"><tt>minute</tt> <a class="iref" href="#rfc.iref.g.38"><b>3.2</b></a></li> 3122 <li class="indline1"><tt>month</tt> <a class="iref" href="#rfc.iref.g.43"><b>3.2</b></a></li> 3123 <li class="indline1"><tt>obs-date</tt> <a class="iref" href="#rfc.iref.g.46"><b>3.2</b></a></li> 3090 3124 <li class="indline1"><tt>obs-text</tt> <a class="iref" href="#rfc.iref.g.20"><b>1.2.2</b></a></li> 3091 <li class="indline1"><tt>obsolete-date</tt> <a class="iref" href="#rfc.iref.g.35"><b>3.2.1</b></a></li>3092 3125 <li class="indline1">OCTET <a class="iref" href="#rfc.iref.g.9"><b>1.2</b></a></li> 3093 3126 <li class="indline1"><tt>OWS</tt> <a class="iref" href="#rfc.iref.g.13"><b>1.2.2</b></a></li> 3094 <li class="indline1"><tt>parameter</tt> <a class="iref" href="#rfc.iref.g. 47"><b>3.3</b></a></li>3127 <li class="indline1"><tt>parameter</tt> <a class="iref" href="#rfc.iref.g.51"><b>3.3</b></a></li> 3095 3128 <li class="indline1"><tt>path-absolute</tt> <a class="iref" href="#rfc.iref.g.26"><b>2.1</b></a></li> 3096 3129 <li class="indline1"><tt>port</tt> <a class="iref" href="#rfc.iref.g.27"><b>2.1</b></a></li> 3097 <li class="indline1"><tt>product</tt> <a class="iref" href="#rfc.iref.g. 59"><b>3.4</b></a></li>3098 <li class="indline1"><tt>product-version</tt> <a class="iref" href="#rfc.iref.g.6 0"><b>3.4</b></a></li>3099 <li class="indline1"><tt>protocol-name</tt> <a class="iref" href="#rfc.iref.g.1 06"><b>8.9</b></a></li>3100 <li class="indline1"><tt>protocol-version</tt> <a class="iref" href="#rfc.iref.g.1 07"><b>8.9</b></a></li>3101 <li class="indline1"><tt>pseudonym</tt> <a class="iref" href="#rfc.iref.g.1 09"><b>8.9</b></a></li>3130 <li class="indline1"><tt>product</tt> <a class="iref" href="#rfc.iref.g.65"><b>3.4</b></a></li> 3131 <li class="indline1"><tt>product-version</tt> <a class="iref" href="#rfc.iref.g.66"><b>3.4</b></a></li> 3132 <li class="indline1"><tt>protocol-name</tt> <a class="iref" href="#rfc.iref.g.112"><b>8.9</b></a></li> 3133 <li class="indline1"><tt>protocol-version</tt> <a class="iref" href="#rfc.iref.g.113"><b>8.9</b></a></li> 3134 <li class="indline1"><tt>pseudonym</tt> <a class="iref" href="#rfc.iref.g.115"><b>8.9</b></a></li> 3102 3135 <li class="indline1"><tt>qdtext</tt> <a class="iref" href="#rfc.iref.g.19"><b>1.2.2</b></a></li> 3103 3136 <li class="indline1"><tt>query</tt> <a class="iref" href="#rfc.iref.g.28"><b>2.1</b></a></li> … … 3105 3138 <li class="indline1"><tt>quoted-string</tt> <a class="iref" href="#rfc.iref.g.18"><b>1.2.2</b></a></li> 3106 3139 <li class="indline1"><tt>quoted-text</tt> <a class="iref" href="#rfc.iref.g.21"><b>1.2.2</b></a></li> 3107 <li class="indline1"><tt>qvalue</tt> <a class="iref" href="#rfc.iref.g.6 1"><b>3.5</b></a></li>3108 <li class="indline1"><tt>Reason-Phrase</tt> <a class="iref" href="#rfc.iref.g.8 2"><b>6.1.1</b></a></li>3109 <li class="indline1"><tt>received-by</tt> <a class="iref" href="#rfc.iref.g.1 08"><b>8.9</b></a></li>3110 <li class="indline1"><tt>received-protocol</tt> <a class="iref" href="#rfc.iref.g.1 05"><b>8.9</b></a></li>3111 <li class="indline1"><tt>Request</tt> <a class="iref" href="#rfc.iref.g.7 3"><b>5</b></a></li>3112 <li class="indline1"><tt>Request-Line</tt> <a class="iref" href="#rfc.iref.g. 74"><b>5.1</b></a></li>3113 <li class="indline1"><tt>request-target</tt> <a class="iref" href="#rfc.iref.g. 77"><b>5.1.2</b></a></li>3114 <li class="indline1"><tt>Response</tt> <a class="iref" href="#rfc.iref.g. 78"><b>6</b></a></li>3115 <li class="indline1"><tt>rfc1123-date</tt> <a class="iref" href="#rfc.iref.g.34"><b>3.2 .1</b></a></li>3116 <li class="indline1"><tt>rfc850-date</tt> <a class="iref" href="#rfc.iref.g. 36"><b>3.2.1</b></a></li>3140 <li class="indline1"><tt>qvalue</tt> <a class="iref" href="#rfc.iref.g.67"><b>3.5</b></a></li> 3141 <li class="indline1"><tt>Reason-Phrase</tt> <a class="iref" href="#rfc.iref.g.88"><b>6.1.1</b></a></li> 3142 <li class="indline1"><tt>received-by</tt> <a class="iref" href="#rfc.iref.g.114"><b>8.9</b></a></li> 3143 <li class="indline1"><tt>received-protocol</tt> <a class="iref" href="#rfc.iref.g.111"><b>8.9</b></a></li> 3144 <li class="indline1"><tt>Request</tt> <a class="iref" href="#rfc.iref.g.79"><b>5</b></a></li> 3145 <li class="indline1"><tt>Request-Line</tt> <a class="iref" href="#rfc.iref.g.80"><b>5.1</b></a></li> 3146 <li class="indline1"><tt>request-target</tt> <a class="iref" href="#rfc.iref.g.83"><b>5.1.2</b></a></li> 3147 <li class="indline1"><tt>Response</tt> <a class="iref" href="#rfc.iref.g.84"><b>6</b></a></li> 3148 <li class="indline1"><tt>rfc1123-date</tt> <a class="iref" href="#rfc.iref.g.34"><b>3.2</b></a></li> 3149 <li class="indline1"><tt>rfc850-date</tt> <a class="iref" href="#rfc.iref.g.47"><b>3.2</b></a></li> 3117 3150 <li class="indline1"><tt>RWS</tt> <a class="iref" href="#rfc.iref.g.14"><b>1.2.2</b></a></li> 3151 <li class="indline1"><tt>second</tt> <a class="iref" href="#rfc.iref.g.39"><b>3.2</b></a></li> 3118 3152 <li class="indline1">SP <a class="iref" href="#rfc.iref.g.10"><b>1.2</b></a></li> 3119 <li class="indline1"><tt>start-line</tt> <a class="iref" href="#rfc.iref.g. 64"><b>4.1</b></a></li>3120 <li class="indline1"><tt>Status-Code</tt> <a class="iref" href="#rfc.iref.g.8 0"><b>6.1.1</b></a></li>3121 <li class="indline1"><tt>Status-Line</tt> <a class="iref" href="#rfc.iref.g. 79"><b>6.1</b></a></li>3122 <li class="indline1"><tt>t-codings</tt> <a class="iref" href="#rfc.iref.g. 94"><b>8.5</b></a></li>3153 <li class="indline1"><tt>start-line</tt> <a class="iref" href="#rfc.iref.g.70"><b>4.1</b></a></li> 3154 <li class="indline1"><tt>Status-Code</tt> <a class="iref" href="#rfc.iref.g.86"><b>6.1.1</b></a></li> 3155 <li class="indline1"><tt>Status-Line</tt> <a class="iref" href="#rfc.iref.g.85"><b>6.1</b></a></li> 3156 <li class="indline1"><tt>t-codings</tt> <a class="iref" href="#rfc.iref.g.100"><b>8.5</b></a></li> 3123 3157 <li class="indline1"><tt>tchar</tt> <a class="iref" href="#rfc.iref.g.17"><b>1.2.2</b></a></li> 3124 <li class="indline1"><tt>TE</tt> <a class="iref" href="#rfc.iref.g.9 2"><b>8.5</b></a></li>3125 <li class="indline1"><tt>te-ext</tt> <a class="iref" href="#rfc.iref.g. 96"><b>8.5</b></a></li>3126 <li class="indline1"><tt>te-params</tt> <a class="iref" href="#rfc.iref.g. 95"><b>8.5</b></a></li>3127 <li class="indline1"><tt>TE-v</tt> <a class="iref" href="#rfc.iref.g.9 3"><b>8.5</b></a></li>3128 <li class="indline1"><tt>time </tt> <a class="iref" href="#rfc.iref.g.41"><b>3.2.1</b></a></li>3158 <li class="indline1"><tt>TE</tt> <a class="iref" href="#rfc.iref.g.98"><b>8.5</b></a></li> 3159 <li class="indline1"><tt>te-ext</tt> <a class="iref" href="#rfc.iref.g.102"><b>8.5</b></a></li> 3160 <li class="indline1"><tt>te-params</tt> <a class="iref" href="#rfc.iref.g.101"><b>8.5</b></a></li> 3161 <li class="indline1"><tt>TE-v</tt> <a class="iref" href="#rfc.iref.g.99"><b>8.5</b></a></li> 3162 <li class="indline1"><tt>time-of-day</tt> <a class="iref" href="#rfc.iref.g.36"><b>3.2</b></a></li> 3129 3163 <li class="indline1"><tt>token</tt> <a class="iref" href="#rfc.iref.g.16"><b>1.2.2</b></a></li> 3130 <li class="indline1"><tt>Trailer</tt> <a class="iref" href="#rfc.iref.g. 97"><b>8.6</b></a></li>3131 <li class="indline1"><tt>trailer-part</tt> <a class="iref" href="#rfc.iref.g. 58"><b>3.3.1</b></a></li>3132 <li class="indline1"><tt>Trailer-v</tt> <a class="iref" href="#rfc.iref.g. 98"><b>8.6</b></a></li>3133 <li class="indline1"><tt>transfer-coding</tt> <a class="iref" href="#rfc.iref.g.4 5"><b>3.3</b></a></li>3134 <li class="indline1"><tt>Transfer-Encoding</tt> <a class="iref" href="#rfc.iref.g. 99"><b>8.7</b></a></li>3135 <li class="indline1"><tt>Transfer-Encoding-v</tt> <a class="iref" href="#rfc.iref.g.10 0"><b>8.7</b></a></li>3136 <li class="indline1"><tt>transfer-extension</tt> <a class="iref" href="#rfc.iref.g. 46"><b>3.3</b></a></li>3137 <li class="indline1"><tt>Upgrade</tt> <a class="iref" href="#rfc.iref.g.10 1"><b>8.8</b></a></li>3138 <li class="indline1"><tt>Upgrade-v</tt> <a class="iref" href="#rfc.iref.g.10 2"><b>8.8</b></a></li>3164 <li class="indline1"><tt>Trailer</tt> <a class="iref" href="#rfc.iref.g.103"><b>8.6</b></a></li> 3165 <li class="indline1"><tt>trailer-part</tt> <a class="iref" href="#rfc.iref.g.64"><b>3.3.1</b></a></li> 3166 <li class="indline1"><tt>Trailer-v</tt> <a class="iref" href="#rfc.iref.g.104"><b>8.6</b></a></li> 3167 <li class="indline1"><tt>transfer-coding</tt> <a class="iref" href="#rfc.iref.g.49"><b>3.3</b></a></li> 3168 <li class="indline1"><tt>Transfer-Encoding</tt> <a class="iref" href="#rfc.iref.g.105"><b>8.7</b></a></li> 3169 <li class="indline1"><tt>Transfer-Encoding-v</tt> <a class="iref" href="#rfc.iref.g.106"><b>8.7</b></a></li> 3170 <li class="indline1"><tt>transfer-extension</tt> <a class="iref" href="#rfc.iref.g.50"><b>3.3</b></a></li> 3171 <li class="indline1"><tt>Upgrade</tt> <a class="iref" href="#rfc.iref.g.107"><b>8.8</b></a></li> 3172 <li class="indline1"><tt>Upgrade-v</tt> <a class="iref" href="#rfc.iref.g.108"><b>8.8</b></a></li> 3139 3173 <li class="indline1"><tt>uri-host</tt> <a class="iref" href="#rfc.iref.g.29"><b>2.1</b></a></li> 3140 3174 <li class="indline1"><tt>URI-reference</tt> <a class="iref" href="#rfc.iref.g.23"><b>2.1</b></a></li> 3141 <li class="indline1"><tt>value</tt> <a class="iref" href="#rfc.iref.g. 49"><b>3.3</b></a></li>3175 <li class="indline1"><tt>value</tt> <a class="iref" href="#rfc.iref.g.53"><b>3.3</b></a></li> 3142 3176 <li class="indline1">VCHAR <a class="iref" href="#rfc.iref.g.11"><b>1.2</b></a></li> 3143 <li class="indline1"><tt>Via</tt> <a class="iref" href="#rfc.iref.g.103"><b>8.9</b></a></li> 3144 <li class="indline1"><tt>Via-v</tt> <a class="iref" href="#rfc.iref.g.104"><b>8.9</b></a></li> 3145 <li class="indline1"><tt>weekday</tt> <a class="iref" href="#rfc.iref.g.43"><b>3.2.1</b></a></li> 3146 <li class="indline1"><tt>wkday</tt> <a class="iref" href="#rfc.iref.g.42"><b>3.2.1</b></a></li> 3177 <li class="indline1"><tt>Via</tt> <a class="iref" href="#rfc.iref.g.109"><b>8.9</b></a></li> 3178 <li class="indline1"><tt>Via-v</tt> <a class="iref" href="#rfc.iref.g.110"><b>8.9</b></a></li> 3147 3179 <li class="indline1">WSP <a class="iref" href="#rfc.iref.g.12"><b>1.2</b></a></li> 3180 <li class="indline1"><tt>year</tt> <a class="iref" href="#rfc.iref.g.44"><b>3.2</b></a></li> 3148 3181 </ul> 3149 3182 </li> … … 3239 3272 <li class="indline1">resource <a class="iref" href="#rfc.iref.r.2">C</a></li> 3240 3273 <li class="indline1">response <a class="iref" href="#rfc.iref.r.3">C</a></li> 3241 <li class="indline1"><em>RFC1123</em> <a class="iref" href="#rfc.xref.RFC1123.1">3.2 .1</a>, <a class="iref" href="#RFC1123"><b>12.2</b></a></li>3274 <li class="indline1"><em>RFC1123</em> <a class="iref" href="#rfc.xref.RFC1123.1">3.2</a>, <a class="iref" href="#RFC1123"><b>12.2</b></a></li> 3242 3275 <li class="indline1"><em>RFC1305</em> <a class="iref" href="#rfc.xref.RFC1305.1">8.3</a>, <a class="iref" href="#RFC1305"><b>12.2</b></a></li> 3243 3276 <li class="indline1"><em>RFC1900</em> <a class="iref" href="#rfc.xref.RFC1900.1">2.1.1</a>, <a class="iref" href="#rfc.xref.RFC1900.2">10.4</a>, <a class="iref" href="#RFC1900"><b>12.2</b></a></li> … … 3276 3309 </ul> 3277 3310 </li> 3278 <li class="indline1"><em>RFC5322</em> <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> <a class="iref" href="#rfc.xref.RFC5322.3">4.2</a></li> 3280 <li class="indline1"><em>Section 3.6.1</em> <a class="iref" href="#rfc.xref.RFC5322.4">8.3</a></li> 3281 <li class="indline1"><em>Section 3.6.7</em> <a class="iref" href="#rfc.xref.RFC5322.5">8.9</a></li> 3311 <li class="indline1"><em>RFC5322</em> <a class="iref" href="#rfc.xref.RFC5322.1">1</a>, <a class="iref" href="#rfc.xref.RFC5322.2">3.2</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"> 3312 <li class="indline1"><em>Section 2.1</em> <a class="iref" href="#rfc.xref.RFC5322.4">4.2</a></li> 3313 <li class="indline1"><em>Section 3.6.1</em> <a class="iref" href="#rfc.xref.RFC5322.5">8.3</a></li> 3314 <li class="indline1"><em>Section 3.6.7</em> <a class="iref" href="#rfc.xref.RFC5322.6">8.9</a></li> 3315 <li class="indline1"><em>Section 3.3</em> <a class="iref" href="#rfc.xref.RFC5322.2">3.2</a></li> 3282 3316 </ul> 3283 3317 </li> -
draft-ietf-httpbis/latest/p1-messaging.xml
r578 r580 836 836 </section> 837 837 838 <section title="Date/Time Formats" anchor="date.time.formats"> 839 <section title="Full Date" anchor="full.date"> 838 <section title="Date/Time Formats: Full Date" anchor="date.time.formats.full.date"> 840 839 <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"/>853 840 <t> 854 841 HTTP applications have historically allowed three different formats … … 870 857 in header fields. See <xref target="tolerant.applications"/> for further information. 871 858 </t> 872 <x:note>873 <t>874 <x:h>Note:</x:h> Recipients of date values are encouraged to be robust in875 accepting date values that may have been sent by non-HTTP876 applications, as is sometimes the case when retrieving or posting877 messages via proxies/gateways to SMTP or NNTP.878 </t>879 </x:note>880 859 <t> 881 860 All HTTP date/time stamps &MUST; be represented in Greenwich Mean Time … … 888 867 grammar. 889 868 </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 869 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="HTTP-date"/> 870 <x:ref>HTTP-date</x:ref> = <x:ref>rfc1123-date</x:ref> / <x:ref>obs-date</x:ref> 871 </artwork></figure> 872 <t anchor="preferred.date.format"> 873 <x:anchor-alias value="rfc1123-date"/> 874 <x:anchor-alias value="time-of-day"/> 875 <x:anchor-alias value="hour"/> 876 <x:anchor-alias value="minute"/> 877 <x:anchor-alias value="second"/> 878 <x:anchor-alias value="day-name"/> 879 <x:anchor-alias value="day"/> 880 <x:anchor-alias value="month"/> 881 <x:anchor-alias value="year"/> 882 <x:anchor-alias value="GMT"/> 883 Preferred format: 884 </t> 885 <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"/> 886 <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> 887 888 <x:ref>day-name</x:ref> = s-Mon / s-Tue / s-Wed 905 889 / s-Thu / s-Fri / s-Sat / s-Sun 906 <x:ref>weekday</x:ref> = l-Mon / l-Tue / l-Wed907 / l-Thu / l-Fri / l-Sat / l-Sun908 <x:ref>month</x:ref> = s-Jan / s-Feb / s-Mar / s-Apr909 / s-May / s-Jun / s-Jul / s-Aug910 / s-Sep / s-Oct / s-Nov / s-Dec911 890 912 GMT = <x:abnf-char-sequence>"GMT"</x:abnf-char-sequence> ; "GMT", case-sensitive913 914 891 s-Mon = <x:abnf-char-sequence>"Mon"</x:abnf-char-sequence> ; "Mon", case-sensitive 915 892 s-Tue = <x:abnf-char-sequence>"Tue"</x:abnf-char-sequence> ; "Tue", case-sensitive … … 920 897 s-Sun = <x:abnf-char-sequence>"Sun"</x:abnf-char-sequence> ; "Sun", case-sensitive 921 898 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 899 <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> 900 ; e.g., 02 Jun 1982 901 902 <x:ref>day</x:ref> = 2<x:ref>DIGIT</x:ref> 903 <x:ref>month</x:ref> = s-Jan / s-Feb / s-Mar / s-Apr 904 / s-May / s-Jun / s-Jul / s-Aug 905 / s-Sep / s-Oct / s-Nov / s-Dec 906 <x:ref>year</x:ref> = 4<x:ref>DIGIT</x:ref> 929 907 930 908 s-Jan = <x:abnf-char-sequence>"Jan"</x:abnf-char-sequence> ; "Jan", case-sensitive … … 940 918 s-Nov = <x:abnf-char-sequence>"Nov"</x:abnf-char-sequence> ; "Nov", case-sensitive 941 919 s-Dec = <x:abnf-char-sequence>"Dec"</x:abnf-char-sequence> ; "Dec", case-sensitive 942 </artwork></figure> 943 <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. 948 </t> 949 </section> 920 921 <x:ref>GMT</x:ref> = <x:abnf-char-sequence>"GMT"</x:abnf-char-sequence> ; "GMT", case-sensitive 922 923 <x:ref>time-of-day</x:ref> = <x:ref>hour</x:ref> ":" <x:ref>minute</x:ref> ":" <x:ref>second</x:ref> 924 ; 00:00:00 - 23:59:59 925 926 <x:ref>hour</x:ref> = 2<x:ref>DIGIT</x:ref> 927 <x:ref>minute</x:ref> = 2<x:ref>DIGIT</x:ref> 928 <x:ref>second</x:ref> = 2<x:ref>DIGIT</x:ref> 929 </artwork></figure> 930 <t> 931 The semantics of <x:ref>day-name</x:ref>, <x:ref>day</x:ref>, 932 <x:ref>month</x:ref>, <x:ref>year</x:ref>, and <x:ref>time-of-day</x:ref> are the 933 same as those defined in the RFC 5322 constructs 934 with the corresponding name (<xref target="RFC5322" x:fmt="," x:sec="3.3"/>). 935 </t> 936 <t anchor="obsolete.date.formats"> 937 <x:anchor-alias value="obs-date"/> 938 <x:anchor-alias value="rfc850-date"/> 939 <x:anchor-alias value="asctime-date"/> 940 <x:anchor-alias value="date1"/> 941 <x:anchor-alias value="date2"/> 942 <x:anchor-alias value="date3"/> 943 <x:anchor-alias value="rfc1123-date"/> 944 <x:anchor-alias value="day-name-l"/> 945 Obsolete formats: 946 </t> 947 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="obs-date"/> 948 <x:ref>obs-date</x:ref> = <x:ref>rfc850-date</x:ref> / <x:ref>asctime-date</x:ref> 949 </artwork></figure> 950 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="rfc850-date"/> 951 <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> 952 <x:ref>date2</x:ref> = <x:ref>day</x:ref> "-" <x:ref>month</x:ref> "-" 2<x:ref>DIGIT</x:ref> 953 ; day-month-year (e.g., 02-Jun-82) 954 955 <x:ref>day-name-l</x:ref> = l-Mon / l-Tue / l-Wed 956 / l-Thu / l-Fri / l-Sat / l-Sun 957 958 l-Mon = <x:abnf-char-sequence>"Monday"</x:abnf-char-sequence> ; "Monday", case-sensitive 959 l-Tue = <x:abnf-char-sequence>"Tuesday"</x:abnf-char-sequence> ; "Tuesday", case-sensitive 960 l-Wed = <x:abnf-char-sequence>"Wednesday"</x:abnf-char-sequence> ; "Wednesday", case-sensitive 961 l-Thu = <x:abnf-char-sequence>"Thursday"</x:abnf-char-sequence> ; "Thursday", case-sensitive 962 l-Fri = <x:abnf-char-sequence>"Friday"</x:abnf-char-sequence> ; "Friday", case-sensitive 963 l-Sat = <x:abnf-char-sequence>"Saturday"</x:abnf-char-sequence> ; "Saturday", case-sensitive 964 l-Sun = <x:abnf-char-sequence>"Sunday"</x:abnf-char-sequence> ; "Sunday", case-sensitive 965 </artwork></figure> 966 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="asctime-date"/> 967 <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> 968 <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> )) 969 ; month day (e.g., Jun 2) 970 </artwork></figure> 971 <x:note> 972 <t> 973 <x:h>Note:</x:h> Recipients of date values are encouraged to be robust in 974 accepting date values that may have been sent by non-HTTP 975 applications, as is sometimes the case when retrieving or posting 976 messages via proxies/gateways to SMTP or NNTP. 977 </t> 978 </x:note> 979 <x:note> 980 <t> 981 <x:h>Note:</x:h> HTTP requirements for the date/time stamp format apply only 982 to their usage within the protocol stream. Clients and servers are 983 not required to use these formats for user presentation, request 984 logging, etc. 985 </t> 986 </x:note> 950 987 </section> 951 988 … … 971 1008 Parameters are in the form of attribute/value pairs. 972 1009 </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"/> 1010 <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"/> 974 1011 <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> 975 1012 <x:ref>attribute</x:ref> = <x:ref>token</x:ref> … … 2285 2322 the message was originated, having the same semantics as orig-date in 2286 2323 <xref target="RFC5322" x:fmt="of" x:sec="3.6.1"/>. The field value is an 2287 HTTP-date, as described in <xref target=" full.date"/>;2324 HTTP-date, as described in <xref target="date.time.formats.full.date"/>; 2288 2325 it &MUST; be sent in rfc1123-date format. 2289 2326 </t> … … 4362 4399 <x:ref>Date-v</x:ref> = HTTP-date 4363 4400 4364 GMT= %x47.4D.544401 <x:ref>GMT</x:ref> = %x47.4D.54 4365 4402 4366 4403 <x:ref>HTTP-Prot-Name</x:ref> = %x48.54.54.50 4367 4404 <x:ref>HTTP-Version</x:ref> = HTTP-Prot-Name "/" 1*DIGIT "." 1*DIGIT 4368 <x:ref>HTTP-date</x:ref> = rfc1123-date / obs olete-date4405 <x:ref>HTTP-date</x:ref> = rfc1123-date / obs-date 4369 4406 <x:ref>HTTP-message</x:ref> = Request / Response 4370 4407 <x:ref>Host</x:ref> = "Host:" OWS Host-v … … 4409 4446 4410 4447 <x:ref>absolute-URI</x:ref> = <absolute-URI, defined in [RFC3986], Section 4.3> 4411 <x:ref>asctime-date</x:ref> = wkday SP date3 SP time SP 4DIGIT4448 <x:ref>asctime-date</x:ref> = day-name SP date3 SP time-of-day SP year 4412 4449 <x:ref>attribute</x:ref> = token 4413 4450 <x:ref>authority</x:ref> = <authority, defined in [RFC3986], Section 3.2> … … 4423 4460 <x:ref>ctext</x:ref> = OWS / %x21-27 / %x2A-5B / %x5D-7E / obs-text 4424 4461 4425 <x:ref>date1</x:ref> = 2DIGIT SP month SP 4DIGIT4426 <x:ref>date2</x:ref> = 2DIGIT"-" month "-" 2DIGIT4462 <x:ref>date1</x:ref> = day SP month SP year 4463 <x:ref>date2</x:ref> = day "-" month "-" 2DIGIT 4427 4464 <x:ref>date3</x:ref> = month SP ( 2DIGIT / ( SP DIGIT ) ) 4465 <x:ref>day</x:ref> = 2DIGIT 4466 <x:ref>day-name</x:ref> = s-Mon / s-Tue / s-Wed / s-Thu / s-Fri / s-Sat / s-Sun 4467 <x:ref>day-name-l</x:ref> = l-Mon / l-Tue / l-Wed / l-Thu / l-Fri / l-Sat / l-Sun 4428 4468 4429 4469 <x:ref>entity-body</x:ref> = <entity-body, defined in [Part3], Section 3.2> … … 4440 4480 message-body ] 4441 4481 4482 <x:ref>hour</x:ref> = 2DIGIT 4442 4483 <x:ref>http-URI</x:ref> = "http://" authority path-abempty [ "?" query ] 4443 4484 … … 4454 4495 <entity-body encoded as per Transfer-Encoding> 4455 4496 <x:ref>message-header</x:ref> = field-name ":" OWS [ field-value ] OWS 4497 <x:ref>minute</x:ref> = 2DIGIT 4456 4498 <x:ref>month</x:ref> = s-Jan / s-Feb / s-Mar / s-Apr / s-May / s-Jun / s-Jul / s-Aug 4457 4499 / s-Sep / s-Oct / s-Nov / s-Dec 4458 4500 4501 <x:ref>obs-date</x:ref> = rfc850-date / asctime-date 4459 4502 <x:ref>obs-fold</x:ref> = CRLF 4460 4503 <x:ref>obs-text</x:ref> = %x80-FF 4461 <x:ref>obsolete-date</x:ref> = rfc850-date / asctime-date4462 4504 4463 4505 <x:ref>parameter</x:ref> = attribute BWS "=" BWS value … … 4486 4528 / authority 4487 4529 <x:ref>response-header</x:ref> = <response-header, defined in [Part2], Section 5> 4488 <x:ref>rfc1123-date</x:ref> = wkday "," SP date1 SP timeSP GMT4489 <x:ref>rfc850-date</x:ref> = weekday "," SP date2 SP timeSP GMT4530 <x:ref>rfc1123-date</x:ref> = day-name "," SP date1 SP time-of-day SP GMT 4531 <x:ref>rfc850-date</x:ref> = day-name-l "," SP date2 SP time-of-day SP GMT 4490 4532 4491 4533 s-Apr = %x41.70.72 … … 4508 4550 s-Tue = %x54.75.65 4509 4551 s-Wed = %x57.65.64 4552 <x:ref>second</x:ref> = 2DIGIT 4510 4553 <x:ref>start-line</x:ref> = Request-Line / Status-Line 4511 4554 … … 4515 4558 <x:ref>te-ext</x:ref> = OWS ";" OWS token [ "=" ( token / quoted-string ) ] 4516 4559 <x:ref>te-params</x:ref> = OWS ";" OWS "q=" qvalue *te-ext 4517 <x:ref>time </x:ref> = 2DIGIT ":" 2DIGIT ":" 2DIGIT4560 <x:ref>time-of-day</x:ref> = hour ":" minute ":" second 4518 4561 <x:ref>token</x:ref> = 1*tchar 4519 4562 <x:ref>trailer-part</x:ref> = *( entity-header CRLF ) … … 4525 4568 <x:ref>value</x:ref> = token / quoted-string 4526 4569 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 4570 <x:ref>year</x:ref> = 4DIGIT 4529 4571 4530 4572 … … 4919 4961 </list> 4920 4962 </t> 4963 <t> 4964 Partly resolved issues: 4965 <list style="symbols"> 4966 <t> 4967 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/163"/>: 4968 "editorial improvements around HTTP-date" 4969 </t> 4970 </list> 4971 </t> 4921 4972 </section> 4922 4973 -
draft-ietf-httpbis/latest/p2-semantics.html
r579 r580 471 471 <tr> 472 472 <td class="header left"></td> 473 <td class="header right">May 9, 2009</td>473 <td class="header right">May 10, 2009</td> 474 474 </tr> 475 475 </table> … … 701 701 <a href="#abnf.dependencies" class="smpl">fragment</a> = <fragment, defined in <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.1</a>> 702 702 <a href="#abnf.dependencies" class="smpl">Host</a> = <Host, defined in <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.1</a>> 703 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html# full.date" title="Full Date">Section 3.2.1</a>>703 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 3.2</a>> 704 704 <a href="#abnf.dependencies" class="smpl">partial-URI</a> = <partial-URI, defined in <a href="#Part1" id="rfc.xref.Part1.14"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.1</a>> 705 705 <a href="#abnf.dependencies" class="smpl">product</a> = <product, defined in <a href="#Part1" id="rfc.xref.Part1.15"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#product.tokens" title="Product Tokens">Section 3.4</a>> … … 2266 2266 <a href="#header.from" class="smpl">From-v</a> = mailbox 2267 2267 2268 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in [Part1], Section 3.2 .1>2268 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in [Part1], Section 3.2> 2269 2269 <a href="#abnf.dependencies" class="smpl">Host</a> = <Host, defined in [Part1], Section 2.1> 2270 2270 … … 2655 2655 <li class="indline1"><em>Section 2.1</em> <a class="iref" href="#rfc.xref.Part1.10">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.11">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.12">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.14">1.2.2</a></li> 2656 2656 <li class="indline1"><em>Section 3.1</em> <a class="iref" href="#rfc.xref.Part1.23">8.5.6</a></li> 2657 <li class="indline1"><em>Section 3.2 .1</em> <a class="iref" href="#rfc.xref.Part1.13">1.2.2</a></li>2657 <li class="indline1"><em>Section 3.2</em> <a class="iref" href="#rfc.xref.Part1.13">1.2.2</a></li> 2658 2658 <li class="indline1"><em>Section 3.4</em> <a class="iref" href="#rfc.xref.Part1.15">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.25">9.8</a>, <a class="iref" href="#rfc.xref.Part1.27">9.9</a></li> 2659 2659 <li class="indline1"><em>Section 4.3</em> <a class="iref" href="#rfc.xref.Part1.19">6</a></li> -
draft-ietf-httpbis/latest/p2-semantics.xml
r579 r580 26 26 <!ENTITY basic-rules "<xref target='Part1' x:rel='#basic.rules' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 27 27 <!ENTITY uri "<xref target='Part1' x:rel='#uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 28 <!ENTITY full-date "<xref target='Part1' x:rel='# full.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">28 <!ENTITY full-date "<xref target='Part1' x:rel='#date.time.formats.full.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 29 29 <!ENTITY http-url "<xref target='Part1' x:rel='#http-url' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 30 30 <!ENTITY http-version "<xref target='Part1' x:rel='#http.version' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> … … 3243 3243 <x:ref>From-v</x:ref> = mailbox 3244 3244 3245 <x:ref>HTTP-date</x:ref> = <HTTP-date, defined in [Part1], Section 3.2 .1>3245 <x:ref>HTTP-date</x:ref> = <HTTP-date, defined in [Part1], Section 3.2> 3246 3246 <x:ref>Host</x:ref> = <Host, defined in [Part1], Section 2.1> 3247 3247 -
draft-ietf-httpbis/latest/p3-payload.html
r577 r580 478 478 <tr> 479 479 <td class="header left"></td> 480 <td class="header right">May 6, 2009</td>480 <td class="header right">May 10, 2009</td> 481 481 </tr> 482 482 </table> … … 1648 1648 </p> 1649 1649 <h2 id="rfc.section.A.3"><a href="#rfc.section.A.3">A.3</a> <a id="conversion.of.date.formats" href="#conversion.of.date.formats">Conversion of Date Formats</a></h2> 1650 <p id="rfc.section.A.3.p.1">HTTP/1.1 uses a restricted set of date formats (<a href="p1-messaging.html# full.date" title="Full Date">Section 3.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) to simplify the process of date comparison. Proxies and gateways from other protocols <em class="bcp14">SHOULD</em> ensure that any Date header field present in a message conforms to one of the HTTP/1.1 formats and rewrite the date if necessary.1650 <p id="rfc.section.A.3.p.1">HTTP/1.1 uses a restricted set of date formats (<a href="p1-messaging.html#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.16"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) to simplify the process of date comparison. Proxies and gateways from other protocols <em class="bcp14">SHOULD</em> ensure that any Date header field present in a message conforms to one of the HTTP/1.1 formats and rewrite the date if necessary. 1651 1651 </p> 1652 1652 <h2 id="rfc.section.A.4"><a href="#rfc.section.A.4">A.4</a> <a id="introduction.of.content-encoding" href="#introduction.of.content-encoding">Introduction of Content-Encoding</a></h2> … … 2059 2059 <li class="indline1"><em>Section 1.2.2</em> <a class="iref" href="#rfc.xref.Part1.2">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.2.1</a></li> 2060 2060 <li class="indline1"><em>Section 2.1</em> <a class="iref" href="#rfc.xref.Part1.6">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.9">1.2.2</a></li> 2061 <li class="indline1"><em>Section 3.2 .1</em> <a class="iref" href="#rfc.xref.Part1.16">A.3</a></li>2061 <li class="indline1"><em>Section 3.2</em> <a class="iref" href="#rfc.xref.Part1.16">A.3</a></li> 2062 2062 <li class="indline1"><em>Section 3.5</em> <a class="iref" href="#rfc.xref.Part1.10">1.2.2</a>, <a class="iref" href="#rfc.xref.Part1.14">5.1</a>, <a class="iref" href="#rfc.xref.Part1.15">5.3</a></li> 2063 2063 <li class="indline1"><em>Section 4.2</em> <a class="iref" href="#rfc.xref.Part1.8">1.2.2</a></li> -
draft-ietf-httpbis/latest/p3-payload.xml
r577 r580 30 30 <!ENTITY message-headers "<xref target='Part1' x:rel='#message.headers' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 31 31 <!ENTITY multipart-byteranges "<xref target='Part5' x:rel='#internet.media.type.multipart.byteranges' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 32 <!ENTITY full-date "<xref target='Part1' x:rel='# full.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">32 <!ENTITY full-date "<xref target='Part1' x:rel='#date.time.formats.full.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 33 33 <!ENTITY qvalue "<xref target='Part1' x:rel='#quality.values' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 34 34 <!ENTITY uri "<xref target='Part1' x:rel='#uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> -
draft-ietf-httpbis/latest/p4-conditional.html
r573 r580 467 467 <tr> 468 468 <td class="header left"></td> 469 <td class="header right">May 1 , 2009</td>469 <td class="header right">May 10, 2009</td> 470 470 </tr> 471 471 </table> … … 602 602 </pre><h3 id="rfc.section.1.2.2"><a href="#rfc.section.1.2.2">1.2.2</a> <a id="abnf.dependencies" href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h3> 603 603 <p id="rfc.section.1.2.2.p.1">The ABNF rules below are defined in other parts:</p> 604 <div id="rfc.figure.u.2"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html# full.date" title="Full Date">Section 3.2.1</a>>604 <div id="rfc.figure.u.2"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 3.2</a>> 605 605 </pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> <a id="entity.tags" href="#entity.tags">Entity Tags</a></h1> 606 606 <p id="rfc.section.2.p.1">Entity tags are used for comparing two or more entities from the same requested resource. HTTP/1.1 uses entity tags in the … … 1161 1161 <a href="#header.etag" class="smpl">ETag-v</a> = entity-tag 1162 1162 1163 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in [Part1], Section 3.2 .1>1163 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in [Part1], Section 3.2> 1164 1164 1165 1165 <a href="#header.if-match" class="smpl">If-Match</a> = "If-Match:" OWS If-Match-v … … 1327 1327 <li class="indline1"><em>Section 1.2</em> <a class="iref" href="#rfc.xref.Part1.1">1.2</a></li> 1328 1328 <li class="indline1"><em>Section 1.2.2</em> <a class="iref" href="#rfc.xref.Part1.2">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.2.1</a></li> 1329 <li class="indline1"><em>Section 3.2 .1</em> <a class="iref" href="#rfc.xref.Part1.5">1.2.2</a></li>1329 <li class="indline1"><em>Section 3.2</em> <a class="iref" href="#rfc.xref.Part1.5">1.2.2</a></li> 1330 1330 <li class="indline1"><em>Section 8.3.1</em> <a class="iref" href="#rfc.xref.Part1.6">3.1</a></li> 1331 1331 <li class="indline1"><em>Section 8.3</em> <a class="iref" href="#rfc.xref.Part1.7">3.1</a></li> -
draft-ietf-httpbis/latest/p4-conditional.xml
r573 r580 25 25 <!ENTITY header-vary "<xref target='Part6' x:rel='#header.vary' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 26 26 <!ENTITY clockless "<xref target='Part1' x:rel='#clockless.origin.server.operation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 27 <!ENTITY full-date "<xref target='Part1' x:rel='# full.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">27 <!ENTITY full-date "<xref target='Part1' x:rel='#date.time.formats.full.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 28 28 ]> 29 29 <?rfc toc="yes" ?> … … 1394 1394 <x:ref>ETag-v</x:ref> = entity-tag 1395 1395 1396 <x:ref>HTTP-date</x:ref> = <HTTP-date, defined in [Part1], Section 3.2 .1>1396 <x:ref>HTTP-date</x:ref> = <HTTP-date, defined in [Part1], Section 3.2> 1397 1397 1398 1398 <x:ref>If-Match</x:ref> = "If-Match:" OWS If-Match-v -
draft-ietf-httpbis/latest/p5-range.html
r576 r580 467 467 <tr> 468 468 <td class="header left"></td> 469 <td class="header right">May 6, 2009</td>469 <td class="header right">May 10, 2009</td> 470 470 </tr> 471 471 </table> … … 606 606 </pre><h3 id="rfc.section.1.2.2"><a href="#rfc.section.1.2.2">1.2.2</a> <a id="abnf.dependencies" href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h3> 607 607 <p id="rfc.section.1.2.2.p.1">The ABNF rules below are defined in other parts:</p> 608 <div id="rfc.figure.u.2"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html# full.date" title="Full Date">Section 3.2.1</a>>608 <div id="rfc.figure.u.2"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 3.2</a>> 609 609 </pre><div id="rfc.figure.u.3"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">entity-tag</a> = <entity-tag, defined in <a href="#Part4" id="rfc.xref.Part4.1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#entity.tags" title="Entity Tags">Section 2</a>> 610 610 </pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> <a id="range.units" href="#range.units">Range Units</a></h1> … … 1110 1110 <a href="#header.content-range" class="smpl">Content-Range-v</a> = content-range-spec 1111 1111 1112 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in [Part1], Section 3.2 .1>1112 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in [Part1], Section 3.2> 1113 1113 1114 1114 <a href="#header.if-range" class="smpl">If-Range</a> = "If-Range:" OWS If-Range-v … … 1313 1313 <li class="indline1"><em>Section 1.2</em> <a class="iref" href="#rfc.xref.Part1.1">1.2</a></li> 1314 1314 <li class="indline1"><em>Section 1.2.2</em> <a class="iref" href="#rfc.xref.Part1.2">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.2.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.2.1</a></li> 1315 <li class="indline1"><em>Section 3.2 .1</em> <a class="iref" href="#rfc.xref.Part1.5">1.2.2</a></li>1315 <li class="indline1"><em>Section 3.2</em> <a class="iref" href="#rfc.xref.Part1.5">1.2.2</a></li> 1316 1316 </ul> 1317 1317 </li> -
draft-ietf-httpbis/latest/p5-range.xml
r576 r580 18 18 <!ENTITY notation-abnf "<xref target='Part1' x:rel='#notation.abnf' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 19 19 <!ENTITY basic-rules "<xref target='Part1' x:rel='#basic.rules' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 20 <!ENTITY full-date "<xref target='Part1' x:rel='# full.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">20 <!ENTITY full-date "<xref target='Part1' x:rel='#date.time.formats.full.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 21 21 <!ENTITY messaging "<xref target='Part1' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 22 22 <!ENTITY entity-tags "<xref target='Part4' x:rel='#entity.tags' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> … … 1405 1405 <x:ref>Content-Range-v</x:ref> = content-range-spec 1406 1406 1407 <x:ref>HTTP-date</x:ref> = <HTTP-date, defined in [Part1], Section 3.2 .1>1407 <x:ref>HTTP-date</x:ref> = <HTTP-date, defined in [Part1], Section 3.2> 1408 1408 1409 1409 <x:ref>If-Range</x:ref> = "If-Range:" OWS If-Range-v -
draft-ietf-httpbis/latest/p6-cache.html
r576 r580 468 468 <tr> 469 469 <td class="header left"></td> 470 <td class="header right">May 6, 2009</td>470 <td class="header right">May 10, 2009</td> 471 471 </tr> 472 472 </table> … … 687 687 <p id="rfc.section.1.4.2.p.1">The ABNF rules below are defined in other parts:</p> 688 688 <div id="rfc.figure.u.2"></div><pre class="inline"> <a href="#abnf.dependencies" class="smpl">field-name</a> = <field-name, defined in <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#message.headers" title="Message Headers">Section 4.2</a>> 689 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html# full.date" title="Full Date">Section 3.2.1</a>>689 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 3.2</a>> 690 690 <a href="#abnf.dependencies" class="smpl">port</a> = <port, defined in <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#uri" title="Uniform Resource Identifiers">Section 2.1</a>> 691 691 <a href="#abnf.dependencies" class="smpl">pseudonym</a> = <pseudonym, defined in <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.via" title="Via">Section 8.9</a>> … … 1185 1185 that time. 1186 1186 </p> 1187 <p id="rfc.section.3.3.p.3">The field-value is an absolute date and time as defined by HTTP-date in <a href="p1-messaging.html# full.date" title="Full Date">Section 3.2.1</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>; it <em class="bcp14">MUST</em> be sent in rfc1123-date format.1187 <p id="rfc.section.3.3.p.3">The field-value is an absolute date and time as defined by HTTP-date in <a href="p1-messaging.html#date.time.formats.full.date" title="Date/Time Formats: Full Date">Section 3.2</a> of <a href="#Part1" id="rfc.xref.Part1.13"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>; it <em class="bcp14">MUST</em> be sent in rfc1123-date format. 1188 1188 </p> 1189 1189 <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span> <a href="#header.expires" class="smpl">Expires</a> = "Expires" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.expires" class="smpl">Expires-v</a> … … 1561 1561 <a href="#header.expires" class="smpl">Expires-v</a> = HTTP-date 1562 1562 1563 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in [Part1], Section 3.2 .1>1563 <a href="#abnf.dependencies" class="smpl">HTTP-date</a> = <HTTP-date, defined in [Part1], Section 3.2> 1564 1564 1565 1565 <a href="#core.rules" class="smpl">OWS</a> = <OWS, defined in [Part1], Section 1.2.2> … … 1856 1856 <li class="indline1"><em>Section 1.2.2</em> <a class="iref" href="#rfc.xref.Part1.2">1.4.1</a>, <a class="iref" href="#rfc.xref.Part1.3">1.4.1</a>, <a class="iref" href="#rfc.xref.Part1.4">1.4.1</a>, <a class="iref" href="#rfc.xref.Part1.5">1.4.1</a></li> 1857 1857 <li class="indline1"><em>Section 2.1</em> <a class="iref" href="#rfc.xref.Part1.8">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.10">1.4.2</a></li> 1858 <li class="indline1"><em>Section 3.2 .1</em> <a class="iref" href="#rfc.xref.Part1.7">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.13">3.3</a></li>1858 <li class="indline1"><em>Section 3.2</em> <a class="iref" href="#rfc.xref.Part1.7">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.13">3.3</a></li> 1859 1859 <li class="indline1"><em>Section 4.2</em> <a class="iref" href="#rfc.xref.Part1.6">1.4.2</a>, <a class="iref" href="#rfc.xref.Part1.12">2.6</a></li> 1860 1860 <li class="indline1"><em>Section 8.3</em> <a class="iref" href="#rfc.xref.Part1.11">2.3.2</a></li> -
draft-ietf-httpbis/latest/p6-cache.xml
r576 r580 23 23 <!ENTITY combining-byte-ranges "<xref target='Part5' x:rel='#combining.byte.ranges' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 24 24 <!ENTITY entity-length "<xref target='Part3' x:rel='#entity.length' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 25 <!ENTITY full-date "<xref target='Part1' x:rel='# full.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">25 <!ENTITY full-date "<xref target='Part1' x:rel='#date.time.formats.full.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 26 26 <!ENTITY header-authorization "<xref target='Part7' x:rel='#header.authorization' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 27 27 <!ENTITY header-connection "<xref target='Part1' x:rel='#header.connection' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> … … 2118 2118 <x:ref>Expires-v</x:ref> = HTTP-date 2119 2119 2120 <x:ref>HTTP-date</x:ref> = <HTTP-date, defined in [Part1], Section 3.2 .1>2120 <x:ref>HTTP-date</x:ref> = <HTTP-date, defined in [Part1], Section 3.2> 2121 2121 2122 2122 <x:ref>OWS</x:ref> = <OWS, defined in [Part1], Section 1.2.2>
Note: See TracChangeset
for help on using the changeset viewer.