http and https version of same site, setup help needed

Apple still use Apache as the webserver in Mountain Lion Server. Unfortunately they no longer provide the ability to configure via a GUI many of the options you used to be able to. Server Admin in Snow Leopard was effectively a GUI tool for 'editing' the apache.conf file.

For Mountain Lion Server you are going to have to manually edit the apache.conf file. If your settings are otherwise the same i.e. host names, websites, etc. there is a good chance you could copy across your old apache.conf file.

I suggest you read your old apache.conf first. I believe it is possible for it to be configured to 'include' additional files. Also have a look at the following.

http://support.apple.com/kb/HT4813

Erich Wetzel wrote:

John,

Are you referring to httpd.conf? If not where is apache.conf?

Oops my bad, it has been httpd.conf for a long time even in Snow Leopard.

See http://smartwebdeveloper.com/mac/httpd-conf-location-mac

If I remember in the now dim and distant past, when the Apache organisation only did a webserver it was apache.conf but they now have multiple projects so the appropriate configuration file is now specific to httpd i.e. the webserver.

rewriting those configs manualy will make problems for future GUI editation (I went through that on Lion). After some time I discovered that the most problems are caused by running community tools. Therefore the easiest solution for me, that helped to keep me using gui was assigning another IP to the network interface and in default web with wiki limit using only to one IP. than on second IP I was able set all other webs I needed, without conflicting with community tools.

Also what I did was, I use www.domain.com on the second IP and leaving wiki on hostname.domain.com:443 than I am using www.domain.com as main portal for all other webs.

This is the problem with Apple dumbing down their tools. However according to the Apple KB article I listed the main httpd.conf is not over-written by Server.app so any additions you make in that will be preserved.

In System Preferences go to networking and add new interface, select Ethernet and set the IP. after adding the interface, set second Ip to it.

Than ping to that IP if it works. It did for me. Than ou can setup web part.

Erich Wetzel wrote:

We do not want to force all pages to be browsed on port 443. All we want to do is force certain pages to be encrypted for use by our staff only.

It sounds like you just need to add one or two Redirect or RedirectMatch rules on the insecure site redirecting certain pages to the secure site. This can be done in Server.app -> Web -> insecure site -> Redirects. You don't need to do any manual configuration file editing for this.