Thanks for the additional info.
David
On Thu, Aug 30, 2018 at 1:01 AM, Gillis J. de Nijs
wrote:
> Also see https://wiki.apache.org/httpd/NameBasedSSLVHosts
>
> As a rule, it is impossible to host more than one SSL virtual host on the
>> same IP address and port.
>
> This is because Apache needs
Also see https://wiki.apache.org/httpd/NameBasedSSLVHosts
As a rule, it is impossible to host more than one SSL virtual host on the
> same IP address and port.
This is because Apache needs to know the name of the host in order to
> choose the correct certificate to setup the encryption layer.
T
It is.
If you try to disable myhost.domain1.org - you will see that
myhost.domain2.org will work over SSL/TLS :)
On 2018-08-29 19:19, David Rush wrote:
Ah, so SNI is dependent on the operating system, not the version of
Apache HTTPD installed?
I had read about SNI and understood the basics
Ah, so SNI is dependent on the operating system, not the version of Apache
HTTPD installed?
I had read about SNI and understood the basics of it, but assumed that it
was a function of HTTPD version rather than older OS version.
Thanks for your help.
David
On Wed, Aug 29, 2018 at 11:00 AM, Jonat
I am very sure that this has to do with the fact that older machines
simply does not have support for SNI.
On 2018-08-29 16:28, David Rush wrote:
I'm running httpd 2.4.12 on Windows Server 2003.
We have things set up and working with http and https using the
primary host name (fully qualified
I'm running httpd 2.4.12 on Windows Server 2003.
We have things set up and working with http and https using the primary
host name (fully qualified).
We need for a different domain (same hostname) to work with https.
These both need to work:
https://myhost.domain1.org - this works fine
https:/
