-Original Message-
From: Om [mailto:[EMAIL PROTECTED]
Sent: Monday, May 29, 2006 5:53 AM
To: users@httpd.apache.org
Cc: [EMAIL PROTECTED]
Subject: Re: [EMAIL PROTECTED] separate logs for aliases
Hi Shai,
you can cross check once again in the apache2.2.2 manual.
Check
Hi Shai,
you can cross check once again in the apache2.2.2 manual.
Check the Virtual hosts section.
I read that.
That configuration is working fine.
Can you please implement that and check once.
Thanks,
Om.
Shai wrote:
On 5/26/06, Brian Rectanus [EMAIL PROTECTED] wrote:
On 5/26/06, Shai [EMAIL
On 5/26/06, Shai [EMAIL PROTECTED] wrote:
On 5/26/06, Brian Rectanus [EMAIL PROTECTED] wrote:
On 5/25/06, Shai [EMAIL PROTECTED] wrote:
Hi,
Since I'm a home user and I only have 1 IP but I still want to make
access to my SSL secured sites, I decided I can't use vhosts since
those
On 5/26/06, Brian Rectanus [EMAIL PROTECTED] wrote:
On 5/26/06, Shai [EMAIL PROTECTED] wrote:
On 5/26/06, Brian Rectanus [EMAIL PROTECTED] wrote:
On 5/25/06, Shai [EMAIL PROTECTED] wrote:
Hi,
Since I'm a home user and I only have 1 IP but I still want to make
access to my SSL
Hi,
I am using apache 2.2.2
and I am running multiple sites on SSL.
It works fine.
VirtualHost 192.168.1.3:443
# General setup for the virtual host
DocumentRoot /www/docs/site1
ServerName site1.mydomain.com
ServerAdmin [EMAIL PROTECTED]
ErrorLog /opt/apache2.2/logs/error_log
TransferLog
But everyone told me that each site needs its own IP or port to run on
when it comes to SSL
On 5/26/06, Om [EMAIL PROTECTED] wrote:
Hi,
I am using apache 2.2.2
and I am running multiple sites on SSL.
It works fine.
VirtualHost 192.168.1.3:443
# General setup for the virtual host
On 5/26/06, Shai [EMAIL PROTECTED] wrote:
But everyone told me that each site needs its own IP or port to run on
when it comes to SSL
It does. It is impossible to do name based vhosting w/SSL because of
how SSL works. SSL must negotiate before the HTTP Host header can be
seen. I don't
On 5/26/06, Brian Rectanus [EMAIL PROTECTED] wrote:
On 5/26/06, Shai [EMAIL PROTECTED] wrote:
But everyone told me that each site needs its own IP or port to run on
when it comes to SSL
It does. It is impossible to do name based vhosting w/SSL because of
how SSL works. SSL must
You can use one IP and have a secure-server as well
as a name-based virtual hosting server for port 80. Just run two instances of
Apache. The apache monitor is capable of reporting and controlling
both.
You are right that using name-based hosting on port
80 will cause the SSL-port server
On 5/25/06, Shai [EMAIL PROTECTED] wrote:
Hi,
Since I'm a home user and I only have 1 IP but I still want to make
access to my SSL secured sites, I decided I can't use vhosts since
those either need to configure different ports or separate IP per
vhost.
So what I want to use now are aliases
On 5/25/06, Bill Angus [EMAIL PROTECTED] wrote:
You can use one IP and have a secure-server as well as a name-based virtual
hosting server for port 80. Just run two instances of Apache. The apache
monitor is capable of reporting and controlling both.
You are right that using name-based
On 5/26/06, Brian Rectanus [EMAIL PROTECTED] wrote:
On 5/25/06, Shai [EMAIL PROTECTED] wrote:
Hi,
Since I'm a home user and I only have 1 IP but I still want to make
access to my SSL secured sites, I decided I can't use vhosts since
those either need to configure different ports or separate
12 matches
Mail list logo
