Hi,
Your problem sounds like you are using a forward tag which might be like -
forward name=success path=/my_page.jsp /
Try this -
forward name=success path=/zip_inquiry.jsp redirect=true /
This should solve your repost problem.
This is very beautifully explained in Chuck Cavances
Hubert:
Thanks for the info. Based on my attempts, and speaking from a position
of ignorance I believe I am unable to use transaction tokens from my
initial login. I believe it's due to the way I set up entry into the web
app. ??
http://entryURL/ --forward index.jsp (submit to loginAction)
configuration file
In reponse to why I didn't use Google: I have been for well over 4 hours.
Google conclusions: setting nocache in web.xml is deprecated. I should
set my controller to nocache=true
my controller in struts-config.xml now looks like:
controller processorClass
In your struts-config.xml controller element, thus:
controller
set-property property=nocache value=true/
/controller
Jay
- Original Message -
From: [EMAIL PROTECTED]
To: Struts Users Mailing List [EMAIL PROTECTED]
Sent: Monday, February 09, 2004 10:58 AM
Subject: Setting nocache
Hi Jay:
Thanks for the response. That didn't have the intended result but, it
appears to be working when I look at the headers.
Maybe my goal's not clear?
Outline of steps in my web app. and where I want to prevent repost as
follows:
1) http://host:port/afadmin/
presents login form
2) On
Take a look at Struts transaction tokens. That will help provide your Action
with a flag to ignore successive transactions (in this case, logins), even
when the user hits ok on the resend prompt.
If you don't want the user to even see the resend prompt, you can redirect to
the view after the
6 matches
Mail list logo