ginal Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 25, 2001 3:51 PM
To: [EMAIL PROTECTED]
Subject: Re: [Zope] How to prevent the user from going
These lines, at least as group, ought only be used on process only pages.
Never on page that an application stops o
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
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"
Original Message ---
> From: Daniel
> Use a session tracking product, that'll give you a session id and ocne the
> session is complete, you can return an error if that session id is
presented
> again.
I'd probably handle this instead by computing an identifier for the
transaction and including it as a hidden form field on the submi
Daniel Rusch wrote:
>
> We have an Order Entry/Billing intranet site where users fill out
> several pages of data an then submit the information. After the order is
> submitted we would like to prevent them from backing up and resubmitting
> the same order. Is there a way to prevent them from doi
All,
Has anyone figured out a way to prevent a user from going "Back" to a
page once they have passed it.
The situation:
We have an Order Entry/Billing intranet site where users fill out
several pages of data an then submit the information. After the order is
submitted we would like to preve
