- From: Roy T. Fielding <fielding@kiwi.ICS.UCI.EDU>
- Date: Fri, 18 Apr 1997 11:02:06 -0700
- To: rlgray@raleigh.ibm.com
- Cc: HTTP Working Group <http-wg@cuckoo.hpl.hp.com>
These changes look fine to me, and match how we implemented 100 in Apache 1.2b. .....Roy >STATUS100 Message transmission requirements may need clarification (rlgray) >------------------------------------------------------------------------------ > >10.1 Informational 1xx > >Is: >--- >This class of status code indicates a provisional response, consisting only >of the Status-Line and optional headers, and is terminated by an empty line. > >Proposed: >--------- >This class of status code indicates a provisional response, consisting only >of the Status-Line and optional headers, and is terminated by an empty line. >| There are no required headers for this class of status codes. > >------------------------------------------------------------------------------ > >14.19 Date > >Is: >--- >However, since the date--as it is believed by the origin--is important for >evaluating cached responses, origin servers MUST include a Date header field >in all responses. > >Proposed: >--------- >However, since the date--as it is believed by the origin--is important for >evaluating cached responses, origin servers MUST include a Date header field >| in all responses, except those with 1xx status. >
Received on Friday, 18 April 1997 11:22:10 UTC