> Date: Tuesday, June 19, 2018 20:01:07 -0400
> From: Louis
>
> Apache 2.4 on Ubuntu 16.04LTS . We have multiple VirtualHosts
> running on port 80, one on port 8080. They are all fully
> functional...
>
> BUT for the one on port 8080 I have to explicitly append the port
> number to the URL in
On Tue, Jun 19, 2018 at 8:01 PM Louis wrote:
>
> Apache 2.4 on Ubuntu 16.04LTS . We have multiple VirtualHosts running on
> port 80, one on port 8080. They are all fully functional...
>
> BUT for the one on port 8080 I have to explicitly append the port number
> to the URL in a browser to access i
Apache 2.4 on Ubuntu 16.04LTS . We have multiple VirtualHosts running on
port 80, one on port 8080. They are all fully functional...
BUT for the one on port 8080 I have to explicitly append the port number
to the URL in a browser to access it (or the browser gets the
000-default.) No diff betw
his is not possible in Apache given
the usage of OpenSSL as the SSL/TLS library.
Does that sum it up?
Thanks,
Karl
Date: Tue, 16 Jun 2015 23:54:39 +0200
From: ylavic@gmail.com
To: users@httpd.apache.org
Subject: Re: [users@httpd] VirtualHosts, SSLPro
+0200
>> From: ylavic@gmail.com
>> To: users@httpd.apache.org
>> Subject: Re: [users@httpd] VirtualHosts, SSLProtocol, and SSLCipherSuite
>>
>> On Tue, Jun 16, 2015 at 10:48 PM, karl karloff
>> wrote:
>>> I am attempting to set up more than one subdomain
:39 +0200
> From: ylavic@gmail.com
> To: users@httpd.apache.org
> Subject: Re: [users@httpd] VirtualHosts, SSLProtocol, and SSLCipherSuite
>
> On Tue, Jun 16, 2015 at 10:48 PM, karl karloff
> wrote:
>> I am attempting to set up more than one subdomain on :443 in this
On Tue, Jun 16, 2015 at 10:48 PM, karl karloff wrote:
> I am attempting to set up more than one subdomain on :443 in this example.
>
> so something like
> sslv3.example.com:443 responds with SSLv3 only
> tlsv1.example.com:443 responds with TLSv1.0 only
> ...
>
> I wasn't aware that could be achiev
bject: Re: [users@httpd] VirtualHosts, SSLProtocol, and SSLCipherSuite
>
> On Tue, Jun 16, 2015 at 1:57 PM, karl karloff wrote:
>>
>
> AIUI This VH style is not used much and could be contributing. If you
> don't care what underlying interface/IP is used, use *:443 and
&g
On Tue, Jun 16, 2015 at 1:57 PM, karl karloff wrote:
>
AIUI This VH style is not used much and could be contributing. If you
don't care what underlying interface/IP is used, use *:443 and
ServerName inside. Otherwise, use the local interface address/IP and
ServerName inside.
--
Eric Covener
-
>> Date: Tue, 16 Jun 2015 11:17:22 +0200
>> From: sarkofag...@gmail.com
>> To: users@httpd.apache.org
>> Subject: Re: [users@httpd] VirtualHosts, SSLProtocol, and SSLCipherSuite
>>
>> Hi,
>>
>> Have y
!
Shouldn't it fail and not negotiate that?
Thanks,
Karl
> Date: Tue, 16 Jun 2015 11:17:22 +0200
> From: sarkofag...@gmail.com
> To: users@httpd.apache.org
> Subject: Re: [users@httpd] VirtualHosts, SSLProtocol, and SSLCipherSuite
>
> Hi,
>
Hi,
Have you tested with the "+"?
from docs :
Syntax:SSLProtocol [+|-]protocol ...
ex :
SSLProtocol +TLSv1.2
...
SSLProtocol+SSLv3
...
On Tue, Jun 16, 2015 at 12:37 AM, karl karloff wrote:
> Is there a way in the current Apache (2.4.x or 2.2.x) to specify an
> SSLProtocol and SSLC
Is there a way in the current Apache (2.4.x or 2.2.x) to specify an SSLProtocol
and SSLCipherSuite that affects only a singular VirtualHost?
e.g.
www.example.com requires modern encryption (i.e. TLSv1.2)
old.example.com allows only deprecated Protocols/ciphers (e.g. SSLv3)
I tried using somethin
On Wed, Dec 12, 2012 at 11:43 AM, José Francisco Álvarez Aguilar
wrote:
> 2012/12/12 Tom Evans
>>
>> It "works" just fine, you are just not understanding what is necessary
>> for it to work.
>>
>> VirtualHost uses the Host header supplied in the request to best
>> determine the website to route t
2012/12/12 Tom Evans
> It "works" just fine, you are just not understanding what is necessary
> for it to work.
>
> VirtualHost uses the Host header supplied in the request to best
> determine the website to route the request to.
>
> In order to read headers in an SSL request you need to decrypt
On Wed, Dec 12, 2012 at 9:30 AM, José Francisco Álvarez Aguilar
wrote:
> Yes, www1.example.com, www2.example.com and wwwsecure.example.com all
> resolve to the same IP.
> So, due to your explanation, I can't have different behaviour for this 3
> virtualhosts without using different certificates or
Yes, www1.example.com, www2.example.com and wwwsecure.example.com all
resolve to the same IP.
So, due to your explanation, I can't have different behaviour for this 3
virtualhosts without using different certificates or without using SNI.
But there's one thing I don't understand: if we use "virtual
On Thu, Dec 6, 2012 at 7:59 PM, Pepe wrote:
> I have an apache server with 3 virtual host (all DNS work already done):
> http://www1.example.com --> listens on port 80
> http://www2.example.com --> listens on port 80 with required user
> authentication
> https://wwwsecure.example.com --> listens o
I have an apache server with 3 virtual host (all DNS work already done):
http://www1.example.com --> listens on port 80
http://www2.example.com --> listens on port 80 with required user authentication
https://wwwsecure.example.com --> listens on port 443
Everyone with different DocumentRoot.
Ever
19 matches
Mail list logo
