I don't think it's a bug Anders. As far I know the umbracoRedirect has always been 302 redirect.
But I do aggree with you. It's would be a good idea to put an option of a 301 redirection into the core of Umbraco. It could be great to have something like the Permanent Redirect package build in. Makes good sense in my opinion.
@Kim yes that package is the solution - but why not just correct it in umbraco 4.5.2 that will be released shortly? Ist a small thing to correct i could imagine and would do it my self if i did know how to get access to the source and commit changes ( any core members that can help with that? )
Agree with Kim that it would be nice to have the option of a permanent or temporary redirection when using umbracoRedirect property.
Yet I think the 302 is actually the right one here: as you can set it to a different page whenever you feel like it in the CMS it is actually not a permanent redirect, it might just be temporary or not a redirect at all if you delete the value. So it would be odd to tell a search engine that the Url has been permantently redirected yet when it checks back (if it does that) it will find new content which hasn't been properly indexed because it was marked 'permanent redirect'.
Anyway, had to write a custom 301 status changer for redirects for a previous project so would appreciate to get the option. Yet with the option it's probably not that simple a change.
umbracoRedirect doing it wrong
Why is umbracoRedirectreturning a 302 and not a 301? It should in my view do a 301
I don't think it's a bug Anders. As far I know the umbracoRedirect has always been 302 redirect.
But I do aggree with you. It's would be a good idea to put an option of a 301 redirection into the core of Umbraco. It could be great to have something like the Permanent Redirect package build in. Makes good sense in my opinion.
/Kim A
@Kim yes that package is the solution - but why not just correct it in umbraco 4.5.2 that will be released shortly? Ist a small thing to correct i could imagine and would do it my self if i did know how to get access to the source and commit changes ( any core members that can help with that? )
Agree with Kim that it would be nice to have the option of a permanent or temporary redirection when using umbracoRedirect property.
Yet I think the 302 is actually the right one here: as you can set it to a different page whenever you feel like it in the CMS it is actually not a permanent redirect, it might just be temporary or not a redirect at all if you delete the value. So it would be odd to tell a search engine that the Url has been permantently redirected yet when it checks back (if it does that) it will find new content which hasn't been properly indexed because it was marked 'permanent redirect'.
Anyway, had to write a custom 301 status changer for redirects for a previous project so would appreciate to get the option. Yet with the option it's probably not that simple a change.
Cheers,
Sascha
Hi guys
Just had to find out if it was a 302 or 301 redirect and thanks to this post it got settled :-) I've updated the wiki entry about the umbracoRedirect property to mention this: http://our.umbraco.org/wiki/reference/umbraco-best-practices/umbracoredirect
Cheers.
/Jan
is working on a reply...