I have a main ASP file that does common page processing and is included in
my data access pages, i.e.

UserDetail.asp has PageProcessor.asp included in it.

When developing, and I have to make changes to the PageProcessor.asp file,
those changes are not seen by IE 6. The PageProcessor.asp page is being
cached.

Tried setting content expiry to expire immediately in IIS. Also tried
setting IE6 to check for new page everytime.

My only work around right now is to rename the PageProcessor.asp file,
refresh the UserDetail.asp page in IE to get an error that it cannot find
PageProcessor.asp, then rename it back and refresh the page again. Then it
works. As you can image this is very frustrating and severly slows down the
development process.

Any help is GREATLY appreciated!!!

Thanks,
Chad

[ Post a follow-up to this message ]

Ah... found this on learnasp.com
Post these on the top of your page
<%

Response.Expires = -600000
Response.Expiresabsolute = Now() - 1
Response.AddHeader "pragma","no-cache"
Response.AddHeader "cache-control","private"
Response.CacheControl = "no-cache"

%>

"Chad Richardson" <chad@NIXSPAM_chadrichardson.com> wrote in message
news:121lv0b58iaj2c7@corp.supernews.com...
>I have a main ASP file that does common page processing and is included in
>my data access pages, i.e.
>
> UserDetail.asp has PageProcessor.asp included in it.
>
> When developing, and I have to make changes to the PageProcessor.asp file,
> those changes are not seen by IE 6. The PageProcessor.asp page is being
> cached.
>
> Tried setting content expiry to expire immediately in IIS. Also tried
> setting IE6 to check for new page everytime.
>
> My only work around right now is to rename the PageProcessor.asp file,
> refresh the UserDetail.asp page in IE to get an error that it cannot find
> PageProcessor.asp, then rename it back and refresh the page again. Then it
> works. As you can image this is very frustrating and severly slows down
> the development process.
>
> Any help is GREATLY appreciated!!!
>
> Thanks,
> Chad
>

[ Post a follow-up to this message ]