Got it. Thanks Michael. --- Michael Jouravlev <[EMAIL PROTECTED]> wrote:
> On 11/25/05, Mon Cab <[EMAIL PROTECTED]> wrote: > > 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. > > Yes, it might do so if page is cacheable. It must > reload page from the > server if you reload it explicitly with "Reload" > button. > > > 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. > > Is it server's or browser's problem that "some > applications have > traditionally used" HTTP protocol not the way it was > intended to do? > GET requests are meant to produce no side effects. > To be on the safe > side, just return the proper cache-control headers. > On Firefox, the > headers are easy to spot with Live HTTPHeaders > extension. > > 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]
