Hi,

When a single file web page .mht is edited then saved a user will still see
the old data if the page is in the IE temp files. I've done some testing to
find ways to alleviate this.

This only happens if the edited file is the first one the user goes to in
the document library after the update. For instance file A is edited and
saved. A user had opened file A before the edit and then hit the back button
to go back to the document library. If they now open file A they see the old
data until they hit refresh. Or if they go back to the document library and
open file B then open file A they see the new data in file A without having
to hit refresh.

Seems the code runs to requery the database if the edited file was not the
last file the user displayed. MS probably did this to decrease the response
time. It would be nice if they recoded to always run the query or give the
admin an option to always run the query for web pages.

You can also set IE to empty the cache when the browser is closed. We don't
have a lot of users accessing a lot of web pages where they need the cache so
we can take the small performance hit. This still does not completly resolve
the issue but will reduce the chance of using old data.

Dave

Re: Update On Browser Caching and Edited Web Pages .mht by Patrick

Patrick
Tue Jan 25 14:05:52 CST 2005

The following may help:
When opening a document from the Shared Document library, if a user is not
seeing the document that was just edited.

Please set the Browser cache settings to "Every visit to the page" in the
IE Temporary Files setting.




"Dave Bone" <DaveBone@discussions.microsoft.com> wrote in message
news:794BA5CC-851C-4AAF-A914-779E97C5E480@microsoft.com...
> Hi,
>
> When a single file web page .mht is edited then saved a user will still
> see
> the old data if the page is in the IE temp files. I've done some testing
> to
> find ways to alleviate this.
>
> This only happens if the edited file is the first one the user goes to in
> the document library after the update. For instance file A is edited and
> saved. A user had opened file A before the edit and then hit the back
> button
> to go back to the document library. If they now open file A they see the
> old
> data until they hit refresh. Or if they go back to the document library
> and
> open file B then open file A they see the new data in file A without
> having
> to hit refresh.
>
> Seems the code runs to requery the database if the edited file was not the
> last file the user displayed. MS probably did this to decrease the
> response
> time. It would be nice if they recoded to always run the query or give the
> admin an option to always run the query for web pages.
>
> You can also set IE to empty the cache when the browser is closed. We
> don't
> have a lot of users accessing a lot of web pages where they need the cache
> so
> we can take the small performance hit. This still does not completly
> resolve
> the issue but will reduce the chance of using old data.
>
> Dave