Changeset 2082 for draft-ietf-httpbis/latest/p2-semantics.html
- Timestamp:
- 04/01/13 10:29:06 (9 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r2080 r2082 449 449 } 450 450 @bottom-center { 451 content: "Expires July 6, 2013";451 content: "Expires July 8, 2013"; 452 452 } 453 453 @bottom-right { … … 495 495 <meta name="dct.creator" content="Reschke, J. F."> 496 496 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 497 <meta name="dct.issued" scheme="ISO8601" content="2013-01-0 2">497 <meta name="dct.issued" scheme="ISO8601" content="2013-01-04"> 498 498 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 499 499 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation."> … … 523 523 <tr> 524 524 <td class="left">Intended status: Standards Track</td> 525 <td class="right">January 2, 2013</td>525 <td class="right">January 4, 2013</td> 526 526 </tr> 527 527 <tr> 528 <td class="left">Expires: July 6, 2013</td>528 <td class="left">Expires: July 8, 2013</td> 529 529 <td class="right"></td> 530 530 </tr> … … 554 554 in progress”. 555 555 </p> 556 <p>This Internet-Draft will expire on July 6, 2013.</p>556 <p>This Internet-Draft will expire on July 8, 2013.</p> 557 557 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 558 558 <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 2804 2804 <h3 id="rfc.section.7.1.1"><a href="#rfc.section.7.1.1">7.1.1</a> <a id="origination.date" href="#origination.date">Origination Date</a></h3> 2805 2805 <h4 id="rfc.section.7.1.1.1"><a href="#rfc.section.7.1.1.1">7.1.1.1</a> <a id="http.date" href="#http.date">Date/Time Formats</a></h4> 2806 <p id="rfc.section.7.1.1.1.p.1">HTTP has historically allowed three different formats for date/time stamps. However, the preferred format is a fixed-length 2807 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>: 2808 </p> 2809 <div id="rfc.figure.u.42"></div><pre class="text">Sun, 06 Nov 1994 08:49:37 GMT ; RFC 1123 2810 </pre><p id="rfc.section.7.1.1.1.p.3">The other formats are described here only for compatibility with obsolete implementations.</p> 2811 <div id="rfc.figure.u.43"></div><pre class="text">Sunday, 06-Nov-94 08:49:37 GMT ; obsolete RFC 850 format 2812 Sun Nov 6 08:49:37 1994 ; ANSI C's asctime() format 2813 </pre><p id="rfc.section.7.1.1.1.p.5">HTTP always represents dates as an instance of Coordinated Universal Time (UTC), without exception; the first two formats 2814 indicate UTC as "GMT" in the three-letter abbreviation for time zone. Recipients <em class="bcp14">MAY</em> assume UTC even if the time zone abbreviation is missing, invalid, or might indicate some other time zone. 2815 </p> 2816 <div id="rfc.figure.u.44"></div><pre class="inline"><span id="rfc.iref.g.39"></span> <a href="#http.date" class="smpl">HTTP-date</a> = <a href="#preferred.date.format" class="smpl">rfc1123-date</a> / <a href="#obsolete.date.formats" class="smpl">obs-date</a> 2817 </pre><div id="preferred.date.format"> 2806 <p id="rfc.section.7.1.1.1.p.1">Prior to 1995, there were three different formats commonly used by servers to communicate timestamps. For compatibility with 2807 old implementations, all three are defined here. The preferred format is a fixed-length and single-zone subset of the date 2808 and time specification used by the Internet Message Format <a href="#RFC5322" id="rfc.xref.RFC5322.3"><cite title="Internet Message Format">[RFC5322]</cite></a>. 2809 </p> 2810 <div id="rfc.figure.u.42"></div><pre class="inline"><span id="rfc.iref.g.39"></span> <a href="#http.date" class="smpl">HTTP-date</a> = <a href="#preferred.date.format" class="smpl">IMF-fixdate</a> / <a href="#obsolete.date.formats" class="smpl">obs-date</a> 2811 </pre><div id="rfc.figure.u.43"></div> 2812 <p>An example of the preferred format is</p><pre class="text">Sun, 06 Nov 1994 08:49:37 GMT ; IMF-fixdate 2813 </pre><div id="rfc.figure.u.44"></div> 2814 <p>Examples of the two obsolete formats are</p><pre class="text">Sunday, 06-Nov-94 08:49:37 GMT ; obsolete RFC 850 format 2815 Sun Nov 6 08:49:37 1994 ; ANSI C's asctime() format 2816 </pre><p id="rfc.section.7.1.1.1.p.5">A recipient that parses a timestamp value in an HTTP header field <em class="bcp14">MUST</em> accept all three formats. A sender <em class="bcp14">MUST</em> generate the IMF-fixdate format when sending an HTTP-date value in a header field. 2817 </p> 2818 <p id="rfc.section.7.1.1.1.p.6">An HTTP-date value represents time as an instance of Coordinated Universal Time (UTC). The first two formats indicate UTC 2819 by the three-letter abbreviation for Greenwich Mean Time, "GMT", a predecessor of the UTC name; values in the asctime format 2820 are assumed to be in UTC. A sender that generates HTTP-date values from a local clock ought to use NTP (<a href="#RFC1305" id="rfc.xref.RFC1305.1"><cite title="Network Time Protocol (Version 3) Specification, Implementation">[RFC1305]</cite></a>) or some similar protocol to synchronize its clock to UTC. 2821 </p> 2822 <div id="preferred.date.format"> 2818 2823 <p id="rfc.section.7.1.1.1.p.7"> Preferred format:</p> 2819 2824 </div> 2820 <div id="rfc.figure.u.45"></div><pre class="inline"><span id="rfc.iref.g.40"></span><span id="rfc.iref.g.41"></span><span id="rfc.iref.g.42"></span><span id="rfc.iref.g.43"></span><span id="rfc.iref.g.44"></span><span id="rfc.iref.g.45"></span><span id="rfc.iref.g.46"></span><span id="rfc.iref.g.47"></span><span id="rfc.iref.g.48"></span><span id="rfc.iref.g.49"></span><span id="rfc.iref.g.50"></span><span id="rfc.iref.g.51"></span> <a href="#preferred.date.format" class="smpl"> rfc1123-date</a>= <a href="#preferred.date.format" class="smpl">day-name</a> "," <a href="#imported.abnf" class="smpl">SP</a> date1 <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">GMT</a>2821 ; fixed length subset of the format defined in2822 ; <a href="http://tools.ietf.org/html/rfc 1123#section-5.2.14">Section 5.2.14</a> of <a href="#RFC1123" id="rfc.xref.RFC1123.2"><cite title="Requirements for Internet Hosts - Application and Support">[RFC1123]</cite></a>2825 <div id="rfc.figure.u.45"></div><pre class="inline"><span id="rfc.iref.g.40"></span><span id="rfc.iref.g.41"></span><span id="rfc.iref.g.42"></span><span id="rfc.iref.g.43"></span><span id="rfc.iref.g.44"></span><span id="rfc.iref.g.45"></span><span id="rfc.iref.g.46"></span><span id="rfc.iref.g.47"></span><span id="rfc.iref.g.48"></span><span id="rfc.iref.g.49"></span><span id="rfc.iref.g.50"></span><span id="rfc.iref.g.51"></span> <a href="#preferred.date.format" class="smpl">IMF-fixdate</a> = <a href="#preferred.date.format" class="smpl">day-name</a> "," <a href="#imported.abnf" class="smpl">SP</a> date1 <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">GMT</a> 2826 ; fixed length/zone subset of the format defined in 2827 ; <a href="http://tools.ietf.org/html/rfc5322#section-3.3">Section 3.3</a> of <a href="#RFC5322" id="rfc.xref.RFC5322.4"><cite title="Internet Message Format">[RFC5322]</cite></a> 2823 2828 2824 2829 <a href="#preferred.date.format" class="smpl">day-name</a> = %x4D.6F.6E ; "Mon", case-sensitive … … 2848 2853 <a href="#preferred.date.format" class="smpl">year</a> = 4<a href="#imported.abnf" class="smpl">DIGIT</a> 2849 2854 2850 <a href="#preferred.date.format" class="smpl">GMT</a> = %x47.4D.54 ; "GMT", case-sensitive2855 <a href="#preferred.date.format" class="smpl">GMT</a> = %x47.4D.54 ; "GMT", case-sensitive 2851 2856 2852 2857 <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> 2853 ; 00:00:00 - 23:59:592858 ; 00:00:00 - 23:59:60 (leap second) 2854 2859 2855 2860 <a href="#preferred.date.format" class="smpl">hour</a> = 2<a href="#imported.abnf" class="smpl">DIGIT</a> 2856 2861 <a href="#preferred.date.format" class="smpl">minute</a> = 2<a href="#imported.abnf" class="smpl">DIGIT</a> 2857 2862 <a href="#preferred.date.format" class="smpl">second</a> = 2<a href="#imported.abnf" class="smpl">DIGIT</a> 2858 </pre><p id="rfc.section.7.1.1.1.p.9">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 for the RFC 5322 constructs with the corresponding name (<a href="#RFC5322" id="rfc.xref.RFC5322.3"><cite title="Internet Message Format">[RFC5322]</cite></a>, <a href="http://tools.ietf.org/html/rfc5322#section-3.3">Section 3.3</a>). 2859 </p> 2860 <div id="obsolete.date.formats"> 2861 <p id="rfc.section.7.1.1.1.p.10"> Obsolete formats:</p> 2863 </pre><div id="obsolete.date.formats"> 2864 <p id="rfc.section.7.1.1.1.p.9"> Obsolete formats:</p> 2862 2865 </div> 2863 2866 <div id="rfc.figure.u.46"></div><pre class="inline"><span id="rfc.iref.g.52"></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> 2864 2867 </pre><div id="rfc.figure.u.47"></div><pre class="inline"><span id="rfc.iref.g.53"></span> <a href="#obsolete.date.formats" class="smpl">rfc850-date</a> = <a href="#obsolete.date.formats" class="smpl">day-name-l</a> "," <a href="#imported.abnf" class="smpl">SP</a> <a href="#obsolete.date.formats" class="smpl">date2</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">GMT</a> 2865 2868 <a href="#obsolete.date.formats" class="smpl">date2</a> = <a href="#preferred.date.format" class="smpl">day</a> "-" <a href="#preferred.date.format" class="smpl">month</a> "-" 2<a href="#imported.abnf" class="smpl">DIGIT</a> 2866 ; day-month-year (e.g., 02-Jun-82)2867 2868 <a href="#obsolete.date.formats" class="smpl">day-name-l</a> = %x4D.6F.6E.64.61.79 ; "Monday", case-sensitive2869 / %x54.75.65.73.64.61.79 ; "Tuesday", case-sensitive2869 ; e.g., 02-Jun-82 2870 2871 <a href="#obsolete.date.formats" class="smpl">day-name-l</a> = %x4D.6F.6E.64.61.79 ; "Monday", case-sensitive 2872 / %x54.75.65.73.64.61.79 ; "Tuesday", case-sensitive 2870 2873 / %x57.65.64.6E.65.73.64.61.79 ; "Wednesday", case-sensitive 2871 / %x54.68.75.72.73.64.61.79 ; "Thursday", case-sensitive2872 / %x46.72.69.64.61.79 ; "Friday", case-sensitive2873 / %x53.61.74.75.72.64.61.79 ; "Saturday", case-sensitive2874 / %x53.75.6E.64.61.79 ; "Sunday", case-sensitive2874 / %x54.68.75.72.73.64.61.79 ; "Thursday", case-sensitive 2875 / %x46.72.69.64.61.79 ; "Friday", case-sensitive 2876 / %x53.61.74.75.72.64.61.79 ; "Saturday", case-sensitive 2877 / %x53.75.6E.64.61.79 ; "Sunday", case-sensitive 2875 2878 </pre><div id="rfc.figure.u.48"></div><pre class="inline"><span id="rfc.iref.g.54"></span> <a href="#obsolete.date.formats" class="smpl">asctime-date</a> = <a href="#preferred.date.format" class="smpl">day-name</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#obsolete.date.formats" class="smpl">date3</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">time-of-day</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#preferred.date.format" class="smpl">year</a> 2876 2879 <a href="#obsolete.date.formats" class="smpl">date3</a> = <a href="#preferred.date.format" class="smpl">month</a> <a href="#imported.abnf" class="smpl">SP</a> ( 2<a href="#imported.abnf" class="smpl">DIGIT</a> / ( <a href="#imported.abnf" class="smpl">SP</a> 1<a href="#imported.abnf" class="smpl">DIGIT</a> )) 2877 ; month day (e.g., Jun 2) 2878 </pre><p id="rfc.section.7.1.1.1.p.14">HTTP-date is case sensitive. A sender <em class="bcp14">MUST NOT</em> generate additional whitespace in an HTTP-date beyond that specifically included as SP in the grammar. 2879 </p> 2880 <p id="rfc.section.7.1.1.1.p.15">Recipients that parse a date value <em class="bcp14">MUST</em> accept all three formats (for compatibility with HTTP/1.0). A sender <em class="bcp14">MUST</em> only generate the RFC 1123 format when sending HTTP-date values in header fields. 2880 ; e.g., Jun 2 2881 </pre><p id="rfc.section.7.1.1.1.p.13">HTTP-date is case sensitive. A sender <em class="bcp14">MUST NOT</em> generate additional whitespace in an HTTP-date beyond that specifically included as SP in the grammar. 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 for the Internet Message Format constructs with the corresponding name (<a href="#RFC5322" id="rfc.xref.RFC5322.5"><cite title="Internet Message Format">[RFC5322]</cite></a>, <a href="http://tools.ietf.org/html/rfc5322#section-3.3">Section 3.3</a>). 2882 </p> 2883 <p id="rfc.section.7.1.1.1.p.14">Recipients of a timestamp value in rfc850-date format, which uses a two-digit year, <em class="bcp14">SHOULD</em> interpret a timestamp that appears to be more than 50 years in the future as representing the most recent year in the past 2884 that had the same last two digits. 2885 </p> 2886 <p id="rfc.section.7.1.1.1.p.15">Recipients of timestamp values are encouraged to be robust in parsing timestamps unless otherwise restricted by the field 2887 definition. For example, messages are occasionally forwarded over HTTP from a non-HTTP source that might generate any of the 2888 date and time specifications defined by the Internet Message Format. 2881 2889 </p> 2882 2890 <div class="note" id="rfc.section.7.1.1.1.p.16"> 2883 <p> <b>Note:</b> Recipients of date values are encouraged to be robust in accepting date values that might have been sent by non-HTTP applications, 2884 as is sometimes the case when retrieving or posting messages via proxies/gateways to SMTP or NNTP. 2885 </p> 2886 </div> 2887 <div class="note" id="rfc.section.7.1.1.1.p.17"> 2888 <p> <b>Note:</b> HTTP requirements for the date/time stamp format apply only to their usage within the protocol stream. Clients and servers 2889 are not required to use these formats for user presentation, request logging, etc. 2891 <p> <b>Note:</b> HTTP requirements for the date/time stamp format apply only to their usage within the protocol stream. Implementations are 2892 not required to use these formats for user presentation, request logging, etc. 2890 2893 </p> 2891 2894 </div> … … 2893 2896 <h4 id="rfc.section.7.1.1.2"><a href="#rfc.section.7.1.1.2">7.1.1.2</a> <a id="header.date" href="#header.date">Date</a></h4> 2894 2897 <p id="rfc.section.7.1.1.2.p.1">The "Date" header field represents the date and time at which the message was originated, having the same semantics as the 2895 Origination Date Field (orig-date) defined 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 defined in <a href="#http.date" title="Date/Time Formats">Section 7.1.1.1</a>, though a sender <em class="bcp14">MUST</em> generate a Date value in the rfc1123-date format.2898 Origination Date Field (orig-date) defined 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.6"><cite title="Internet Message Format">[RFC5322]</cite></a>. The field value is an HTTP-date, as defined in <a href="#http.date" title="Date/Time Formats">Section 7.1.1.1</a>. 2896 2899 </p> 2897 2900 <div id="rfc.figure.u.49"></div><pre class="inline"><span id="rfc.iref.g.55"></span> <a href="#header.date" class="smpl">Date</a> = <a href="#http.date" class="smpl">HTTP-date</a> … … 2902 2905 message origination. 2903 2906 </p> 2904 <p id="rfc.section.7.1.1.2.p.6">An origin server <em class="bcp14">MUST NOT</em> send a Date header field if it does not have a clock capable of providing a reasonable approximation of the current time.2905 An origin server <em class="bcp14">MAY</em> send a Date header field if the response is in the <a href="#status.1xx" class="smpl">1xx (Informational)</a> or <a href="#status.5xx" class="smpl">5xx (Server Error)</a> class of status codes. An origin server <em class="bcp14">MUST</em> send a Date header field in all other cases.2907 <p id="rfc.section.7.1.1.2.p.6">An origin server <em class="bcp14">MUST NOT</em> send a Date header field if it does not have a clock capable of providing a reasonable approximation of the current instance 2908 in Coordinated Universal Time. An origin server <em class="bcp14">MAY</em> send a Date header field if the response is in the <a href="#status.1xx" class="smpl">1xx (Informational)</a> or <a href="#status.5xx" class="smpl">5xx (Server Error)</a> class of status codes. An origin server <em class="bcp14">MUST</em> send a Date header field in all other cases. 2906 2909 </p> 2907 2910 <p id="rfc.section.7.1.1.2.p.7">A recipient with a clock that receives a response message without a Date header field <em class="bcp14">MUST</em> record the time it was received and append a corresponding Date header field to the message's header block if it is cached … … 3951 3954 </tr> 3952 3955 <tr> 3953 <td class="reference"><b id="RFC1 123">[RFC1123]</b></td>3954 <td class="top"><a href="mailto: Braden@ISI.EDU" title="University of Southern California (USC), Information Sciences Institute">Braden, R.</a>, “<a href="http://tools.ietf.org/html/rfc1123">Requirements for Internet Hosts - Application and Support</a>”, STD 3, RFC 1123, October 1989.3956 <td class="reference"><b id="RFC1305">[RFC1305]</b></td> 3957 <td class="top"><a href="mailto:mills@udel.edu" title="University of Delaware, Electrical Engineering Department">Mills, D.</a>, “<a href="http://tools.ietf.org/html/rfc1305">Network Time Protocol (Version 3) Specification, Implementation</a>”, RFC 1305, March 1992. 3955 3958 </td> 3956 3959 </tr> … … 4056 4059 </div> 4057 4060 <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a> <a id="differences.between.http.and.mime" href="#differences.between.http.and.mime">Differences between HTTP and MIME</a></h1> 4058 <p id="rfc.section.A.p.1">HTTP/1.1 uses many of the constructs defined for Internet Mail (<a href="#RFC5322" id="rfc.xref.RFC5322. 5"><cite title="Internet Message Format">[RFC5322]</cite></a>) and the Multipurpose Internet Mail Extensions (MIME <a href="#RFC2045" id="rfc.xref.RFC2045.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a>) to allow a message body to be transmitted in an open variety of representations and with extensible mechanisms. However,4061 <p id="rfc.section.A.p.1">HTTP/1.1 uses many of the constructs defined for Internet Mail (<a href="#RFC5322" id="rfc.xref.RFC5322.7"><cite title="Internet Message Format">[RFC5322]</cite></a>) and the Multipurpose Internet Mail Extensions (MIME <a href="#RFC2045" id="rfc.xref.RFC2045.1"><cite title="Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies">[RFC2045]</cite></a>) to allow a message body to be transmitted in an open variety of representations and with extensible mechanisms. However, 4059 4062 RFC 2045 discusses mail, and HTTP has a few features that are different from those described in MIME. These differences were 4060 4063 carefully chosen to optimize performance over binary connections, to allow greater freedom in the use of new media types, … … 4252 4255 <a href="#preferred.date.format" class="smpl">GMT</a> = %x47.4D.54 ; GMT 4253 4256 4254 <a href="#http.date" class="smpl">HTTP-date</a> = rfc1123-date / obs-date 4257 <a href="#http.date" class="smpl">HTTP-date</a> = IMF-fixdate / obs-date 4258 4259 <a href="#preferred.date.format" class="smpl">IMF-fixdate</a> = day-name "," SP date1 SP time-of-day SP GMT 4255 4260 4256 4261 <a href="#header.location" class="smpl">Location</a> = URI-reference … … 4346 4351 <a href="#quality.values" class="smpl">qvalue</a> = ( "0" [ "." *3DIGIT ] ) / ( "1" [ "." *3"0" ] ) 4347 4352 4348 <a href="#preferred.date.format" class="smpl">rfc1123-date</a> = day-name "," SP date1 SP time-of-day SP GMT4349 4353 <a href="#obsolete.date.formats" class="smpl">rfc850-date</a> = day-name-l "," SP date2 SP time-of-day SP GMT 4350 4354 … … 4519 4523 <li><tt>hour</tt> <a href="#rfc.iref.g.43"><b>7.1.1.1</b></a></li> 4520 4524 <li><tt>HTTP-date</tt> <a href="#rfc.iref.g.39"><b>7.1.1.1</b></a></li> 4525 <li><tt>IMF-fixdate</tt> <a href="#rfc.iref.g.40"><b>7.1.1.1</b></a></li> 4521 4526 <li><tt>language-range</tt> <a href="#rfc.iref.g.33"><b>5.3.5</b></a></li> 4522 4527 <li><tt>language-tag</tt> <a href="#rfc.iref.g.12"><b>3.1.3.1</b></a></li> … … 4536 4541 <li><tt>Referer</tt> <a href="#rfc.iref.g.35"><b>5.5.2</b></a></li> 4537 4542 <li><tt>Retry-After</tt> <a href="#rfc.iref.g.57"><b>7.1.3</b></a></li> 4538 <li><tt>rfc1123-date</tt> <a href="#rfc.iref.g.40"><b>7.1.1.1</b></a></li>4539 4543 <li><tt>rfc850-date</tt> <a href="#rfc.iref.g.53"><b>7.1.1.1</b></a></li> 4540 4544 <li><tt>second</tt> <a href="#rfc.iref.g.45"><b>7.1.1.1</b></a></li> … … 4658 4662 <li><em>REST</em> <a href="#rfc.xref.REST.1">3</a>, <a href="#rfc.xref.REST.2">4.1</a>, <a href="#REST"><b>11.2</b></a></li> 4659 4663 <li>Retry-After header field <a href="#rfc.xref.header.retry-after.1">6.6.4</a>, <a href="#rfc.xref.header.retry-after.2">7.1</a>, <a href="#rfc.iref.r.3"><b>7.1.3</b></a>, <a href="#rfc.xref.header.retry-after.3">8.3.2</a></li> 4660 <li><em>RFC1123</em> <a href="#rfc.xref.RFC1123.1">7.1.1.1</a>, <a href="#rfc.xref.RFC1123.2">7.1.1.1</a>, <a href="#RFC1123"><b>11.2</b></a><ul> 4661 <li><em>Section 5.2.14</em> <a href="#rfc.xref.RFC1123.2">7.1.1.1</a></li> 4662 </ul> 4663 </li> 4664 <li><em>RFC1305</em> <a href="#rfc.xref.RFC1305.1">7.1.1.1</a>, <a href="#RFC1305"><b>11.2</b></a></li> 4664 4665 <li><em>RFC1945</em> <a href="#rfc.xref.RFC1945.1">6.4</a>, <a href="#RFC1945"><b>11.2</b></a>, <a href="#rfc.xref.RFC1945.2">B</a><ul> 4665 4666 <li><em>Section 9.3</em> <a href="#rfc.xref.RFC1945.1">6.4</a></li> … … 4722 4723 </ul> 4723 4724 </li> 4724 <li><em>RFC5322</em> <a href="#rfc.xref.RFC5322.1">5.5.1</a>, <a href="#rfc.xref.RFC5322.2">5.5.1</a>, <a href="#rfc.xref.RFC5322.3">7.1.1.1</a>, <a href="#rfc.xref.RFC5322.4">7.1.1. 2</a>, <a href="#RFC5322"><b>11.2</b></a>, <a href="#rfc.xref.RFC5322.5">A</a><ul>4725 <li><em>Section 3.3</em> <a href="#rfc.xref.RFC5322. 3">7.1.1.1</a></li>4725 <li><em>RFC5322</em> <a href="#rfc.xref.RFC5322.1">5.5.1</a>, <a href="#rfc.xref.RFC5322.2">5.5.1</a>, <a href="#rfc.xref.RFC5322.3">7.1.1.1</a>, <a href="#rfc.xref.RFC5322.4">7.1.1.1</a>, <a href="#rfc.xref.RFC5322.5">7.1.1.1</a>, <a href="#rfc.xref.RFC5322.6">7.1.1.2</a>, <a href="#RFC5322"><b>11.2</b></a>, <a href="#rfc.xref.RFC5322.7">A</a><ul> 4726 <li><em>Section 3.3</em> <a href="#rfc.xref.RFC5322.4">7.1.1.1</a>, <a href="#rfc.xref.RFC5322.5">7.1.1.1</a></li> 4726 4727 <li><em>Section 3.4</em> <a href="#rfc.xref.RFC5322.1">5.5.1</a>, <a href="#rfc.xref.RFC5322.2">5.5.1</a></li> 4727 <li><em>Section 3.6.1</em> <a href="#rfc.xref.RFC5322. 4">7.1.1.2</a></li>4728 <li><em>Section 3.6.1</em> <a href="#rfc.xref.RFC5322.6">7.1.1.2</a></li> 4728 4729 </ul> 4729 4730 </li>
Note: See TracChangeset
for help on using the changeset viewer.