Patrick Lightbody wrote:
But if they go back to that form, not by clicking the back button, but
through navigation links, the url "foobar.html?foo=bar" still won't work.
Sure it does. If you click something other than foobar.html, then that
association is removed. When the form is rendered again, due to the user
navigating to that page, the forum URL is again associated with the action.
We
need sometime random/unique with each page generation so that they can still
use the form when they don't do something silly like press the back button
or click submit twice. Am I just missing it?
Yup. After a form is rendered there are a couple of options. No matter
what the user clicks the association will be reset. *IF* the URL that
the user clicked happened to have an action, then it is executed.
Otherwise the only that happens is that the <user/URL/action> tuples are
removed so that any other access by <user/URL> yields no action.
Is the url tag informing the SerlvetDispatch/Filter that "soon" a request
will come in with that URL pattern, and that once it does, any following
ones should be ignored until the next <xw:url/> tag is called?
Yup.
/Rickard
--
Rickard Öberg
[EMAIL PROTECTED]
Senselogic
Got blog? I do. http://dreambean.com
-------------------------------------------------------
This SF.NET email is sponsored by: Thawte.com
Understand how to protect your customers personal information by implementing
SSL on your Apache Web Server. Click here to get our FREE Thawte Apache
Guide: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0029en
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
