I wasn't suggesting changing the functionality of setRedirect, but instead maybe adding setPermanentRedirect(true) or another way for wicket to be able to perform a 301.
On Wed, 2007-12-05 at 13:43 +0000, Gwyn Evans wrote: > I think the one thread was "Consistent homepage URL" from 2005Q2 - I > think the gist was that in the scenario there, it wasn't desirable > having the redirected URL becoming the one that the search engines > would always go to. > > /Gwyn > > On 04/12/2007, Johan Compagner <[EMAIL PROTECTED]> wrote: > > Long long time ago we had discussions about this, i think also related > > to what google expects. I guess what we now have is a result of that. > > But i cant remember what the pros and cons are > > > > 2007/12/4, Joe Toth <[EMAIL PROTECTED]>: > > > When you setRedirect(true), wicket does a 302, temporary, redirect. The > > > basic rule of thumb in SEO is if you want to pass all authority to a > > > different page use 301 (permanent). > > > > > > http://www.seotoday.com/browse.php/category/articles/id/477/index.php > > > > > > Thoughts on adding something to Wicket to support this functionality? > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
