Strange IIS6.0/ASP.NET Behaviour (HELP!)

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

Mikere:
> I have read a bit about 2003 and the http.sys cache and believe that my
> problem my lie here.

There is a simple way to find out if the problem is with the http.sys cache.
You can disable it entirely.

That way, if the problem continues, you'll know it's not http.sys's fault.

Follow the instructions at http://support.microsoft.com/?id=820129
to create a DWORD value of zero for "UriEnableCache" at this key :

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\HTTP\Parameters

Mind you, use this only for test purposes.
The http.sys cache is important for IIS's performance.

Here's some more background info on http.sys cache which you will find
interesting, since it details the reasons for http.sys *not* caching content :

http://support.microsoft.com/Default.aspx?id=817445

You might want to try out any of those techniques
to force http.sys to not cache content.

Juan T. Llibre
ASP.NET MVP
ASP.NET FAQ : http://asp.net.do/faq/
==========================

"Mike Trebilcock" <no@.replies.here> wrote in message
news:dgb3gc$atl$1@.news8.svr.pol.co.uk...
>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
>