It was caching problem from the beginning, thank you guys, very much!

gg

header(”ETag: PUB” . time());
header(”Last-Modified: ” . gmdate(”D, d M Y H:i:s”, time()-10) . ” GMT”);
header(”Expires: ” . gmdate(”D, d M Y H:i:s”, time() + 5) . ” GMT”);
header(”Pragma: no-cache”);
header(”Cache-Control: post-check=0, pre-check=0, max-age=1, s-maxage=1, no-cache, must-revalidate”);
session_cache_limiter(”nocache”);

I use GET to retrieve the XML file as such

http.open(”GET”,”myfile.xml”,true)

HTTP = getHTTPObject();
//var url = “news.xml”+”?ms=”+new Date().getTime();
var url = “news.xml”;
HTTP.open(”GET”,url,true);
HTTP.setRequestHeader(’If-Modified-Since’, ‘Sat, 1 Jan 2000 00:00:00 GMT’);
HTTP.onreadystatechange = Process;
HTTP.send(null);

On one server, Apache/1.2.33 (Unix) mod_ssl/2.8.22 OpenSSL/0.9.7e PHP/4.3.10 (as returned by

alert(HTTP.getAllResponseHeaders());

It still loads the initial XML file before changes were made to it.

On this server, Netscape-Enterprise/3.6 SP2, as I’m making changes to the XML file, it loads the changed XML just fine.

Any ideas? FF works fine on either servers.

ajaxRequest.open(”GET”, url, true);

// This ensures that the result is not cached.
ajaxRequest.setRequestHeader( “If-Modified-Since”, “Sat, 1 Jan 2000 00:00:00 GMT” );

ajaxRequest.send(null);

POST is supposed to be used to denote making a durable change in a resource of some kind.

The real issue is caching, and I think IE has never handled caching very well. (Note: I believe using SSL generally disables caching. Although it increases the bandwidth and computational requirements, it also keeps your transactions away from prying eyes.)

It shouldn’t be considered a bug at all. You’re telling the server to send a GET request. According to the W3 spec, GET requests are “idempotent”, meaning that the repeated requests with identical input yield identical output. This is why browsers and firewalls cache these types of requests.

You can get around problems entirely if you use POST instead of GET. Most of the time you really want POST anyway. Just change your code like so..

req.open(”POST”, urlstr, true); //Mission accomplised.

Yes, you can certainly use tricks to fool the browser into downloading a new copy for a GET request. However, probably shouldn’t be doing this depending on your intended goal.