M
Mike Trebilcock
I have a web app that builds a tree from a database. The tree is built on
demand when the user POSTs the page back to the sever. The server maintains
a copy of the current tree in a session object.
This all works fine on the development server but I have a problem on my
live server (IIS6.0 ASP.NET 1.1). When the user posts the page back the
request is not getting to ASP.NET. When tracing is enabled there is no
entry. However the browser is getting an old picture of the tree from a
couple of clicks ago and things start going a bit haywire.
I have set every option I can find within my code to prevent caching
occuring, and I know that no servers along the route a caching because I get
the same problem when I access the app from the server using localhost.
I have read a bit about 2003 and the http.sys cache and believe that my
problem my lie here.
HELP!!
Thanks in anticipation
Mike
demand when the user POSTs the page back to the sever. The server maintains
a copy of the current tree in a session object.
This all works fine on the development server but I have a problem on my
live server (IIS6.0 ASP.NET 1.1). When the user posts the page back the
request is not getting to ASP.NET. When tracing is enabled there is no
entry. However the browser is getting an old picture of the tree from a
couple of clicks ago and things start going a bit haywire.
I have set every option I can find within my code to prevent caching
occuring, and I know that no servers along the route a caching because I get
the same problem when I access the app from the server using localhost.
I have read a bit about 2003 and the http.sys cache and believe that my
problem my lie here.
HELP!!
Thanks in anticipation
Mike