Changeset 1047 for draft-ietf-httpbis/latest
- Timestamp:
- 22/10/10 09:55:14 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r1045 r1047 2072 2072 a Date. 2073 2073 </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 even2075 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). 2076 2076 </p> 2077 2077 <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 … … 3458 3458 </li> 3459 3459 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/221">http://tools.ietf.org/wg/httpbis/trac/ticket/221</a>>: "effective request URI: handling of missing host in HTTP/1.0" 3460 </li> 3461 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/248">http://tools.ietf.org/wg/httpbis/trac/ticket/248</a>>: "confusing Date requirements for clients" 3460 3462 </li> 3461 3463 </ul> -
draft-ietf-httpbis/latest/p1-messaging.xml
r1045 r1047 3005 3005 </t> 3006 3006 <t> 3007 Clients &SHOULD; only send a Date header field in messages that include3008 a payload, as is usually the case for PUT and POST requests, and even3009 then it is optional. A client without a clock &MUST-NOT; send a Date3010 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). 3011 3011 </t> 3012 3012 <t> … … 5664 5664 "effective request URI: handling of missing host in HTTP/1.0" 5665 5665 </t> 5666 <t> 5667 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/248"/>: 5668 "confusing Date requirements for clients" 5669 </t> 5666 5670 </list> 5667 5671 </t>
Note: See TracChangeset
for help on using the changeset viewer.