Event handlers in Tapestry, such as onActivate() may return a page object or page name. That gets translated into a HTTP 302 redirect.
Now there are situations, e.g. in shopping applications, where one needs to use 301 (moved permanently) redirects instead. One can @Inject the Response object, set the status to 301 and the location in the HTTP header. That works but it makes you mix framework code with application code in a page class which feels a bit wrong. Is there a cleaner way? Stephan ----- -- http://www.caimito.net - Caimito One Team - Agile Collaboration and Planning tool http://www.stephan-schwab.com - Personal blog http://code.google.com/p/tapestry-sesame - Authentication extension for Tapestry 5 -- View this message in context: http://old.nabble.com/301-vs-302-redirects-due-to-SEO-tp27165953p27165953.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
