AJAX html won't refresh after data update

[javelin]

I created a feature in a page where a DIV displays child records of
the current record. From this same page, I can submit the insertion of
a new child record. However, the while the previous child records
displayed fine, the newly added ones don't - until I close down IE and
restart it. I know, there's a setting in IE options which will force a
refresh on each page load, instead of caching, but I can't access it
from these computers (NT policy prohibits it, I guess). None of the
end users can either, so that's not a solution. Anything I can do
programmaticall y here?

Thanks.

[Robin]

javelin wrote:

I created a feature in a page where a DIV displays child records of
the current record. From this same page, I can submit the insertion of
a new child record. However, the while the previous child records
displayed fine, the newly added ones don't - until I close down IE and
restart it. I know, there's a setting in IE options which will force a
refresh on each page load, instead of caching, but I can't access it
from these computers (NT policy prohibits it, I guess). None of the
end users can either, so that's not a solution. Anything I can do
programmaticall y here?

Add a 'unique' variable to the query string of you ajax URI so that
browser doesn't use the cached copy.

i.e.
obj.open('GET', 'ajax_call.php? recid='+recid+' &z='+
new Date().getTime( ),true);
HTH
Robin

[Good Man]

javelin <go************ *@spamgourmet.c omwrote in
news:11******** **************@ 22g2000hsm.goog legroups.com:

I created a feature in a page where a DIV displays child records of
the current record. From this same page, I can submit the insertion of
a new child record. However, the while the previous child records
displayed fine, the newly added ones don't - until I close down IE and
restart it. I know, there's a setting in IE options which will force a
refresh on each page load, instead of caching, but I can't access it
from these computers (NT policy prohibits it, I guess). None of the
end users can either, so that's not a solution. Anything I can do
programmaticall y here?

Send an expired header with your data. Here's a straight lift from PHP
code:

//IE CACHES AJAX PAGES!!!
header("Expires : Sun, 19 Nov 1978 05:00:00 GMT");
header("Last-Modified: " . gmdate("D, d M Y H:i:s") . " GMT");
header("Cache-Control: no-store, no-cache, must-revalidate");
header("Cache-Control: post-check=0, pre-check=0", false);
header("Pragma: no-cache");

.... followed by the correct headers and data for the XML or whatever output
you send back....

[cts1]

Dang, Robin! That actually works! Not used to getting such good help
the first time around :D

Thanks for the great idea.

J

On Oct 4, 9:52 am, Robin <a...@somewhere .comwrote:

javelin wrote:

I created a feature in a page where a DIV displays child records of
the current record. From this same page, I can submit the insertion of
a new child record. However, the while the previous child records
displayed fine, the newly added ones don't - until I close down IE and
restart it. I know, there's a setting in IE options which will force a
refreshon each page load, instead of caching, but I can't access it
from these computers (NT policy prohibits it, I guess). None of the
end users can either, so that's not a solution. Anything I can do
programmaticall y here?

Add a 'unique' variable to the query string of you ajax URI so that
browser doesn't use the cached copy.

i.e.
obj.open('GET', 'ajax_call.php? recid='+recid+' &z='+
new Date().getTime( ),true);

HTH
Robin

[Thomas 'PointedEars' Lahn]

ct**@spvision.c om wrote:

On Oct 4, 9:52 am, Robin <a...@somewhere .comwrote:

>Add a 'unique' variable to the query string of you ajax URI so that
browser doesn't use the cached copy.

i.e.
obj.open('GET' ,'ajax_call.php ?recid='+recid+ '&z='+
new Date().getTime( ),true);

Dang, Robin! That actually works! Not used to getting such good help
the first time around :D

Thanks for the great idea.

That idea is BAD because it fills the browser cache with garbage, and so
eventually slows down access to other content. Unnecessarily.

Please don't top-post: http://jibbering.com/faq/
PointedEars
--
realism: HTML 4.01 Strict
evangelism: XHTML 1.0 Strict
madness: XHTML 1.1 as application/xhtml+xml
-- Bjoern Hoehrmann

[cts1]

Dang, Robin! That actually works! Not used to getting such good help
the first time around :D

Thanks for the great idea.

J

On Oct 4, 9:52 am, Robin <a...@somewhere .comwrote:

javelin wrote:

I created a feature in a page where a DIV displays child records of
the current record. From this same page, I can submit the insertion of
a new child record. However, the while the previous child records
displayed fine, the newly added ones don't - until I close down IE and
restart it. I know, there's a setting in IE options which will force a
refreshon each page load, instead of caching, but I can't access it
from these computers (NT policy prohibits it, I guess). None of the
end users can either, so that's not a solution. Anything I can do
programmaticall y here?

