W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2013

Requiring proxies to process warn-date

From: Mark Nottingham <mnot@mnot.net>
Date: Wed, 8 May 2013 23:14:09 +1000
Message-Id: <D528E812-45A0-426F-972F-3F4AC6F8DEA7@mnot.net>
To: "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>
In #480, Alex brought this text up in p6:

> If an implementation sends a message with one or more Warning header fields to a receiver whose version is HTTP/1.0 or lower, then the sender must include in each warning-value a warn-date that matches the Date header field in the message.
> 
> If a system receives a message with a warning-value that includes a warn-date, and that warn-date is different from the Date value in the response, then that warning-value must be deleted from the message before storing, forwarding, or using it. (preventing the consequences of naive caching of Warning header fields.) If all of the warning-values are deleted for this reason, the Warning header field must be deleted as well.

My inclination here is to change the first paragraph to begin "If a sender generates a message...", and the second to be "If a recipient receives...", also removing "forwarding" later down.

This is because IME proxies do not do any of this for messages that they aren't caching, and moreover there are whole classes of implementations that won't.

Thoughts?

--
Mark Nottingham   http://www.mnot.net/
Received on Wednesday, 8 May 2013 13:14:39 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:13 UTC