specifications...
-ascs
-Original Message-
From: Andrew Clarke [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 04, 2005 2:26 AM
To: Apache Users
Subject: [EMAIL PROTECTED] adding SSL - is a distinct virtual host mandatory?
SuSE 9.3 hosting Apache 2.0.53 (the build from SuSE installs
On Tue, 04 Oct 2005 16:07, Axel-Stéphane SMORGRAV wrote:
If you are planning on serving both SSL and non-SSL connections, then
yes, a separate virtual host is necessary for one of the two.
The fact is that the SSLEngine directive is only valid in a server or
virtual host context. I do not
Boyle Owen wrote:
Just to clear up some apparent confusion on this thread: I think the point everyone is missing is
that an SSL-encrypted website uses a *different protocol* than plain old HTTP. Instead of thinking
of SSL as some sort of add-on (like mod_perl) to a normal website, look
On Tue, 04 Oct 2005 16:44, Boyle Owen wrote:
Just to clear up some apparent confusion on this thread: I think the
point everyone is missing is that an SSL-encrypted website uses a
*different protocol* than plain old HTTP. Instead of thinking of SSL as
some sort of add-on (like mod_perl) to a
-Original Message-
From: William A. Rowe, Jr. [mailto:[EMAIL PROTECTED]
Sent: Dienstag, 4. Oktober 2005 08:50
To: users@httpd.apache.org
Subject: Re: [EMAIL PROTECTED] adding SSL - is a distinct virtual host
mandatory?
Boyle Owen wrote:
Just to clear up some apparent
-Original Message-
From: Andrew Clarke [mailto:[EMAIL PROTECTED]
As I mentioned on my last reply, I'm hoping that http://myserver and
https://myserver both work; the first on :80 and the 2nd on
:443. Am I
expecting too much? Is this unpossible?
This is fine. The use of https in
On Tue, 04 Oct 2005 17:06, Boyle Owen wrote:
Well, I was trying to clear some confusion without everyone's eyes
glazing over. That inevitably means taking shortcuts with the precise
details of HTTPS session negotiation.
Heh. Computers are tricky things. Sometimes our eyes NEED to glaze over.
Andrew Clarke wrote:
You've all been great helps so far. I hope I haven't inspired a flame-war
amongst yourselves. The help here is quite speedy and of high quality.
Congratulate yourselves, and please, buy yourselves a beer on my behalf.
Feel free to buy a draft for Boyle (should he get
Yes, I can see the need for a separate port, but it's not clear why VH's
are/must be used to separate off the HTTPS activity on port 443.
As I mentioned on my last reply, I'm hoping that http://myserver and
https://myserver both work; the first on :80 and the 2nd on :443. Am I
expecting too
On Tue, 04 Oct 2005 17:20, William A. Rowe, Jr. wrote:
Feel free to buy a draft for Boyle (should he get there) and myself at
ApacheCon/US '05 (www.apachecon.com).
If but someone would pay for me to take a junket overseas for a conference.
I'm in Sydney. Shouldn't you guys schedule these
On Tue, 04 Oct 2005 20:00, Paul Annesley wrote:
Specifying http:// will cause the browser to use port 80 by default.
Specifying https:// will cause the browser to use port 443 by default.
However, apache does not automatically assume that 80 == http and 443
== https, you need to use the
Andrew Clarke wrote:
On Tue, 04 Oct 2005 17:20, William A. Rowe, Jr. wrote:
Feel free to buy a draft for Boyle (should he get there) and myself at
ApacheCon/US '05 (www.apachecon.com).
If but someone would pay for me to take a junket overseas for a conference.
I'm in Sydney. Shouldn't you
SuSE 9.3 hosting Apache 2.0.53 (the build from SuSE installs) and Firefox
1.0.6 for a self-contained server and workstation on a laptop.
I'm working on getting https working for the first time, and keep reading
hints that it's usual to make another virtual host to carry the SSL. Is
this
I believe the error you are getting is often caused by trying to serve
plain HTTP on port 443, instead of HTTPS which the browser is
expecting..
Regards,
Paul
On 10/4/05, Andrew Clarke [EMAIL PROTECTED] wrote:
On a closely related topic, I eventually reached the point of creating a
No it is not required to have a separate virtual host,
at least not for Apache itself. I am running V2.054
http and https on FreeBSD V5.3 with no problem.
BZAG
=
--- Andrew Clarke [EMAIL PROTECTED] wrote:
SuSE 9.3 hosting Apache 2.0.53 (the build from SuSE
On Tue, 04 Oct 2005 10:36, Paul Annesley wrote:
I believe the error you are getting is often caused by trying to serve
plain HTTP on port 443, instead of HTTPS which the browser is
expecting..
That's a reasonable suggestion. I have not set any parameters which tell it
what port serves which
16 matches
Mail list logo