Add a 'unique' variable to the query string of you ajax URI so that
browser doesn't use the cached copy.

i.e.
obj.open('GET', 'ajax_call.php? recid='+recid+' &z='+
new Date().getTime( ),true);

HTH
Robin

[Randy Webb]

Thomas 'PointedEars' Lahn said the following on 10/5/2007 2:00 PM:

ct**@spvision.c om wrote:

>On Oct 4, 9:52 am, Robin <a...@somewhere .comwrote:

>>Add a 'unique' variable to the query string of you ajax URI so that
browser doesn't use the cached copy.

i.e.
obj.open('GET ','ajax_call.ph p?recid='+recid +'&z='+
new Date().getTime( ),true);

Dang, Robin! That actually works! Not used to getting such good help
the first time around :D

Thanks for the great idea.

That idea is BAD because it fills the browser cache with garbage, and so
eventually slows down access to other content. Unnecessarily.

Pure nonsense.

--
Randy
Chance Favors The Prepared Mind
comp.lang.javas cript FAQ - http://jibbering.com/faq/index.html
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/

[Thomas 'PointedEars' Lahn]

Randy Webb wrote:

Thomas 'PointedEars' Lahn said the following on 10/5/2007 2:00 PM:

>ct**@spvision.c om wrote:

>>On Oct 4, 9:52 am, Robin <a...@somewhere .comwrote:
Add a 'unique' variable to the query string of you ajax URI so that
browser doesn't use the cached copy.

i.e.
obj.open('GE T','ajax_call.p hp?recid='+reci d+'&z='+
new Date().getTime( ),true);
Dang, Robin! That actually works! Not used to getting such good help
the first time around :D

Thanks for the great idea.

That idea is BAD because it fills the browser cache with garbage, and so
eventually slows down access to other content. Unnecessarily.

Pure nonsense.

(sic!)

It isn't nonsense, it's a fact. (Or have I overlooked your argument by any
chance?)
PointedEars
--
var bugRiddenCrashP ronePieceOfJunk = (
navigator.userA gent.indexOf('M SIE 5') != -1
&& navigator.userA gent.indexOf('M ac') != -1
) // Plone, register_functi on.js:16

[Randy Webb]

Thomas 'PointedEars' Lahn said the following on 10/5/2007 7:41 PM:

Randy Webb wrote:

>Thomas 'PointedEars' Lahn said the following on 10/5/2007 2:00 PM:

>>ct**@spvision.c om wrote:
On Oct 4, 9:52 am, Robin <a...@somewhere .comwrote:
Add a 'unique' variable to the query string of you ajax URI so that
browser doesn't use the cached copy.
>
i.e.
obj.open('G ET','ajax_call. php?recid='+rec id+'&z='+
new Date().getTime( ),true);
Dang, Robin! That actually works! Not used to getting such good help
the first time around :D

Thanks for the great idea.
That idea is BAD because it fills the browser cache with garbage, and so
eventually slows down access to other content. Unnecessarily.

Pure nonsense.

(sic!)

It isn't nonsense, it's a fact. (Or have I overlooked your argument by any
chance?)

You have overlooked the argument. There is a very good reason for using
a query string to force a reload from the server. And no, headers and
server settings won't satisfy the need.

--
Randy
Chance Favors The Prepared Mind
comp.lang.javas cript FAQ - http://jibbering.com/faq/index.html
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/

[Laurent vilday]

Thomas 'PointedEars' Lahn a écrit :

Randy Webb wrote:

>Thomas 'PointedEars' Lahn said the following on 10/5/2007 2:00 PM:

>>ct**@spvision.c om wrote:
On Oct 4, 9:52 am, Robin <a...@somewhere .comwrote:
Add a 'unique' variable to the query string of you ajax URI so that
browser doesn't use the cached copy.
Dang, Robin! That actually works! Not used to getting such good help
the first time around :D
Thanks for the great idea.
That idea is BAD because it fills the browser cache with garbage, and so
eventually slows down access to other content. Unnecessarily.

Pure nonsense.

(sic!)

It isn't nonsense, it's a fact.

sic !

It is well-known among competent Web developers that IE is suffering a
cache issue with XHR when the call method is "GET". And no headers will
do anything to it.

The only solution is to add a dummy unique variable to the querysting.

*That* is a fact among others !

--
laurent