Ignore:
Timestamp:
Jan 4, 2013, 2:29:06 AM (7 years ago)
Author:
fielding@…
Message:

Yet another attempt to explain HTTP-date, remove redundant requirements in sections that use HTTP-date, and correct some inconsistent requirements regarding time zones; related to #375 and [2077]

File:
1 edited

Legend:

Unmodified
Added
Removed

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

    r2080 r2082  
    449449  }
    450450  @bottom-center {
    451        content: "Expires July 6, 2013";
     451       content: "Expires July 8, 2013";
    452452  }
    453453  @bottom-right {
    … …  
    495495      <meta name="dct.creator" content="Reschke, J. F.">
    496496      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    497       <meta name="dct.issued" scheme="ISO8601" content="2013-01-02">
     497      <meta name="dct.issued" scheme="ISO8601" content="2013-01-04">
    498498      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    499499      <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.">
    … …  
    523523            <tr>
    524524               <td class="left">Intended status: Standards Track</td>
    525                <td class="right">January 2, 2013</td>
     525               <td class="right">January 4, 2013</td>
    526526            </tr>
    527527            <tr>
    528                <td class="left">Expires: July 6, 2013</td>
     528               <td class="left">Expires: July 8, 2013</td>
    529529               <td class="right"></td>
    530530            </tr>
    … …  
    554554         in progress”.
    555555      </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>
    557557      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    558558      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    … …  
    28042804      <h3 id="rfc.section.7.1.1"><a href="#rfc.section.7.1.1">7.1.1</a>&nbsp;<a id="origination.date" href="#origination.date">Origination Date</a></h3>
    28052805      <h4 id="rfc.section.7.1.1.1"><a href="#rfc.section.7.1.1.1">7.1.1.1</a>&nbsp;<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
     2815Sun 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">
    28182823         <p id="rfc.section.7.1.1.1.p.7">                    Preferred format:</p>
    28192824      </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 in
    2822   ; <a href="http://tools.ietf.org/html/rfc1123#section-5.2.14">Section 5.2.14</a> of <a href="#RFC1123" id="rfc.xref.RFC1123.2"><cite title="Requirements for Internet Hosts - Application and Support">[RFC1123]</cite></a>
     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>
    28232828 
    28242829  <a href="#preferred.date.format" class="smpl">day-name</a>     = %x4D.6F.6E ; "Mon", case-sensitive
    … …  
    28482853  <a href="#preferred.date.format" class="smpl">year</a>         = 4<a href="#imported.abnf" class="smpl">DIGIT</a>
    28492854
    2850   <a href="#preferred.date.format" class="smpl">GMT</a>   = %x47.4D.54 ; "GMT", case-sensitive
     2855  <a href="#preferred.date.format" class="smpl">GMT</a>          = %x47.4D.54 ; "GMT", case-sensitive
    28512856
    28522857  <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:59
     2858               ; 00:00:00 - 23:59:60 (leap second)
    28542859                 
    28552860  <a href="#preferred.date.format" class="smpl">hour</a>         = 2<a href="#imported.abnf" class="smpl">DIGIT</a>               
    28562861  <a href="#preferred.date.format" class="smpl">minute</a>       = 2<a href="#imported.abnf" class="smpl">DIGIT</a>               
    28572862  <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>
    28622865      </div>
    28632866      <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>
    28642867</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>
    28652868  <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-sensitive
    2869          / %x54.75.65.73.64.61.79 ; "Tuesday", case-sensitive
     2869               ; 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
    28702873         / %x57.65.64.6E.65.73.64.61.79 ; "Wednesday", case-sensitive
    2871          / %x54.68.75.72.73.64.61.79 ; "Thursday", case-sensitive
    2872          / %x46.72.69.64.61.79 ; "Friday", case-sensitive
    2873          / %x53.61.74.75.72.64.61.79 ; "Saturday", case-sensitive
    2874          / %x53.75.6E.64.61.79 ; "Sunday", case-sensitive
     2874         / %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
    28752878</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>
    28762879  <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.
    28812889      </p>
    28822890      <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.
    28902893         </p>
    28912894      </div>
    … …  
    28932896      <h4 id="rfc.section.7.1.1.2"><a href="#rfc.section.7.1.1.2">7.1.1.2</a>&nbsp;<a id="header.date" href="#header.date">Date</a></h4>
    28942897      <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&nbsp;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&nbsp;7.1.1.1</a>.
    28962899      </p>
    28972900      <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>
    … …  
    29022905         message origination.
    29032906      </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.
    29062909      </p>
    29072910      <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
    … …  
    39513954         </tr>
    39523955         <tr>
    3953             <td class="reference"><b id="RFC1123">[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&nbsp;3, RFC&nbsp;1123, October&nbsp;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&nbsp;1305, March&nbsp;1992.
    39553958            </td>
    39563959         </tr>
    … …  
    40564059      </div>
    40574060      <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<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,
    40594062         RFC 2045 discusses mail, and HTTP has a few features that are different from those described in MIME. These differences were
    40604063         carefully chosen to optimize performance over binary connections, to allow greater freedom in the use of new media types,
    … …  
    42524255<a href="#preferred.date.format" class="smpl">GMT</a> = %x47.4D.54 ; GMT
    42534256
    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
    42554260
    42564261<a href="#header.location" class="smpl">Location</a> = URI-reference
    … …  
    43464351<a href="#quality.values" class="smpl">qvalue</a> = ( "0" [ "." *3DIGIT ] ) / ( "1" [ "." *3"0" ] )
    43474352
    4348 <a href="#preferred.date.format" class="smpl">rfc1123-date</a> = day-name "," SP date1 SP time-of-day SP GMT
    43494353<a href="#obsolete.date.formats" class="smpl">rfc850-date</a> = day-name-l "," SP date2 SP time-of-day SP GMT
    43504354
    … …  
    45194523                        <li><tt>hour</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.43"><b>7.1.1.1</b></a></li>
    45204524                        <li><tt>HTTP-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.39"><b>7.1.1.1</b></a></li>
     4525                        <li><tt>IMF-fixdate</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.40"><b>7.1.1.1</b></a></li>
    45214526                        <li><tt>language-range</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.33"><b>5.3.5</b></a></li>
    45224527                        <li><tt>language-tag</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.12"><b>3.1.3.1</b></a></li>
    … …  
    45364541                        <li><tt>Referer</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.35"><b>5.5.2</b></a></li>
    45374542                        <li><tt>Retry-After</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.57"><b>7.1.3</b></a></li>
    4538                         <li><tt>rfc1123-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.40"><b>7.1.1.1</b></a></li>
    45394543                        <li><tt>rfc850-date</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.53"><b>7.1.1.1</b></a></li>
    45404544                        <li><tt>second</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.45"><b>7.1.1.1</b></a></li>
    … …  
    46584662                  <li><em>REST</em>&nbsp;&nbsp;<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>
    46594663                  <li>Retry-After header field&nbsp;&nbsp;<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>&nbsp;&nbsp;<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>&nbsp;&nbsp;<a href="#rfc.xref.RFC1123.2">7.1.1.1</a></li>
    4662                      </ul>
    4663                   </li>
     4664                  <li><em>RFC1305</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1305.1">7.1.1.1</a>, <a href="#RFC1305"><b>11.2</b></a></li>
    46644665                  <li><em>RFC1945</em>&nbsp;&nbsp;<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>
    46654666                        <li><em>Section 9.3</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC1945.1">6.4</a></li>
    … …  
    47224723                     </ul>
    47234724                  </li>
    4724                   <li><em>RFC5322</em>&nbsp;&nbsp;<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>&nbsp;&nbsp;<a href="#rfc.xref.RFC5322.3">7.1.1.1</a></li>
     4725                  <li><em>RFC5322</em>&nbsp;&nbsp;<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>&nbsp;&nbsp;<a href="#rfc.xref.RFC5322.4">7.1.1.1</a>, <a href="#rfc.xref.RFC5322.5">7.1.1.1</a></li>
    47264727                        <li><em>Section 3.4</em>&nbsp;&nbsp;<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>&nbsp;&nbsp;<a href="#rfc.xref.RFC5322.4">7.1.1.2</a></li>
     4728                        <li><em>Section 3.6.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5322.6">7.1.1.2</a></li>
    47284729                     </ul>
    47294730                  </li>
Note: See TracChangeset for help on using the changeset viewer.