IIS won't recognize if an ASP page has been changed

External Since: Nov 20, 2003 Posts: 5

With Windows 2003 Server...

Imagine the following scenario: there is a simple ASP page, for example just
a single Response.Write statement. There is a virtual directory pointing to
the directory, where the ASP page is stored.

If I change this ASP page and hit the refresh button on the client browser.
I can then see the following behaviour:

[1] If the ASP page had been stored in the local file system of the IIS
Server, anything works fine. The client immediately sees the change.

[2] If the ASP page had been stored in the file system of another Windows
2003 server, the first refresh does not work. The old content is sent to the
browser. One has to refresh a second time, for getting the new contents.

The wrong result can be seen, even if the following scenario is performed...

- open new browser
- load ASP page
- change the ASP page on the server
- open a new browser
- load the ASP page

After loading the ASP page in a separate browser window, the old contents
can be seen.

I am sure, that this is no client side feature. The browser has the "search
for new versions of a page on each and every access" setting (translation
probably not 100% correct). Clearing cookies, temporary files or history on
the client does not help.

It is definitely a question of whether the ASP page is stored locally or
remotely. The good behaviour (local) and the bad behaviour (remote) can be
reproduced any number of times.

Can anybody reproduce this behaviour? Is it already known? Is there a
solution?

Michael G. Schneider

External Since: Aug 25, 2003 Posts: 2419

Please give more details on how you configured #2.

In particular, are you using Mapped Drive or UNC shares. Is it pass-thru
authentication or not?

--
//David
IIS
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Michael G. Schneider" <mgs-AntiSpam RemoveThis @mgs-software.de> wrote in message
news:%234mOCqzrDHA.3140@TK2MSFTNGP11.phx.gbl...
With Windows 2003 Server...

Imagine the following scenario: there is a simple ASP page, for example just
a single Response.Write statement. There is a virtual directory pointing to
the directory, where the ASP page is stored.

If I change this ASP page and hit the refresh button on the client browser.
I can then see the following behaviour:

[1] If the ASP page had been stored in the local file system of the IIS
Server, anything works fine. The client immediately sees the change.

[2] If the ASP page had been stored in the file system of another Windows
2003 server, the first refresh does not work. The old content is sent to the
browser. One has to refresh a second time, for getting the new contents.

The wrong result can be seen, even if the following scenario is performed...

- open new browser
- load ASP page
- change the ASP page on the server
- open a new browser
- load the ASP page

After loading the ASP page in a separate browser window, the old contents
can be seen.

I am sure, that this is no client side feature. The browser has the "search
for new versions of a page on each and every access" setting (translation
probably not 100% correct). Clearing cookies, temporary files or history on
the client does not help.

It is definitely a question of whether the ASP page is stored locally or
remotely. The good behaviour (local) and the bad behaviour (remote) can be
reproduced any number of times.

Can anybody reproduce this behaviour? Is it already known? Is there a
solution?

Michael G. Schneider