Redirect (by design) uses an HTTP GET request method. This means the only way to pass values is in the URL. If your data is small enough, you could encode/encrypt it into the URL and decode it back after the redirect - an approach that isn't clean and I wouldn't recommend. (Also, the URL is limited to 256 characters length).
The only other option is the session. Nils-Helge Garli wrote: > > > Well, it sounds like something that shouldn't be possible to me... It > kind of violates the whole concept of a redirect. If you really want > the data to be a part of the URL, you could do some encoding to make > them less readable and shorter. > > Nils-H > > On Thu, Apr 24, 2008 at 10:12 PM, Allen, Daniel <[EMAIL PROTECTED]> > wrote: >> I can, and I considered that, but I was hoping to keep it in the XML to >> minimize the number of files that need to be changed. The documentUpload >> action that's the redirect target below is actually the recipient of >> quite a few links (in fact the basic point of the application is to >> facilitate document submission for various purposes). >> >> If this isn't possible purely via configuration, then yeah, session >> storage is definitely my fallback plan. >> >> ~DVA >> >> >> >> -----Original Message----- >> From: Nils-Helge Garli Hegvik [mailto:[EMAIL PROTECTED] >> Sent: Thursday, April 24, 2008 3:58 PM >> To: Struts Users Mailing List >> Subject: Re: Redirect-action parameters via POST >> >> Can you put the info on the session? >> >> Nils-H >> > > -- View this message in context: http://www.nabble.com/Redirect-action-parameters-via-POST-tp16884951p16893112.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]
