Bad response header - browser cache is not invalidated for some browsers

[Licho]

I tested this with latest Opera. It fails to redownload trac sites, you have to manually refresh it.

Trac should tell opera to not use cache.

[Dave.Wilson@…]

With the latest development version of Trac I also have a similar issue. For example... if I have a new ticket and attempt to resolve it, add a comment or some other action I have to hit refresh (even after hitting "Submit change") before the changes are visible on the ticket. This only happens with the newest Firefox so far - IE 6 doesn't do it.

[sonic_and_tails2000@…]

I would also like to follow-up this issue on Opera and on devel v11-r6216. As of version 9.24, Opera seems to be not updating the changes properly. Not really a major issue but it can get quite annoying.

[anonymous]

I've encountered this behavior with Trac 0.11 + Apache 2.2. It affected both browsers used - Firefox 2.0.14 and IE 7.

I've changed all headers generated trac/web/api.py to prevent browser caching. I went through trac/web/api.py, found there 3 places where trac generates an http header and replaced all existed cache control options with following:

self.send_header('Pragma', 'no-cache') self.send_header('Cache-control', 'no-cache') self.send_header('Expires', 'Fri, 01 Jan 1999 00:00:00 GMT')

Apparently it solved the issue.

I didn't have an opportunity to investigate it deeper. However, the issue seems to be affected by authentication method used. With SSPI authentication it was similar to described by Dave.Wilson: I had to refresh page after a modification in order to see changes. Happened on both IE and Firefox (despite Firefox seems can't use SSPI and uses Basic instead). When I changed authentication to Basic I've been regularly seeing "logged in as" showing another user (e.g. Firefox shows a user logged on in IE or even from another machine). I've surely checked caching on Apache and to my best knowledge it is disabled there. The latter case make me think it isn't exactly a browser issue. Anyway the fix above have solved both issues.