safari redirect caching bug
At some point recently, Safari's caching with respect to 302 redirects changed.
I have the following setup:
- URL A is handled dynamically, and redirects the user to one of several possibilities.
- One of the possibilities is to redirect (302) to a static HTML page.
If I start up a fresh Safari process then the first time I go to URL A, then it's handled correctly. Any subsequent attempts to go to URL A result in the browser immediately showing the cached static content, and never hitting A.
This still works as expected (ie how it's been working for the last few years) on all other browsers, but it looks like this behaviour changed with the most recent Safari releases. It's true for Safari 7.0 on Mavericks and 6.1 (8537.71) on Mountain Lion.
Obviously I can code round this, but the behaviour seems surprising.
Neil
MacBook Pro & Powerbook