.asp pages and cache

[Scott]

Kevin,


On Monday, June 10, 2002, at 02:01  PM, Kevin A Roust wrote:

> I've been finding that OW 4.1b7 caches some pages for longer that it
> "should".  In particular, when dealing with a site with lots of *.asp
> pages (which, in this case at least, are being generated dynamically on
> the server side), OW is keeping and displaying cached copies even after
> the page on the server changes.  For now, I can get around this by doing
> a reload, but a better fix would be nice...
>
> I've mainly been running into this on pages at 
> http://acts.wizard.com.hk/
> but unfortunately I haven't found any publically-available examples yet.
> As a registered user, I see this through things like the following:
>   Log in
>   Click on "Titan" to get the list of all games
>   Click on the name of the first game
>     Note the name top-center on the page
>   Go Back to the list of games (using toolbar Back)
>   Click on the name of the second game
>     Note the name top-center on the page (same as before)
>   Click the reload button in the toolbar
>     Note that the top-center name has changed

I logged in here and was able to reproduce what you describe.  Each one 
of the game links that you click has a very unique URL (GET 
/ttn/game.asp?id=1816&GUEST=1) but is then redirected by the server to a 
different URL:

Jun 10 15:34:57  http Rx: HTTP/1.1 302 Object moved
Jun 10 15:34:57  Location: guest.asp

Then you hit the back button, choose a different game, and we go through 
the same process again; making the request and then being redirected to 
guest.asp which we have in our cache and so we show that page.

The pages that come from the server have nothing in them or the headers 
that would indicate to us that it should expire at a specific time or 
that we should be making a new request for the page when later 
redirected to the same URL.

For a technical reference you can see the HTTP 1.1 spec, section 10.3.3 
302 Found, at this URL:

http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html

Mentioned there for a 302 is the following: "This response is only 
cacheable if indicated by a Cache-Control or Expires header field." and 
we are not caching the redirect response, just the response to the 
request for the document at the redirected URL.


If you can provide some reason that we should not be behaving this way 
then we'd certainly consider modifying our behavior but it seems to me 
that we're doing things right here.  You might want to contact the 
people who run this site and see what they have to say about this.

We recently modified our caching behavior to be more compatible with 
dynamic pages, as the tests here show (We pass them all):

http://www.procata.com/cachetest/


> Another minor nit is that I would like to be able to adjust the cmd-Up
> and cmd-Down behavior to act like Page Up/Down, rather than
> Next/Previous Anchor.  I use an iBook, which doesn't have dedicated
> Page Up/Down keys and the relevant meta key is on the opposite side of
> the keyboard from the arrow keys.  However, there is a handy-dandy apple
> key close to the arrow keys.
>
> If cmd-Up could be set to act like Page Up (as in, say, Netscape 4.7) I
> would be able to read long pages with only one hand, not the two (or
> mouse) that is required now.
>
> If changing the behavior of cmd-Up and cmd-Down is difficult (or not
> recommended), some other one-handed chord would be reasonable -- I've
> grown used to Acrobat's enter/shift-enter or return/shift-return combos
> for page down/up.

Might I suggest you take a look at ReKey, an application that can change 
and add keyboard shortcuts in Cocoa applications.  See 
http://www.versiontracker.com/moreinfo.fcgi?id=10592&db=mac for more 
information.

Of course, if you decide to install this software you do so at your own 
risk.  The Omni Group does not support this software in any fashion.


Sincerely,


Scott
Support Engineer
Omni Group