I only use it in an action, and have never had any problems. However, I have never tried it in a screen.
Scott -----Original Message----- From: Gareth Coltman [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 17, 2002 10:08 AM To: Turbine Developers List Subject: RE: Redirects I tried both Scott. The first method doesn't seem to do anything. But I found that sending a redirect in the middle of an action (or perhaps it was a screen) would result in a garbled page being sent to the browser. ??? Anyway. I would really like to see a solid redirect component in the t3 pipeline. I don't know if you agree, but for me redirecting is really vital for making solid apps. Gareth > -----Original Message----- > From: Weaver, Scott [mailto:[EMAIL PROTECTED]] > Sent: 17 January 2002 15:05 > To: 'Turbine Developers List' > Subject: RE: Redirects > > > I just use the HttpResponse object. > > This didn't seem work well for me... > > data.setRedirectURI(URL); > data.setStatusCode(302); > > but using the HttpResponse object this worked great... > > data.getResponse().sendRedirect(URL); > > Scott > > -----Original Message----- > From: Gareth Coltman [mailto:[EMAIL PROTECTED]] > Sent: Thursday, January 17, 2002 9:49 AM > To: Turbine Developers List > Subject: Redirects > > > Hi, > > In my web development experience redirects have been an extremely useful > tool. I have used them for security, to stop repeated form submission, and > to make (sort-of) recursive components. I have had no success > (after a great > deal of work and reading of archives) getting redirects to work in Turbine > 2. It seems that the current buffer is sent back to the client along with > the redirect, which cause the browser to display half a page and then the > http header at the bottom. Has anyone successfully manage to perform a > redirect? > > All u turbine 3 guys - I noticed in the source that the redirect in > commented out - will redirecting work with a default (classic) pipeline. > > Typically I would want the following kind of logic - in this case > to prevent > the user's back button returning them to the login action after a login. > > LOGIN: > > if user's credentials are valid > Redirect to the home page > else > Just set the template to login > fi > > What do you guys think? > > Gareth > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
