October 10, 2003
@ 10:27 AM

Since I moved websites I'd like people to access my dasBlog RSS feed as opposed to my old RSS feeds. However whereas getting a web server to send a 301 (Moved Permanently) result to a client is a piece of cake in Apache (simply edit some config file) it seems to be a bitch and a half in IIS.

If anyone has any tips or tricks as to how to setup IIS 5.1 running ASP.NET to send 301s I'm all ears.


Friday, October 10, 2003 12:16:13 PM (GMT Daylight Time, UTC+01:00)
This may help: http://www.agiledeveloper.com/articles/CustomErrorsASPDOTNET.pdf

The general steps to apply this in IIS afaik:
1) move all files/folders to be redirected to a subfolder, e.g. "redireced"
2) Install/configure a "File not found error handler (.asp, aspx file)
3) Put some redirection code in there that may use the Response.Status property to initiate a "301 #redirection url')
Friday, October 10, 2003 5:08:22 PM (GMT Daylight Time, UTC+01:00)
Assuming I'm not missing the point, this is trivial with IIS.

1. In Internet Services Manager, find the particular file you want to redirect.

2. Right-click on the file, and go to "Properties"

3. On the File tab, select "A redirection to a URL"

4. Enter the URL, and check the "A permanent redirection for this resource" option.
Friday, October 10, 2003 5:32:32 PM (GMT Daylight Time, UTC+01:00)
Wow, you're right Greg it is pretty trivial. Now I worry that if I do a permanent redirect that it would break anybody using an aggregator that doesn't support HTTP 301. :(

I'll have to think about this for a while.
Friday, October 10, 2003 9:22:50 PM (GMT Daylight Time, UTC+01:00)
How about static RSS files at the old location that have one entry with the current date? That entry could be just a link to the new location.
Comments are closed.