301 vs 302

2011-06-03 Thread Mark
A have an onActivate method like this: Object onActivate(EventContext context) { //we have what we need to render the page if(context.getCount() == 2) { this.keyword = context.get(String.class,0); this.page = context.get(Integer.class, 1);

Re: 301 vs 302

2011-06-03 Thread Josh Canfield
Is there a simple way to do something similar and get a 301 permanent redirect? In particular, can I modify the PageRenderLinkWithContext to control the type of redirect? Tapestry eventually calls ServletResponse.sendRedirect, which is always a 302. If you want to send a 301 you have to do it

Re: 301 vs 302

2011-06-03 Thread Mark
Perfect. Thank you. On Fri, Jun 3, 2011 at 12:41 PM, Josh Canfield joshcanfi...@gmail.com wrote: Is there a simple way to do something similar and get a 301 permanent redirect? In particular, can I modify the PageRenderLinkWithContext to control the type of redirect? Tapestry eventually

Re: 301 vs 302 redirects due to SEO

2010-01-16 Thread Stephan Schwab
://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-tp27165953p27191977.html Sent from the Tapestry - User mailing list archive at Nabble.com

Re: 301 vs 302 redirects due to SEO

2010-01-15 Thread Lutz Hühnken
Stephan, you can extend the possible return types of the onActivate method by adding a ComponentEventResultProcessor to you configuration. You can define an HttpStatusCode class that returns the code you wish. I don't know if you consider this clean, but it takes HTTP internals, codes etc. out

301 vs 302 redirects due to SEO

2010-01-14 Thread Stephan Schwab
://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