"Clients SHOULD only send a Date header field in messages that include
an entity-body, as in the case of the PUT and POST requests, and even then
it is optional. A client without a clock MUST NOT send a Date header field
in a request.
So I think the parenthetical comment is incorrect.
"Hastings, Tom N" <email@example.com> on 04/27/99 11:27:33 AM
To: Carl Kugler/Boulder/IBM, firstname.lastname@example.org
Subject: RE: IPP> Last Call Comment: Job and Printer time attributes shou
ld be REQ
The suggestion was that the date came in the "incoming" client supplied
header, not the server returned HTTP header. If the parenthetical comment
"(where it is always present)" is not correct, then we can just delete the
From: email@example.com [mailto:firstname.lastname@example.org]
Sent: Tuesday, April 27, 1999 08:50
Subject: Re: IPP> Last Call Comment: Job and Printer time attributes
should be REQ
> However, we could write the requirement such that the IPP/1.1 Printer
> implementation had to attempt to get the time by some means, such as
> the time from a networked NTP Time server, from an incoming HTTP request
> (where it is always present),
I don't think you can count on that. From draft-ietf-http-v11-spec-rev-06,
section 14.18 Date: "If the server does not have a clock that can provide a
reasonable approximation of the current time, its responses MUST NOT
include a Date header field.