It's understandable that my browser would retireve from cache when I hit the back button. BUT: Should my browser also be retrieving from cache when I click on the same url twice, even if the url/uri is a get request.
I am implementing a logout link as follows: login.do?use_case=logout When I click on this link twice my Action.execute() is not being invoked. According to the HTTP Specification (section 13.9 - http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13): since some applications have traditionally used GETs and HEADs with query URLs (those containing a "?" in the rel_path part) to perform operations with significant side effects, caches MUST NOT treat responses to such URIs as fresh unless the server provides an explicit expiration time. This specifically means that responses from HTTP/1.0 servers for such URIs SHOULD NOT be taken from a cache. See section 9.1.1 for related information. --- Michael Jouravlev <[EMAIL PROTECTED]> wrote: > Browser is not obliged to reload non-cached page > when a user navigates > back in browser page history. Quite the opposite, > they must present > the resourse in the same state it was accessed for > the first time. > Opera does not reload a page, even with > cache-control settings telling > to not cache a page. MSIE reloads page when it sees > "no-cache". > Firefox reloads a page when it sees "no-store" or > the page is secured > by SSL and returned as "no-cache". > > Usually "no-cache, no-store" is enough for most > browsers, but not for Opera. > > Michael. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > __________________________________ Start your day with Yahoo! - Make it your home page! http://www.yahoo.com/r/hs --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
