Hi,

In my asp.net 1.1 web application there is a page with a url something
like userinfo.aspx?userid=107 which has some postback buttons on it.

In the GET method (i.e. IsPostBack = false) it fetches some
information about that user and stored it in the session, then in the
postback it uses that information from the session.

However, if the user has the IE browser cache setting at the default
value ("check for new versions of stored pages automatically"),
sometimes IE will use the cached page instead of sending the GET. this
means that when it sends the postback, the wrong information is in the
session.

from what I can tell, the best way to solve this is to put cache-
control directives in, so that the page doesn't get cached. I would
like to do this for every page in the application. is there a way to
specify in the web.config that all aspx pages should be sent with "no
cache" direcives?

it seems to me that most asp.net applications would suffer from the
same problem are there any best practice techniques to avoid this
(except not using session state)

TIA

Andy

With v2.0 I think you could set it on web.config
(http://msdn2.microsoft.com/en-us/library/ms228124.aspx) but in v1.x you
certainly can do it programmatically in Application_BeginRequest event
handler (global.asax)


--
Teemu Keiski
AspInsider, ASP.NET MVP
http://blogs.aspadvice.com/joteke
http://teemukeiski.net




<ajfish (AT) blueyonder (DOT) co.uk> wrote