http:// is *NOT* the same thing has https:// .. therefore, http://host:443 is a standard HTTP request to port 443, it is *NOT* a HTTPS request.
URL 101 is in session! protocol://user:pass@host:port/uri and since "http" is not the same thing as "https", the server is simply giving you back precisely what you asked for .. non-secure http from port 443 .. which it doesn't know how to do since it's only designed to speak secure http. no wonder you found IIS5 to be "better" than in the past .. Microsoft doesn't understand what RFCs are either. ::sigh:: -dsp [EMAIL PROTECTED] wrote: > > Hi guys! > I am Apache webserver user too. I don't know how long... IIS5 is much better > now than in the past. > I had have this problem in the past using Apache. > As far as I know, seems that apache use distinct IPs for every virtual SSL > host configured. > So I see no solution for you unless if you could build a second SSL virtual > server using other port than default port 443. > Suppose that will work how will access browsers your website using > encryption? > Browsers know to communicate encrypted using https protocol witch is default > set on 443 port. > Why am I saying that? > I made few tests: > 1. http://www.inetsoft.ro:443 who generated these: > Bad Request > Your browser sent a request that this server could not understand. > Reason: You're speaking plain HTTP to an SSL-enabled server port. > Instead use the HTTPS scheme to access this URL, please. > > Hint: https://www.inetsoft.ro:443/ > 2. https://www.inetsoft.ro who worked! > > 3. I changed 443 port in 444 for one of my websites http://xxx.aaa.ro. > https://xxx.aaa.ro/ was redirected by apache to default SSL virtual host. > > Conclusion: I don't know! :) [...] ______________________________________________________________________ Apache Interface to OpenSSL (mod_ssl) www.modssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
