I’m trying to understand the redirection and caching mechanism on Nokia handsets.
It seems that when a resource (e.g. a web page) is requested from the server and the server
reply with a ‘302 Found ‘ – the browser (on Nokia handsets) will request the resource from the server even if it is already in cache and is still ‘fresh’.
1. Client has downloaded a page named ‘x.htm’ (the page is set to expire in 5 days).
2. Client downloaded a different page (y.htm) that has a link : <a href=”z.htm”….
3. The link is clicked by the user.
4. The server responds with a ‘302 Found’ and redirects to x.htm (which is still in cache – see line 1).
What happens now depends on whether it is a Nokia handset or not:
On Motorola, Sony Ericsson, etc. (And, of course, PC browsers) -> There won’t be another request for x.htm.
Nokia handsets on the other hand, will request that resource again!
I can also confirm that the page 'x.htm' was cached in the first request also on the Nokia handsets.
Is there a way to override this behavior?
(i.e. can I force the browser to look in cache first)