[Zope] How to prevent the user from going

[rlanham@speakeasy.net]

These lines, at least as group, ought only be used on process only pages.
Never on page that an application stops on and renders to a browser.
In addition to these lines, I always make it a practice to do DB or file
system processes on a page that I post to, that includes the lines below,
and when done, redirect with querystring variables to the calling page.
This way the user can click refresh and back all day and you won't get
dupes or constraint errors, etc.



> ------------ Original Message -----------
> From: Oliver Bleutgen <myzope@gmx.net>
> Date: Thu, 25 Jan 2001 21:11:43 +0100
> 
> > I use this on asp pages, you will have to modify for zope syntax, but
it
> > works
> > very well for your need:
> 
> > Response.buffer = true
> > Response.Expires = -1
> > Response.AddHeader "Pragma", "no-cache"
> > Response.AddHeader "cache-control", "no-store"
> 
> IIRC there's one catch though, It may be stopping netscape
> from being able to print the page. The silly thing then just prints
> "this page is expired from cache". 
> 
> cheers,
> oliver
> 
> 
>