Can I make 301 redirects on a Windows server (without access to IIS)?

[BrianAlpert78]

Hey everyone,

I've been trying to figure out a way to set up some 301 redirects to handle the broken links left behind after a site restructuring, but I can only ever find information on 2 methods that I can't use (as far as I can tell). The first method is to do some stuff with an htaccess file, but that looks like it only works on Linux-based servers. The method described for Windows servers is generally to install this IIS rewrite/redirect module and run that, but I don't think our web hosting company allows users to log directly into the server, so I wouldn't be able to use the IIS thing.

Is there any other way to get a 301 redirect set up? And is this uncommon for a web hosting company to do, or do you all just run your sites on Linux-based servers or your own Windows machines?

Thanks!

[irvingw]

Have you called the hosting company? They may say that you need to switch to a Linux box, and they migrate everything over for you. Or maybe they can help you get your redirects in place on their end.

[OlegKorneitchouk]

Try this. It uses the web.config file which is accessible via FTP.

[BrianAlpert78]

Can I create a web.config file, or is that something that needs to be set up by the hosting company (or at least whoever has access to IIS)? I suppose I could just call the hosting company (as Irving recommended).

Thanks, guys!

[ThompsonPaul]

This is a really common problem on shared Windows IIS-based hosting, Brian.

In addition to the web.config method Oleg mentions, there's another method if it's only for a few specific pages.

This method involves actually having a "placeholder" page on the server at the old URL. You then add a script to provide the 301 redirect. (Or just replace the content of the origianl page, if it's still on the server.)

For example:

On ASP.net you would create the page oldpagename.aspx and its content would be:

On ASP you'd create the placeholder oldpagename.asp and its content would be:

<%@ Language=VBScript %>
<%
Response.Status="301 Moved Permanently"
Response.AddHeader "Location", "www.mydomain.com/newpagename.aspx"
%>

Obviously this method doesn't scale as easily as the web.config method, but it's generally easier if you're just dealing with a few pages every once in a while.

Paul