Forum Moderators: open

Message Too Old, No Replies

Shared IIS Server - Remote Access Setup & Redirection Help

HTTP redirection and server login help

         

Cornelius Macdougall

5:55 pm on Feb 13, 2012 (gmt 0)

10+ Year Member



Hello all,


My client has a website which is hosted on a shared IIS server. I have been asked to make some changes to that website.


I need to redirect some of the old web pages to their new web page addresses - which I know how to do on Apache by using .htaccess.

I currently have access to the FTP account and I can also access the Web Hosting Contol Panel.


I had a look in the web hosting control panel and nowhere could I find that it was possible to set up a simple web page redirect such as something which would be able to do the below:


http://www.example.com/oldpage.html (redirects to--->) http://www.example.com/newpage.html


So instead I read that you must install the "Internet Information Services Manager" software to your desktop and then log in using this software, then connect to the server and then I can change the HTTP redirect settings.


However, I have tried both the "connect to a server" and "connect to a website" options multiple times but have not had any success.


So I have some questions:


1) The ultimate goal is to change the HTTP redirect settings. Is there an easier way to do this than the way I am currently attempting?

2) How can I connect to the server properly using the "Internet Information Services Manager" software? What am I doing wrong? At the moment I am getting the "


I appreciate your help and please bear with me as I have never used IIS before and only have used Apache previously.


All the best,
Cornelius

dstiles

10:39 pm on Feb 13, 2012 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



No idea how you could connect IIS Manager to your web site but if I were the hosting company I would forbid it as a high-potential exploit node.

You can add headers into the top of any IIS file before writing out any content - ie before the Document declaration. For example...

Response.Status = "301 Moved Permanently"
Response.Expires = -1
Response.AddHeader "Pragma", "no-cache"
Response.CacheControl="max-age=1000, private, no-cache, no-store, must-revalidate, proxy-revalidate"

Response.Write "<!DOCTYPE HTML PUBLIC ""-//W3C//DTD HTML 4.01 Transitional//EN"">" & vbCrLf & vbCrLf
Response.Write "<html>" & vbCrLf
...etc...

The above is for Classic ASP. I assume it would work in .NET but there may be better ways of doing it in that.