Re: New Quixote site, and expire problem
Mike Orr <[email protected]>
| Newsgroups | gmane.comp.web.quixote.user |
|---|---|
| Message-ID | <[email protected]> |
On 9/12/05, Neil Schemenauer <[email protected]> wrote: > [This message has also been posted.] > Mike Orr <[email protected]> wrote: > > The problem is that if you view one category (list of entries), > > then go back and view another, on some browsers you see the first > > category again. Then if you hit Refresh it shows the correct > > category. It seems to be a problem with browser caching. > > Which browsers? Is there some kind of pattern? Firefox, IE, Safari, and Netscape 7 at least. Not Konqueror. It doesn't always happen, but when it does it keeps happening several times in a row. It migrates sites too, sometimes on one, sometimes on the other, even though they're derived from the same codebase. > > I looked through the HTTP RFC and http_response.py, and it looks like > > it doesn't cache by default but somehow it is. self.cache is 0, which > > seems to translate to "Expires: -1", but my browser (Firefox) says > > "Expires: not specified". I'd like to put "Expires: 0" but it looks > > like I'd have to hack the Publisher to do so. I figured I'd ask here > > first. > > "Expires: -1" should do the right thing. I verified it is generating "Expires: -1" when the problem occurs. I hacked http_response.generate_headers() to set "Expires: 0" instead but it didn't make any difference. Firefox in its info box says "Expires: (no expiration set)" either way. Konqueror is more explicit:: Cache-Control max-age=60 Expires -1 (or 0) Expires <one minute later than Date: header> I'm going to rearrange the URLs as David suggested ( /1/categories/4 ) and do the query for every page. That means several more Directories, but it should bypass the problem, at least until we have a general search screen. Then it won't be practical to have a distinct URL for every type of search. The problem is easy to work around by pressing the Refresh button, but that's unreasonable to expect of users. -- Mike Orr <[email protected]> or <[email protected]>