Closed Bug 200706 Opened 22 years ago Closed 20 years ago

XML documents caching

Categories

(Core :: XML, defect)

x86
Windows 2000
defect
Not set
major

Tracking

()

RESOLVED INVALID

People

(Reporter: bmf1972, Assigned: hjtoi-bugzilla)

References

Details

Attachments

(1 file)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2a) Gecko/20020910 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2a) Gecko/20020910 Some DOM application uses the 'XMLHttpRequest' object to retrieve some XML document. If the document was retrieved some time ago (cached) then the browser decides no to check for new versions of it. Reproducible: Always Steps to Reproduce: 1. Load the XML document, using 'XMLHttpRequest' object 2. Change something in the XML document 3. Reload the XML document Actual Results: The browser cached the first version of the XML document, and uses the cached version for every consequent load. Expected Results: It must check for a new document version, and if new the it must update its cache accordingly. Here is the full test case: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <HTML> <HEAD> <TITLE>Test XMLHttpRequest</TITLE> <SCRIPT> function load( xmlHref ) { var xmlhttpRequest; xmlhttpRequest = new XMLHttpRequest(); xmlhttpRequest.open( "GET", xmlHref, false ); xmlhttpRequest.send( null ); return xmlhttpRequest.responseXML; } function serialize( oXML ) { return (new XMLSerializer()).serializeToString( oXML ); } </SCRIPT> </HEAD> <BODY> <FORM action="javascript:void(0)"> <INPUT type="text" name="href" size="80"> <INPUT type="button" value="Load & Display" onclick="alert(serialize(load(this.form.href.value)))"> </FORM> </BODY> </HTML>
Also checked with: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4a) Gecko/20030401
Attached file Test loader
*** Bug 215802 has been marked as a duplicate of this bug. ***
This is now fixed. Fixed as part of bug 237319. Marking FIXED.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
This is no longer "fixed" now that bug 268844 got checked in, and in fact, this bug shouldn't be fixed. Whether or not a XMLHttpRequest should be cached is up to the caller (by setting http headers on the request) or the server to decide, not the browser.
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Marking INVALID.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago20 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: