Whatz up, guys? Well, I´m having problems in reloading a page that shows information contained in a table of a database. The problem is that whenever I include some data in the database at another page it send´s me back to that page that shows information, it doens´t show the update, but a cached page. I´m using the IE 5.0 and I haven´t figured out how to reload it every time without changing the configuration of the browser. I´ve tryed the same code that I´m using in IE 5.0 in IE 5.5 and this problem doens´t happen. Hope that you all could give me some help. Thank´s, Daniel C. Azevedo
Daniel Corrêa de Azevedo wrote:
Whatz up, guys?
Well, I´m having problems in reloading a page that shows information contained in a table of a database. The problem is that whenever I include some data in the database at another page it send´s me back to that page that shows information, it doens´t show the update, but a cached page. I´m using the IE 5.0 and I haven´t figured out how to reload it every time without changing the configuration of the browser. I´ve tryed the same code that I´m using in IE 5.0 in IE 5.5 and this problem doens´t happen. Hope that you all could give me some help. Thank´s, Daniel C. Azevedo
Try putting this in the head of your standard_html_header: <dtml-if no_cache> <META HTTP-EQUIV="pragma" CONTENT="no-cache"> </dtml-if no_cache> Then set a boolean property on the DTML Document (or folder if it's a method) called "no_cache". This should prevent the browser from caching the page. -- | Casey Duncan | Kaivo, Inc. | cduncan@kaivo.com `------------------>
Hi... ... snip ...
Try putting this in the head of your standard_html_header:
<dtml-if no_cache> <META HTTP-EQUIV="pragma" CONTENT="no-cache"> </dtml-if no_cache>
I recommend <dtml-call "RESPONSE.setHeader('pragma','no-cache')"> <dtml-call "RESPONSE.setHeader('Expires',_.DateTime().rfc822()"> for greater effect. (Even with proxies)
Then set a boolean property on the DTML Document (or folder if it's a method) called "no_cache". This should prevent the browser from caching the page.
Regards Tino
Hi Daniel, for whatever reason some of the defaults in IE5 is often to never look for new versions of a resource. You have to change that for your pages to work. (This is true for all similar things like shops and so on) Regards Tino Daniel Corrêa de Azevedo wrote:
Whatz up, guys?
Well, I´m having problems in reloading a page that shows information contained in a table of a database. The problem is that whenever I include some data in the database at another page it send´s me back to that page that shows information, it doens´t show the update, but a cached page. I´m using the IE 5.0 and I haven´t figured out how to reload it every time without changing the configuration of the browser. I´ve tryed the same code that I´m using in IE 5.0 in IE 5.5 and this problem doens´t happen. Hope that you all could give me some help. Thank´s, Daniel C. Azevedo
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
On Fri, 9 Mar 2001 00:22, Daniel Corrêa de Azevedo wrote:
Whatz up, guys?
Well, I´m having problems in reloading a page that shows information contained in a table of a database. The problem is that whenever I include some data in the database at another page it send´s me back to that page that shows information, it doens´t show the update, but a cached page. I´m using the IE 5.0 and I haven´t figured out how to reload it every time without changing the configuration of the browser. I´ve tryed the same code that I´m using in IE 5.0 in IE 5.5 and this problem doens´t happen. Hope that you all could give me some help. Thank´s,
It's almost certainly your browser. IE seems to come default configured to only check for new pages once persession, or sometimes "never" (or until the item is flushed from the cache). Under Netscape, you could simply hold Shift whilst you pressed reload, which would bypass it's internal cache. However, just recently on this list there were two server side 'solutions' to this problem. One involved a META tag, which, imho, is a poor move when there is a perfectly good HTTP header line to use. => Tino Wildenhain wrote: => I recommend <dtml-call "RESPONSE.setHeader('pragma','no-cache')"> => <dtml-call "RESPONSE.setHeader('Expires',_.DateTime().rfc822()"> These headers should mean that nothing caches your pages. Not your browser or any proxies along the way. Another option is to just use the "Expires" line, and set it to 10seconds or so into the future...
Daniel C. Azevedo
Have a better one, Curtis Maloney
Curtis Maloney wrote:
These headers should mean that nothing caches your pages. Not your browser or any proxies along the way. Another option is to just use the "Expires" line, and set it to 10seconds or so into the future...
Daniel C. Azevedo
It is legal to send Expires: 0 to signify an uncacheable object in HTTP/1.1. If you want to work with any browser and webcache, use Pragma: no-cache. You can't rely on everyone to handle the Expires header correctly, especially Expires: 0. Pragma: no-cache has been around forever. --sam
participants (5)
-
Casey Duncan -
Curtis Maloney -
Daniel Corrêa de Azevedo -
Samuel D. Gendler -
Tino Wildenhain