Bugzilla is not the right place for advocacy, as you can see from the two-year delay :) It probably would help filing specific issues with separate testcase for the most painful violations of the spec (and/or violations where we are the only non-conforming browser left) and either finding resources or persuading the drivers that fixing these violations is more important than working on other features/bugs. Since this bug is rather unspecific, I'm morphing it to a meta bug and adding a few bugs about XMLHttpRequest caching to the dependencies.
You may also want to look at bug #462243
> Bugzilla is not the right place for advocacy, as you can see from the two-year delay :) Thanks for the response nonetheless. Since writing this up in 2008 I've come to the conclusion that browser-level caching, content-negotiation, etc. will be quirky for the foreseeable future so we now design our apps to make things as simple as possible between the browser and first server. We optimize around server-to-server communication and server-side code where you have more control. So in summary I'm no longer advocating for this improvement but of course would be happy if it were to happen.
The bug is still not fixed, not even on Firefox 29 Nightly. On Chrome setRequestHeader('Cache-Control', 'no-cache') would avoid the cache and retry new XMLHttpRequest.
The problem is - nothing supported from Cache-Control sent by the user agent. For example Cache-Control: "no-cache", Cache-Control: "max-age=0", Cache-Control: "max-age=0, must-revalidate" must avoid cache, but does not on Firefox. Cache-Control explained in http://stackoverflow.com/questions/1046966/whats-the-difference-between-cache-control-max-age-0-and-no-cache
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 428916
You need to log in before you can comment on or make changes to this bug.