Ignore:
Timestamp:
Dec 31, 2012, 9:58:52 PM (7 years ago)
Author:
fielding@…
Message:

(editorial) another attempt to explain GMT as UTC

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r2076 r2077  
    35123512  <x:anchor-alias value="HTTP-date"/>
    35133513<t>
    3514    HTTP applications have historically allowed three different formats
     3514   HTTP has historically allowed three different formats
    35153515   for date/time stamps. However, the preferred format is a fixed-length subset
    35163516   of that defined by <xref target="RFC1123"/>:
     
    35283528</artwork></figure>
    35293529<t>
    3530    HTTP/1.1 clients and servers that parse a date value &MUST; accept
    3531    all three formats (for compatibility with HTTP/1.0), though they &MUST;
    3532    only generate the RFC 1123 format for representing HTTP-date values
    3533    in header fields.
    3534 </t>
    3535 <t>
    3536    All HTTP date/time stamps are represented in Greenwich Mean Time
    3537    (GMT), without exception. For the purposes of HTTP, GMT is exactly
    3538    equal to UTC (Coordinated Universal Time). This is indicated in the
    3539    first two formats by the inclusion of "GMT" as the three-letter
    3540    abbreviation for time zone, and is assumed when reading the
    3541    asctime format. HTTP-date is case sensitive. A sender &MUST-NOT; generate
    3542    additional whitespace in an HTTP-date beyond that specifically included as
    3543    SP in the grammar.
     3530   HTTP always represents dates as an instance of Coordinated Universal Time
     3531   (UTC), without exception; the first two formats indicate UTC as "GMT" in
     3532   the three-letter abbreviation for time zone. Recipients &MAY; assume UTC
     3533   even if the time zone abbreviation is missing, invalid, or might indicate
     3534   some other time zone.
    35443535</t>
    35453536<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="HTTP-date"/>
     
    36363627                 ; month day (e.g., Jun  2)
    36373628</artwork></figure>
     3629<t>
     3630   HTTP-date is case sensitive.
     3631   A sender &MUST-NOT; generate additional whitespace in an HTTP-date beyond
     3632   that specifically included as SP in the grammar.
     3633</t>
     3634<t>
     3635   Recipients that parse a date value &MUST; accept all three formats (for
     3636   compatibility with HTTP/1.0). A sender &MUST; only generate the RFC 1123
     3637   format when sending HTTP-date values in header fields.
     3638</t>
    36383639<x:note>
    36393640  <t>
Note: See TracChangeset for help on using the changeset viewer.