- From: Robert Finean <Rob.Finean@openwave.com>
- Date: Tue, 2 Dec 2008 18:00:01 -0000
- To: "Francois Daoust" <fd@w3.org>, "public-bpwg-ct" <public-bpwg-ct@w3.org>
I meant
Cache-Control: no-cache
and not
Cache-Control: must-revalidate
Thanks,
Rob
-----Original Message-----
<snip />
Cached responses and pagination
<francois> "SHOULD provide a simple means of retrieving a fresh
copy"
rob: if we respect the cache-control: no-cache (or revalidate, or
whatever) that happens when you do a refresh from the handset menu,
there's no need to do anything specific re what you put on the
screen
<snip />
rob: The latter doesn't need to be a link on the page, as long as
cache-control: must-revalidate is observed then there is a simple
means of retrieving a fresh copy.
<snip />
francois: does the use case Rob mentioned (clicking refresh in the
menu) fit the definition of "something provided by the proxy"?
... is this a question of its respecting the simple means provided
by the browser.
yes
edC: Rob said that "the simple means" is "the user clicking a
refresh on their browser triggers the proxy to refetch the content"
francois: yes
... does the guideline embrace this case? I think so
Received on Tuesday, 2 December 2008 18:00:55 UTC