Re: Is it possible to have in Apache 2.4 VirtualHosts, each with its own SSLProtocol ?

To: users@xxxxxxxxxxxxxxxx
Subject: Re: Is it possible to have in Apache 2.4 VirtualHosts, each with its own SSLProtocol ?
From: Marian-Nicolae Ion <m.ion@xxxxxxxxxxx>
Date: Mon, 21 Oct 2019 22:53:02 +0200 (CEST)
Cc: ylavic.dev@xxxxxxxxx
In-reply-to: <CAKQ1sVOOxdPC-SabGH8f6=x55PhKkNG=O0i8edmjZV8HCq=pAw@mail.gmail.com>
Reply-to: users@xxxxxxxxxxxxxxxx
Thread-index: eIqOoXydJiHxQehaMF81XQI/r9mLZg==
Thread-topic: Is it possible to have in Apache 2.4 VirtualHosts, each with its own SSLProtocol ?

Hi!

I recompiled and installed the new version... but I came back quickly to the "standard" one:

- using "curl" I have noticed that effectively I could have TLS 1.3 only on the desired virtual host and TLS 1.2+ on the others,

- however, using a normal browser ("Firefox, Chromium,...) I always encountered 403, on all virtual hosts, for all resources!

I also use http2, I wonder if this does not also interfere with TLS...

Regards,

Marian

Follow-Ups:
- Re: Is it possible to have in Apache 2.4 VirtualHosts, each with its own SSLProtocol ?
  - From: Yann Ylavic
- Re: Is it possible to have in Apache 2.4 VirtualHosts, each with its own SSLProtocol ?
  - From: Stefan Eissing

References:
- Is it possible to have in Apache 2.4 VirtualHosts, each with its own SSLProtocol ?
  - From: Marian Ion
- Re: Is it possible to have in Apache 2.4 VirtualHosts, each with its own SSLProtocol ?
  - From: Yann Ylavic
- Re: Is it possible to have in Apache 2.4 VirtualHosts, each with its own SSLProtocol ?
  - From: Aleksandar Ivanisevic
- Re: Is it possible to have in Apache 2.4 VirtualHosts, each with its own SSLProtocol ?
  - From: Yann Ylavic
- Re: Is it possible to have in Apache 2.4 VirtualHosts, each with its own SSLProtocol ?
  - From: Yann Ylavic