Hi Jordan,
You are right, very sorry for the noise. Must have confounded the error
with the many changes I made at the same time. Thanks for your time!
Kind regards,
Taco de Wolff
Op za 2 mrt 2024 om 15:52 schreef J Carter :
> Hello Taco,
>
> On Sat, 2 Mar 2024 09:54:46 -0300
> Taco de Wolff
Hello Taco,
On Sat, 2 Mar 2024 09:54:46 -0300
Taco de Wolff wrote:
> Thank you Jordan for the response.
>
No problem.
> Including the SNI information in cURL works, thank you. I wasn't aware this
> was so very different from TCP/HTTP2.
>
> The point I was trying to make about the ssl_certif
Thank you Jordan for the response.
Including the SNI information in cURL works, thank you. I wasn't aware this
was so very different from TCP/HTTP2.
The point I was trying to make about the ssl_certificate options to be
mandatory, is that HTTP/2 also requires SSL but recognizes that when
ssl_reje
Hello,
On Wed, 28 Feb 2024 21:45:37 -0300
Taco de Wolff wrote:
> Hi,
>
> I've noticed at least in 1.24.0 and 1.25.4 that adding an
> ssl_reject_handshake to the default server breaks SNI for other
> servers. Example:
>
> ```
> server {
> server_name _;
> listen 80 default_server;
>
Hi,
I've noticed at least in 1.24.0 and 1.25.4 that adding an
ssl_reject_handshake to the default server breaks SNI for other servers.
Example:
```
server {
server_name _;
listen 80 default_server;
listen 443 default_server ssl;
listen 443 default_server quic reuseport;
listen
