* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Changeset 1047


Ignore:
Timestamp:
2010-10-22 02:55:14 (4 years ago)
Author:
julian.reschke@gmx.de
Message:

rephrase client requirements for Date header field (addresses #248)

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.html

    r1045 r1047  
    20722072         a Date. 
    20732073      </p> 
    2074       <p id="rfc.section.9.3.p.7">Clients <em class="bcp14">SHOULD</em> only send a Date header field in messages that include a payload, as is usually the case for PUT and POST requests, and even 
    2075          then it is optional. A client without a clock <em class="bcp14">MUST NOT</em> send a Date header field in a request. 
     2074      <p id="rfc.section.9.3.p.7">Clients can use the Date header field as well; in order to keep request messages small, they are advised not to include it 
     2075         when it doesn't convey any useful information (as it is usually the case for requests that do not contain a payload). 
    20762076      </p> 
    20772077      <p id="rfc.section.9.3.p.8">The HTTP-date sent in a Date header field <em class="bcp14">SHOULD NOT</em> represent a date and time subsequent to the generation of the message. It <em class="bcp14">SHOULD</em> represent the best available approximation of the date and time of message generation, unless the implementation has no means 
     
    34583458         </li> 
    34593459         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/221">http://tools.ietf.org/wg/httpbis/trac/ticket/221</a>&gt;: "effective request URI: handling of missing host in HTTP/1.0" 
     3460         </li> 
     3461         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/248">http://tools.ietf.org/wg/httpbis/trac/ticket/248</a>&gt;: "confusing Date requirements for clients" 
    34603462         </li> 
    34613463      </ul> 
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r1045 r1047  
    30053005</t> 
    30063006<t> 
    3007    Clients &SHOULD; only send a Date header field in messages that include 
    3008    a payload, as is usually the case for PUT and POST requests, and even 
    3009    then it is optional. A client without a clock &MUST-NOT; send a Date 
    3010    header field in a request. 
     3007   Clients can use the Date header field as well; in order to keep request 
     3008   messages small, they are advised not to include it when it doesn't convey 
     3009   any useful information (as it is usually the case for requests that do not 
     3010   contain a payload). 
    30113011</t> 
    30123012<t> 
     
    56645664      "effective request URI: handling of missing host in HTTP/1.0" 
    56655665    </t> 
     5666    <t> 
     5667      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/248"/>: 
     5668      "confusing Date requirements for clients" 
     5669    </t> 
    56665670  </list> 
    56675671</t> 
Note: See TracChangeset for help on using the changeset viewer.