>> Then they're going to be available in the browser cache until the >> browser chooses to discard them. You can't have it both ways. > >The OP could set expires headers that are relatively short-lived. That >way, the client /should/ request a fresh page after, say, 30 minutes >or whatever the session timeout is set to. > >But Martin, I agree with Chuck: you can't have it both ways.
I was going to suggest that you could use the ETag to create tags composed of the last edit time and the session-id. That way the pages will be cached for the current user's session, but are freshed once the user logs out/original page is updated. Its not true caching in that the browser will still ask the server if it has changed, but at least it won't have to send the whole file down each time. Seems that the thread has moved on now though. If I understood correctly you have turned off all caching, yet the pages are still cached. I agree with the others - try using some tools to sniff the actual network traffic. I find fiddler very useful for this kind of work Chris
