Custom Query (2297 matches)

Proxification to server accepting TLSv1 fails when TLSv1.2 is activated

We discover this problem when proxifying to www.groupama.fr which is a website that support only TLSv1 but don't support TLSv1.1 or TLSv1.2 (see ​https://www.ssllabs.com/ssltest/analyze.html?d=www.groupama.fr)

We had to change our nginx configuration in order to establish TLS connection to this server on TLSv1:

location / {

• proxy_ssl_protocols TLSv1 TLSv1.1 TLSv1.2; (fails)

+ proxy_ssl_protocols TLSv1 TLSv1.1; (work) ...

The Error message when TLSv1.2 is enabled : peer closed connection in SSL handshake while SSL handshaking to upstream

We don't understand why nginx don't try to establish a connection to TLSv1 when TLSv1 TLSv1.1 and TLSv1.2 are activated.

Hi,

Can we get a ballpark ETA on when these features will be out of the preview as we are trying to implement the same in our application? We have tried patch versions of this but we were not able to achieve the same because of the lack of official support and documentation on the same. Reporting the same here as we have not found an issues tracker in the GitHub repository.

Reference: ​https://www.nginx.com/blog/binary-packages-for-preview-nginx-quic-http3-implementation/

The context:

thread_pool $server_name threads=12;

http {
    server {
        aio threads=$server_name;
    }
}

This setup produces no errors at config test nginx -t but HTTP produces Error 500 and at error.log because thread_pool is not found.

thread pool "example.com" not found, server: example.com, request: "GET / HTTP/1.1"

It should either be allowed, or produce an an error at config test like nginx.conf: $server_name is not allowed here.