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 wa
> -Original Message-
> From: Thomas Antony [mailto:[EMAIL PROTECTED]
> Sent: Monday, December 10, 2007 12:30 PM
> To: users@httpd.apache.org
> Subject: Re: [EMAIL PROTECTED] plain HTTP to an SSL-enabled server port
>
> Hi,
>
> This works.
> Is there a
SL in which you add information about the ciphersuite if required.
-ascs
-Message d'origine-
De : Thomas Antony [mailto:[EMAIL PROTECTED]
Envoyé : lundi 10 décembre 2007 12:30
À : users@httpd.apache.org
Objet : Re: [EMAIL PROTECTED] plain HTTP to an SSL-enabled server port
Hi,
This
Hi,
This works.
Is there a technical reason why i need 2 virtual hosts instead of one?
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
ECTED]
Envoyé : lundi 10 décembre 2007 11:30
À : users@httpd.apache.org
Objet : [EMAIL PROTECTED] plain HTTP to an SSL-enabled server port
Hi,
I bought a Thawte certificate and configured that in Apache 2.2 with a IP based
virtual host.
SSL is working fine but everytime i open the site with http
Hi,
I bought a Thawte certificate and configured that in Apache 2.2 with a
IP based virtual host.
SSL is working fine but everytime i open the site with http:// i get
this error message displayed:
Bad Request
Your browser sent a request that this server could not understand.
Reason: You're sp
