IIS ASP - Firefox reload page

This is Interesting: Free IT Magazines  
Home > Archive > IIS ASP > August 2004 > Firefox reload page





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Firefox reload page
Dave Blair

2004-08-27, 6:17 pm

Hi,

Hi,
In firefox I can't get a page (which queries an SQL database and shows
all the available records) to re-fresh with new updated data after a
'javascript:history.go(-4)' is used to return to the page after a new
record is added.

I have the following code in the page which displays the records:

<%
Response.Buffer = True
Response.ExpiresAbsolute = Now() - 1
Response.Expires = 0
Response.CacheControl = "no-cache"
%>

This should make it completly refresh the page rather than load it
from the IIS server cache.

Also I added:

<meta http-equiv="no-cache">
<meta http-equiv="pragma" content="no-cache">
<meta http-equiv="expires" CONTENT="Wed, 26 Feb 1997 08:21:57 GMT">

Which should mean that it's not reloading from any local browser
cache.

Anyone any ideas as to how to force a complete reload.
I should mention that the page is in a frame, and that doing
'right-click'->'This frame'->'Reload Frame' works as it should and
refreshes the data properly.

thanks for any help,
Dave

Dave Anderson

2004-08-27, 6:17 pm

Dave Blair wrote:
> In firefox I can't get a page (which queries an SQL database and shows
> all the available records) to re-fresh with new updated data after a
> 'java script:history.go(-4)' is used to return to the page after a new
> record is added...


Isn't that the correct behavior? Cache control is for subsequent *requests*.
You are not sending one.

"History mechanisms and caches are different. In particular history
mechanisms SHOULD NOT try to show a semantically transparent view
of the current state of a resource. Rather, a history mechanism is
meant to show exactly what the user saw at the time when the
resource was retrieved."
(http://www.w3.org/Protocols/rfc2616...3.html#sec13.13)


> Anyone any ideas as to how to force a complete reload.


Yes. Stop (ab)using history. Force the browser to send a request. Any of
these are options:

Response.Redirect(...)
window.location.replace(...)
window.location = "..."
<a href="...">Updated View</A>



--
Dave Anderson

Unsolicited commercial email will be read at a cost of $500 per message. Use
of this email address implies consent to these terms. Please do not contact
me directly or ask me to contact you directly for assistance. If your
question is worth asking, it's worth posting.


Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com