Ignore:
Timestamp:
Dec 31, 2012, 3:02:54 AM (7 years ago)
Author:
fielding@…
Message:

fix several more cases of include being used instead of send or generate, and a few requirements that are simply facts

File:
1 edited

Legend:

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

    r2072 r2073  
    20982098      <p id="rfc.section.5.5.3.p.1">The "User-Agent" header field contains information about the user agent originating the request, which is often used by servers
    20992099         to help identify the scope of reported interoperability problems, to work around or tailor responses to avoid particular user
    2100          agent limitations, and for analytics regarding browser or operating system use. A user agent <em class="bcp14">SHOULD</em> include a User-Agent field in each request unless specifically configured not to do so.
     2100         agent limitations, and for analytics regarding browser or operating system use. A user agent <em class="bcp14">SHOULD</em> send a User-Agent field in each request unless specifically configured not to do so.
    21012101      </p>
    21022102      <div id="rfc.figure.u.38"></div><pre class="inline"><span id="rfc.iref.g.36"></span>  <a href="#header.user-agent" class="smpl">User-Agent</a> = <a href="#header.user-agent" class="smpl">product</a> *( <a href="#imported.abnf" class="smpl">RWS</a> ( <a href="#header.user-agent" class="smpl">product</a> / <a href="#imported.abnf" class="smpl">comment</a> ) )
     
    27262726      <div id="rfc.iref.s.6"></div>
    27272727      <p id="rfc.section.6.6.p.1">The <dfn>5xx (Server Error)</dfn> class of status code indicates that the server is aware that it has erred or is incapable of performing the requested method.
    2728          Except when responding to a HEAD request, the server <em class="bcp14">SHOULD</em> include a representation containing an explanation of the error situation, and whether it is a temporary or permanent condition.
     2728         Except when responding to a HEAD request, the server <em class="bcp14">SHOULD</em> send a representation containing an explanation of the error situation, and whether it is a temporary or permanent condition.
    27292729         User agents <em class="bcp14">SHOULD</em> display any included representation to the user. These response codes are applicable to any request method.
    27302730      </p>
     
    28132813</pre><p id="rfc.section.7.1.1.1.p.5">HTTP/1.1 clients and servers that parse a 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.
    28142814      </p>
    2815       <p id="rfc.section.7.1.1.1.p.6">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
    2816          Universal Time). This is indicated in the first two formats by the inclusion of "GMT" as the three-letter abbreviation for
    2817          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.
     2815      <p id="rfc.section.7.1.1.1.p.6">All HTTP date/time stamps are represented in Greenwich Mean Time (GMT), without exception. For the purposes of HTTP, GMT is
     2816         exactly equal to UTC (Coordinated Universal Time). This is indicated in the first two formats by the inclusion of "GMT" as
     2817         the three-letter abbreviation for time zone, and is assumed when reading the asctime format. HTTP-date is case sensitive.
     2818         A sender <em class="bcp14">MUST NOT</em> generate additional whitespace in an HTTP-date beyond that specifically included as SP in the grammar.
    28182819      </p>
    28192820      <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>
Note: See TracChangeset for help on using the changeset viewer.