Brad A Cupit wrote: > > Having said that, I question using the session, since > redirect-after-post was designed to help alleviate back and refresh > button problems. If we store information in the session for the > redirect, then the first GET will find that information, but subsequent > GETs (perhaps the result of pressing back or refresh) will not find that > information, so the GET will have been inconsistent. >
Precisely. Using the session to store data across a redirect does indeed lead to a misbehaving GET. More importantly, IMHO the need to preserve data this way indicates a design flaw - Redirect was designed to use GET and there are always (perhaps, not-so-easy) alternatives to keep it that way. That said, one occasion when I was forced into using the session this way was when I wrote a custom solution to redirect across HTTP and HTTPS (like when a secure resource is accessed via HTTP) for Struts, working very similar to the SSL plugin. -- View this message in context: http://www.nabble.com/Is-there-such-a-thing-as-flash-in-S2--tp16697840p16935302.html Sent from the Struts - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
