[Bug 135156] JavaScript loading of external XML always uses cache

[Adrian Irving-Beer]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=135156         




------- Additional Comments From wisq-kde wisq net  2007-06-09 00:09 -------
Sorry for the months-long delay on this.  I apparently signed up for an account on this bug tracker but never actually followed up.  Found this when going back through my old e-mail.

The bug appears to remain in my current version of Konqueror (3.5.6).  Furthermore, it doesn't even require that I access a remote server -- I can reproduce it simply by saving the test.html and test.xml to disk and loading the test.html (refreshing to make the text appear), then editing the test.xml and seeing the (lack of any) effect.

At the time I reported this issue, I was working on a site that I could not have released at the time, hence the submitting of simple test files.  That site has since been released, and the offending page is available at http://www.nfa-arb.org/by-topic , with indexes by topic and by claim number.  XML indices are in http://www.nfa-arb.org/xml/topics and http://www.nfa-arb.org/xml/claims .

I verified the issue against the live site:

1. Access topic index with Konqueror; tree is rendered correctly.

2. Make a minor cosmetic alteration to a single node within the tree (in the XML file).

3. Refresh the topic index.  Change is not reflected.

4. Load XML index up directly in Konqueror (using the embedded kxmleditor interface) and refresh it.  XML shows current version; hence it is not a normal caching issue.

5. Repeat step 3.  Same result.

"Iceweasel" (Debian's Firefox) does not have the same problem, but it always takes a little time to load the index, so it may not be caching at all.

Note that the XML does eventually seem to expire from the cache, but on a schedule independent of Konqueror's main cache, i.e. using "refresh" or clearing the Konqueror cache does not help.

At this point, I'm not really affected by this issue any more, but I reported it due to the inconsistency it created (and the confusion it caused during development).

Let me know if you need anything else.