Closed Bug 290929 Opened 20 years ago Closed 9 years ago

firefox does not check to to see if the current xml file is newer than the info stored in the chache.

Categories

(Core :: Networking: Cache, defect)

x86
Windows XP
defect
Not set
minor

Tracking

()

RESOLVED WONTFIX

People

(Reporter: crazymanraymond, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3

the swf at www.raymondselzer.com/portfolio/ calls an xml file on the same
server, however if the xml file is updated changes cannot be seen in the swf
until the cache is cleared. 

this is not a problem with any other type of text file.

Reproducible: Always

Steps to Reproduce:
1. add an update to the xml file
2. refresh the main page
Actual Results:  
changes to the xml file did not appear in the swf

Expected Results:  
showed the changes made to the xml file

this problem only seems to occur with xml files txt files and any custom
extension of a txt file is refreshed fine every time.
Assignee: firefox → darin
Component: General → Networking: Cache
Product: Firefox → Core
QA Contact: general → networking.cache
Version: unspecified → Trunk
Since Flash (swf) is a both client-side and server-side application and is sort
of a gateway between firefox and the internet.  Since your comment said Flash
(swf) access the xml then firefox doesn't need to access the xml file for that
since Flash (swf) would do it for us.  It could be as result of a programming
error or something in Flash (swf).

If that's not what you meant then can you clarify it?
Another thought came to my mind, does the flash applet (swf) reload upon refreshing?
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
So, I believe that flash uses Mozilla's HTTP stack to access resources off the
internet.  That means that Mozilla's cache could possibly be in the loop here. 
I'd like to see a HTTP log if someone could please generate one.  Instructions here:

http://www.mozilla.org/projects/netlib/http/http-debugging.html

Thanks!
-> default owner
Assignee: darin → nobody
The bug may be old but I'm still experiencing it (31.4.0). It drove me crazy trying to figure out why a web site update wasn't working.

I updated an xml file that controlled a javascript slide show. It worked locally but when I posted the update, the old slide show would still show. Days later the change still wasn't showing up in Firefox but was in other browsers. I had to manually clear Firefox's cache to get the update to show.

I'm running Debian/Jessie on an AMD64 machine.
the xml needs to be served with the appropriate http caching info (expires, cache-control, etc..)
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.