> Mais je crois que l'entête Date est obligatoire
Pas vraiment, car la RFC2616 autorise les serveurs non datés:
14.18 Date
[...]
Origin servers MUST include a Date header field in all responses, except in these cases:
[...]
3. 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. In this case, the rules
in section 14.18.1 MUST be followed.
[...]
14.18.1 Clockless Origin Server Operation
Some origin server implementations might not have a clock available. An origin server without a clock MUST NOT assign Expires or Last- Modified values to a response, unless these values were associated with the resource by a system or user with a reliable clock. It MAY assign an Expires value that is known, at or before server configuration time, to be in the past (this allows "pre-expiration" of responses without storing separate Expires values for each resource).
[^] # Re: Optimisations:
Posté par Moonz . En réponse au journal Mon serveur Web. Évalué à 6.
Pas vraiment, car la RFC2616 autorise les serveurs non datés:
14.18 Date
[...]
Origin servers MUST include a Date header field in all responses, except in these cases:
[...]
3. 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. In this case, the rules
in section 14.18.1 MUST be followed.
[...]
14.18.1 Clockless Origin Server Operation
Some origin server implementations might not have a clock available. An origin server without a clock MUST NOT assign Expires or Last- Modified values to a response, unless these values were associated with the resource by a system or user with a reliable clock. It MAY assign an Expires value that is known, at or before server configuration time, to be in the past (this allows "pre-expiration" of responses without storing separate Expires values for each resource).
(voir http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14(...)