301 Redirect Option for "Additional Urls"Cancel

The forums are in read-only mode. In case that you want to directly contact the Progress Sitefinity team use the support center. In our Google Plus group you can find more than one thousand Sitefinity developers discussing different topics. For the Stack Overflow threads don’t forget to use the “Sitefinity” tag.

hello again! I am in the process of replacing our existing website with the sitefinity cms. I love the feature of additional urls which will allow me to use the old links and show the new content that is replacing it, however, the way that it is set up, putting in the old url (added as an additional URL in the page properties) does not redirect to the correct page, rather it intercepts it and renders it as if they had loaded the correct page.

this is not the behavior that I want because we would then have two different urls for the same page. what I want to do is be able to catch the old url, and REDIRECT to the correct default one, with 301 so that it is search engine friendly. is this a possibility?

The original idea of additional URLs is to provide simple way for URL rewriting without using regular expressions. However, your idea makes perfect sense indeed. We will try to add this option for the next release which should be out in a couple of weeks.

I've hit a snag while using this feature. I think there are two possible reasons why it's not working so let me tell you what I did and maybe you can see what's going on internally, thanks.

I have a page which is located at site.com/subsection/dynamicpage.aspx. This is the current, permanent location for this content, however previous to our adopting sitefinity, this page was located at site.com/dynamicpage.aspx. I added the additional url to be ~/dynamicpage and forwarded it to the current correct page and it works just as I expected.

However, not too long before that, this content was on a STATIC, html only page. the link to that was site.com/staticpage.htm. I need to be able to forward BOTH the old site.com/dynamicpage.aspx AND the OLDER site.com/staticpage.htm to the new permanent page of site.com/subsection/dynamicpage.aspx. I have set an additional url for the old, static, html only version of the page and set it to forward to the correct url, however when I run that link,I see the correct content from the permanent new page, but in the address bar it still says site.com/staticpage.htm and doesn't forward the URL to the correct one.

it might be that it's not forwarding from a root directory to the new subdirectory, but as I say above, the middle link site.com/dynamicpage.aspx DOES forward correctly...

so it seems more likely that it's the htm extension that's killing it. Do I have to map this extention to run through sitefinity or something? why does it display the content correctly, but not forward the url?

okay hmm here's some more information... it seems that this problem only occurs the first time that I visit the url. I set the additional urls as specified above, and after that I type the oldest address to see if it works, and like I said I see the new content, but it doesn't forward the url, leaving me at site.com/staticcontent.htm.

but then if I refresh the page, it DOES forward me to the correct url, but it appends ?404;http://site.com/staticpage.htm to the end. This doesn't seem right, I know it's gotta be a problem with my 404 and/or extensionless url handling, but I'm starting to get lost here. any insight you can provide will be very much appreciated.

We were able to test Sitefinity 3.2SP2 as well as the Hotfix under different environments and saw that the problem described really exists. We have logged this issue with high priority and it will be fixed as soon as possible.

Tools

Sitefinity Professional Services

Progress, Telerik, Sitefinity and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries.