RE: plain HTTP to an SSL-enabled server port

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> -----Original Message-----
> From: Thomas Antony [mailto:thomas@xxxxxxxxx] 
> Sent: Monday, December 10, 2007 12:30 PM
> To: users@xxxxxxxxxxxxxxxx
> Subject: Re:  plain HTTP to an SSL-enabled server port
> 
> Hi,
> 
> This works.
> Is there a technical reason why i need 2 virtual hosts instead of one?

Because HTTPS and HTTP are two different protocols.

HTTPS is a protocol that encapsulates HTTP. That is, when you type in an
HTTPS URL in a browser, it first tries to establish an SSL-session with
the server's mod_ssl engine. Once that's up, the browser and server then
use HTTP in the normal way, but each frame is encrypted and decrypted at
the interfaces. So at the start of a session, the server listening on
port 443 is an HTTPS server and cannot receive plain HTTP requests. So
you need a second VH to listen to HTTP traffic and redirect it to HTTPS.

Rgds,
Owen Boyle
Disclaimer: Any disclaimer attached to this message may be ignored. 


> Is it safe that both virtual hosts share the same log files?
> 
> 
> 
> >  You need to create 2 virtual hosts: one for port 80 where 
> SSL is NOT enabled, and one on port 443 where SSL is enabled. 
> You will also need two Listen directives: one for each of 
> ports 80 and 443.
> > 
> > Listen *:80
> > Listen *:443
> > 
> > <VirtualHost *:443>
> > 
> >    ServerName my.server.com:443   
> > 
> >    SSLCertificateFile /sslcerts/crt/my.server.com.crt
> >    SSLCertificateKeyFile /sslcerts/key/my.server.com.key
> >    SSLEngine on
> > 
> > </VirtualHost>                                  
> > 
> > <VirtualHost *:80>
> > 
> >    ServerName my.server.com:80   
> > 
> >    SSLEngine off
> > 
> > </VirtualHost>                                  
> 
> ---------------------------------------------------------------------
> The official User-To-User support forum of the Apache HTTP 
> Server Project.
> See <URL:http://httpd.apache.org/userslist.html> for more info.
> To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
>    "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
> For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
>
 
 
This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please notify the sender urgently and then immediately delete the message and any copies of it from your system. Please also immediately destroy any hardcopies of the message. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. The sender's company reserves the right to monitor all e-mail communications through their networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them to be the views of the sender's company.

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
   "   from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx



[Index of Archives]     [Open SSH Users]     [Linux ACPI]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Squid]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux