How to make website always load under SSL?

Question

Level 1

0 points

How to make website always load under SSL?

I basically can't find a proper solution to this question through searching the internet, so I'm hoping someone can help me.

I have just set up my server (Mountain Lion 10.8) with a website and can't seem to find a way that works and is stable for making sure if someone comes in on http://www.domain.com they automatically are pointed to https://www.domain.com.

I am finding that on server.app I have to choose one of the other (which is fine, I prefer the whole thing be https anyway), which means that whatever I choose, there's no redirecting to the proper (https) place.

I tried creating a parallel version of the domain with a redirect to solve the problem, and that works for about an hour and then server.app merges the two and suddenly it is redirecting to itself. So that doesn't work.

I've tried some back end (Apache) tricks I've found, but nothing has worked so far.

If you've had this problem and resolved it, I'd love to know what the solution really is.

Thanks!

Drew

OS X Mountain Lion (10.8.5)

Posted on Mar 5, 2014 2:12 PM

Reply

Answer 1

Best reply

paulfromburwood

Level 1

90 points

Mar 5, 2014 3:53 PM in response to Drew1212

Try this

Lets assume you want https://web.server.com

Create a site called

https://web.server.com at port 443 with an SSL

Now come out and create a site call https://webredirect.server.com at port 80 and ensure "Automatically create new folder" is on. Click create

Now double click on webredirect.server.com and change the URL at the top back to web.server.com at port 80, next to Store Site Files in, click the arrow to go to the folder, delete everything in there, and add you our HTML page with this code in it:

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

<html>

<head>

<title>{Please wait a moment...</title>

<BODY>

Redirecting to a secure page....

</BODY>

</HTML>

Obviously change https://web.server.com to be the address you want!

Reply

Answer 2

Drew1212 Author

Level 1

0 points

Mar 6, 2014 9:53 AM in response to paulfromburwood

Thanks for the suggestion. I actually did find a solution that was a variance of what I had tried and what you were suggesting:

If I set up two www.domain.com sites, ***each with their own folder*** and one SSL secured and one not SSL secured, and then set one to redirect to the other (in this case, from the non-secured to the secured one), the problem resolves itself and the system doesn't merge them.

Reply