W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2012

Caching unsafe methods - p6 overview clarification

From: Mark Nottingham <mnot@mnot.net>
Date: Tue, 10 Jul 2012 10:34:41 +1000
Message-Id: <E3ED0593-0085-43DC-AD02-E8B9A62D3A58@mnot.net>
To: HTTP Working Group <ietf-http-wg@w3.org>
p6 section 2 <https://svn.tools.ietf.org/svn/wg/httpbis/draft-ietf-httpbis/latest/p6-cache.html#caching.overview> says:

> However, it is also possible to cache negative results (e.g., 404 (Not Found), incomplete results (e.g., 206 (Partial Content)), and responses to safe methods other than GET if the method's definition allows such caching and defines something suitable for use as a cache key.

"safe" here is misleading; we don't restrict the *potential* for responses to unsafe methods from being cached (e.g., see POST).

I think this is just a glitch from a rewrite of the intro; removing the word "safe" here.

--
Mark Nottingham   http://www.mnot.net/
Received on Tuesday, 10 July 2012 00:35:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 10 July 2012 00:35:17 GMT