Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

http to https redirect on sharepoint 2007 1

Status
Not open for further replies.

bshbsh

Technical User
Apr 11, 2007
163
US
This must be a old topic. I did try to search for previous posts, but couldnt find anything useful.

But has anyone had any success redirecting http to https on IIS 6. I found a bunch of ways this could be possible (using asp and javascript), but unfortunately nothing seems to work, I get the same message,

Secure Channel Required
This Virtual Directory requires a browser that supports the configured encryption options

What should I do.
Please advice.
Thanks.
 
I don't use Sharepoint... but could you use a Meta redirect?

Redirecting to a New Page

While the reload option is useful, it is usually not what people want from the meta refresh tag. To redirect to a new page, the syntax is nearly the same:

<meta http-equiv="refresh" content="2;url=https://webdesign.about.com">

The only difference is in the content attribute.

content="2;url=http://webdesign.about.com"

The number is the time, in seconds, until the page should be redirected. Then, separated by a semi-colon (;) is the URL that should be loaded.

Jesse Hamrick
 
Is this done on the default.asp page.
 
Did this at USF Health to meet HIPAA compliance when implementing WSS 2.0 after a few beta sites were implemented.

1. move your "default web site" to port 8080 for http, keep 443 for https

2. create a new web site on port 80 for http, whatever you please for https

3. make the new site SSL only

4. put your rewriter script on the new site and assign it to handle 401.3 errors (we skipped .net and went with plain asp since it was on a separate site from sharepoint)

5. user goes to port 80, denied, script adds the necessary "s" in the protocol and sends the proper page

6. make the default web ssl only after wrapping up.

There may be a few incremental steps missing (it was a while ago and I didn't walk out with the process notes), but it got the job done without a lot of hassle and was transparent.

Neil Bailey
Sr. Microsoft Practice Consultant
EMC Global Services
 
Ahh, the missing step.

On the secondary redirect site, create a directory to hold your asp script, give it an independent application from the root and make it non-ssl accessible to beat the endless 401.3 cycle.

Neil
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top