joined:Aug 14, 2011
I'd be happy if I can be referred to another thread/post if one is around.
The situation is as follows:
Am planning on 301 redirecting
://www.example.com/default.asp to https
://www.example.com/default.asp or just 301 to https
However here are the issues. While through the setting of IIS server
configuration this is easily done. Here is what the hosting company are saying.
1. Redirects on a custom application are not controlled by IIS.
2. They are using a combination of
2.1. ISAPI re-writes,
2.2. Application embedded code (ASP) and load balancer regex
3. They can redirect the default.asp using a 301 method, however cannot redirect all pages using 301 method because the platform is presenting HTTP pages to the load balancer which then presents them back to the end user as HTTPS. A load balancer is a proxy, and proxy hosts cannot re-represent end host SSL, they must present their own SSL conversation, which is why the SSL certificates are bound to your load balancer.
4. Question is would you still do the 301 redirect?
5. The above situation/issue is also holding off the change where we are keen to add a "canonical tag" across all pages. Web Hosting is recommending that they can organise the "canonical tag" at the presentation layer of the CMS.
In my opinion, I believe it is fine to go ahead, however am keen to see what other experts have to say about this.
[edited by: Ocean10000 at 2:55 am (utc) on Aug 22, 2011]
[edit reason] Switched to Example Domain [/edit]