Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Click here to return to the 'How to create a secure (HTTPS) OS X webserver' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
How to create a secure (HTTPS) OS X webserver
Authored by: jecwobble on Dec 01, '04 01:44:26PM

I can only speak for Safari on OS X and Internet Explorer on XP: they don't exactly "choke" as much as "hiccough". On a per-session basis, I get prompted with a warning message about the certs, but once I accept this, I can load pages just fine.

Since I am pretty much the only surfer of my pages (I have mine secured with mod-auth, too), I don't mind the minor inconvenience. If others were surfing, I might go ahead and get a real domain name and use one of the cert authorities.

On a side note- I would prefer to use mod-digest instead, but IE really chokes on some of my PHP pages then. Since I am using SSL, am I correct that that covers my mod-auth also? In other words, eventhough the password is sent in the clear, it's sent in the clear THROUGH SLL, so it's encrypted, right?

[ Reply to This | # ]
How to create a secure (HTTPS) OS X webserver
Authored by: _merlin on Dec 01, '04 06:34:03PM

Yes, it is sent over the encrypted link, so it isn't clear-text. Digest authentication is flawed, anyway, so you really need SSL even when you use it.

[ Reply to This | # ]