Handling non-aspx request in the 301 Url Tracker - a concrete suggestion for improvement
Hi
We really like your package, and try to use it as our Swiss army knife of URL migration for our client. We apply some URL rewriting ninja tricks for handling non-aspx pages. E.g.:
Everything works and Google bot is happely crawling the sites and becomes aware of the new URLs.
One thing is nagging me though. And that is that we have to instruct the webmasters to use the rewritten URL for the custom mapping property (/htm/oldpage.aspx). It would be very cool if the webmaster could write what the browser actually requests (/oldpage.htm).
Would it not be possible to add support for rewriting the url in the lookup you do in the infocaster301 table. Eg. select * from infocaster301 where OldUrl = ''/oldpage.htm" instead of the rewritten URL (/htm/oldpage.aspx).
You could create a configuration option to allow for supporting this scheme?
Handling non-aspx request in the 301 Url Tracker - a concrete suggestion for improvement
Hi
We really like your package, and try to use it as our Swiss army knife of URL migration for our client. We apply some URL rewriting ninja tricks for handling non-aspx pages. E.g.:
This works like this.
Browser requests: /oldpage.htm
URL rewrite: /htm/oldpage.aspx
301 Redirect: /oldpage
Everything works and Google bot is happely crawling the sites and becomes aware of the new URLs.
One thing is nagging me though. And that is that we have to instruct the webmasters to use the rewritten URL for the custom mapping property (/htm/oldpage.aspx). It would be very cool if the webmaster could write what the browser actually requests (/oldpage.htm).
Would it not be possible to add support for rewriting the url in the lookup you do in the infocaster301 table. Eg. select * from infocaster301 where OldUrl = ''/oldpage.htm" instead of the rewritten URL (/htm/oldpage.aspx).
You could create a configuration option to allow for supporting this scheme?
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.