David Loszewski wrote: > > I have a few small questions that I'm seeking answers for, any help > would be much appreciated: > > 1. Mod_SSL is working...I type in 'https://192.168.0.1' and it uses the > ssl but when I type in 'http://192.168.0.1:443' it doesn't work, comes > up saying that it can't load the page. Ideas?
URLs are encoded by protocol first. HTTP is *not* HTTPS. Plain and simple. Your suggestion might as well by wondering why http://127.0.0.1:21 doesn't make your web client a FTP client. Most web browsers *can* do FTP, provided you type ftp://... > 2. How do I make it so if I type in 'http://192.168.0.1' it goes to > 'https://192.168.0.1', pretty much so it only uses ssl, and please don't > tell me to just redirect it. You'll need to redirect it somehow, someway. The client is requesting one protocol and you want them to request another. If *you* don't redirect it, then .. uhmm .. who are you expecting will? Santa Claus is busy routing presents, not packets. Look into mod_rewrite. > 3. This is more of a curious type question, but if https is so much more > secured than http then why aren't all the big sites using it? "so much more secured" .. one uses encryption, one doesn't. HTTP isn't secure at all. As for why not.. becuase buying racks full of majorly expensive SSL accelerators to hide information you want shown to as many people as possible is $#!*ing dumb. -d ______________________________________________________________________ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
