- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Wed, 05 Dec 2012 10:17:54 +0100
- To: Barry Leiba <barryleiba@computer.org>
- CC: Martin Thomson <martin.thomson@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>, James M Snell <jasnell@gmail.com>, Mark Nottingham <mnot@mnot.net>
On 2012-12-05 00:08, Barry Leiba wrote: >>>> Another option available to clients is to utilize Request URI query- >>>> string parameters to express preferences. Doing so, however, results >>>> in a variety of issues affecting the cacheability of responses. > ... >> If the intent is to retrieve: >> http://example.com/foo >> with prefer: wait=5, then asking for >> http://example.com/foo?wait=5 >> will result in a cache entry against the latter URI, just as >> http://example.com/foo?wait=3 >> will create another cache entry that are all equally useless to the >> requester pulling down the "unmodified" URI. >> >> Any change needs to be aware of the strict interpretation, but make >> this implication obvious. > > How about this: > > OLD > Doing so, however, results in a variety of issues affecting the > cacheability of responses. > > NEW > But any mechanism that alters the URI can have undesirable effects, > such as when caches record the altered URI. Works for me.
Received on Wednesday, 5 December 2012 09:18:35 UTC