-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
lb,
lightbulb432 wrote:
> So would the following be a good way of approaching this using filter
> mappings (where the filter is as described in the OP)?
> - No filter on all servlets that can, upon success or failure, redirect to
> another page
> - Fi
llowing be a good way of approaching this using filter
mappings (where the filter is as described in the OP)?
- No filter on all servlets that can, upon success or failure, redirect to
another page
- Filters on all JSPs with a ${message} anywhere in their markup
In what ways could I use the dispatcher el
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
lb,
lightbulb432 wrote:
> Redirects are used so that users don't encounter the resubmit warning by the
> browser when they refresh the page, and so that page refreshes don't result
> in the POST being resent to the server.
I know people like to avoid
E-
>
> -------------
> To start a new topic, e-mail: users@tomcat.apache.org
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
--
View this message in contex
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mark,
Mark Thomas wrote:
> lightbulb432 wrote:
>> I have a question about whether there is a race condition with the following
>> technique for displaying messages across redirects.
>
> Yes there is.
>
>> If you submit a form with an invalid value o
lightbulb432 wrote:
> I have a question about whether there is a race condition with the following
> technique for displaying messages across redirects.
Yes there is.
> If you submit a form with an invalid value on page P1 and the receiving
> servlet S redirects to another page P2, you'd like pag
n (and remove the "message" attribute) before page P2
renders, thereby leaving ${message} empty?
Thanks.
--
View this message in context:
http://www.nabble.com/Race-condition-with-values-displayed-across-redirects-tf45657
