> -Original Message-
> From: Gregor Schneider [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, November 21, 2007 5:33 PM
> To: users@httpd.apache.org
> Subject: Re: [EMAIL PROTECTED] Problem with NameVirtualHost and
> VirtualHost
>
> Hi Owen!
>
> On Nov 21, 20
On Wed, Nov 21, 2007 at 04:59:33PM +0100, Boyle Owen wrote:
> It is worth emphasising that this "problem" is nothing specific to do with
> apache; it's a fundamental feature of HTTP/HTTPS.
You might want to read this recent howto:
http://howtoforge.net/enable-multiple-https-sites-on-one-ip-using-
Hi Owen!
On Nov 21, 2007 4:59 PM, Boyle Owen <[EMAIL PROTECTED]> wrote:
>
> That's about right... You didn't (mercifully :-) show us your complete config,
>
well, if u need some reading-stuff. I'll send them to ypu right away
or, if you prefer, post 'em here on the list ;)
> but I'm guessing you
> -Original Message-
> From: Gregor Schneider [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, November 21, 2007 11:32 AM
> To: users@httpd.apache.org
> Subject: Re: [EMAIL PROTECTED] Problem with NameVirtualHost and
> VirtualHost
>
> hi krist,
>
>
> &g
hi krist,
>
> Are you sure? This looks like Apache behaving against its
> specification in a big way.
>
I am sure since it's working as expected.
Afaik this issue has been discussed before, I just couldn't find it.
Against what specs should Apache behave? Any URL quoting those specs?
As I'm un
On Nov 20, 2007 4:48 PM, Gregor Schneider <[EMAIL PROTECTED]> wrote:
> Guys,
>
> I've just solved the problem.
>
> As I said b4, I don't care about a message stating "SSL-cert is not
> valid" since it's just a test-server.
That's not the issue. You can't combine namevirtualhosts with SSL. So
any
Guys,
I've just solved the problem.
As I said b4, I don't care about a message stating "SSL-cert is not
valid" since it's just a test-server.
The problem was the ServerName-directive:
Now I've changed my vhost-definition to
ServerAlias test-clue
ServerAlias test-clue
.
You can't use Virtual Hosts like that with SSL. The SSL handshake
with keys etc comes before the client tells the server which host it's
trying
to connect to, so the server has to read the ssl config before then,
thus you
get the config for the first one.
Solution is to use IP based virtual
You can't to name based virtual hosting.
You need more IP addresses :)
The way SSL works is by connecting to the first host. It will then be
tied to that one forever...
You'd need to run the extra SSL sites on either extra IP addresses or
other port numbers.
D
On Tue, 2007-11-20 at 16:09 +010
On Nov 20, 2007 10:09 AM, Gregor Schneider <[EMAIL PROTECTED]> wrote:
> NameVirtualHost *:443
>
> ServerName test-clue
>
>
>
> ServerName test-dom
>
>
> When I enter the url "https://test-ltc";, I'm always sent to
> "https://test-clue";, and I kust don't understand wh
Hi Guys,
I always keep being puzzled about those options, and I also don't get
enlighted by the doc.
this is what I have:
System: Debian Etch
/etc/apache2/apaxhe2.conf:
...
NameVirtualHost *:80
NameVirtualHost *:443
...
in /etc/apache2/sites-enabled I have
file clue:
ServerName test-cl
11 matches
Mail list logo
