>From: Danalien [mailto:[EMAIL PROTECTED]]
>
>As I know, you can only bind one uniqe ip to one SSL virtual host.
not quite - see below..
>and from what I have read, you can't use name-based SSL
>virtual host(s) either,
>as a work around.
Mostly right, but with one privisio: You cannot do name-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi.
As I know, you can only bind one uniqe ip to one SSL virtual host.
and from what I have read, you can't use name-based SSL virtual host(s) either,
as a work around.
please correct me if I'm misstaking, anyone, I am only using 1.3.24.
>
>I h
I have tried to configure a port-based virtual hosts with the following
ports:
443
444
445
446
447
Is there a better how-to than on the apache site? I'm using apache
2.0.39 and would like to see an example. I follow the text and keep
getting the same error message. Keep in mind that port
Brandon DeYoung wrote:
>
> I have a similar problem...hopefully someone has as good an answer.
>
> I've got a bunch of virtual hosts running on port 80 just fine. I also have
> a single HTTPS running on 443. I'd like to have multiple SSL hosts. So far
> all my attempts have ended
he/logs/ssl_request_log \
"%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jason Paul McCartan
Sent: Tuesday, December 19, 2000 7:11 AM
To: [EMAIL PROTECTED]
Subject
Hi Owen
Thanks for the reply
Owen Boyle wrote:
>
> Jason Paul McCartan wrote:
> > Recently though the server was used to add other name-based virtual domains.
> > Now the SSL through HTTPS is totally unavailable, and when we tried to view
> > anything over HTTPS we get a blank "Page Not Found"
Jason Paul McCartan wrote:
> Recently though the server was used to add other name-based virtual domains.
> Now the SSL through HTTPS is totally unavailable, and when we tried to view
> anything over HTTPS we get a blank "Page Not Found" page. We have no problem
> on port 80 for any of the sites.
I'd like to get an opinion from the experts on a problem we've ran into.
We use Redhat 6.1 at the moment and Apache/1.3.9 (Unix) Red-Hat-Secure/3.1
mod_ssl/2.4.10 OpenSSL/0.9.4 as installed by our hosting company on our
dedicated machine.
When we first kicked the server into life we were using o
On Sat, Sep 09, 2000, Matthew Asham wrote:
> A question I couldn't find in the FAQ..
> Does TLS work with Virtual Hosts?
No, TLSv1 is equal to SSLv2/v3 when it comes to this problem. Only the
new RFC2817 stuff would solve the problem.
Ralf S. Engelschall
age-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of James Treworgy
> Sent: Friday, September 08, 2000 9:22 AM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Virtual Hosting problem
>
>
> RTFA ;-)
>
> Virtual hosting does not work with
Whoops, I did go through the FAQ, I just didn't read that item since
it's worded kinda strange. Sorry,
Tom
"Thomas E. Ruth" wrote:
>
> Hello,
>
> I have a little but I found that I'd like to report.
>
> I am using the NameVirtualHost facility of Apache together with SSL. The
> problem comes w
ms Engineer
PFK Business Systems, Inc.
(972) 621-0300
www.pfk.com
> -Original Message-
> From: Thomas E. Ruth [mailto:[EMAIL PROTECTED]]
> Sent: Friday, September 08, 2000 11:11 AM
> To: [EMAIL PROTECTED]
> Subject: Virtual Hosting problem
>
>
> Hello,
>
&
RTFA ;-)
Virtual hosting does not work with SSL. Each site must have its own IP.
Jamie
At 12:10 PM 9/8/00, Thomas E. Ruth wrote:
>Hello,
>
>I have a little but I found that I'd like to report.
>
>I am using the NameVirtualHost facility of Apache together with SSL. The
>problem comes with the en
Hello,
I have a little but I found that I'd like to report.
I am using the NameVirtualHost facility of Apache together with SSL. The
problem comes with the environment variable DOCUMENT_ROOT that Apache is
setting.
When using http to connect, loading up a phpinfo.php page will give the
environm
14 matches
Mail list logo
