Why does the nginx.org main site not supporting TLS v1.3?

[David Hu]

I just did a cURL request just now using the command in Windows Powershell using the MinGW version of cURL.
`./curl -vvvvv --http2-prior-knowledge --tlsv1.3 https://nginx.org`
And my curl specs are as follows
curl 7.74.0 (x86_64-pc-win32) libcurl/7.74.0 OpenSSL/1.1.1i (Schannel) zlib/1.2.11 brotli/1.0.9 zstd/1.4.8 WinIDN libssh2/1.9.0 nghttp2/1.42.0
Release-Date: 2020-12-09
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps mqtt pop3 pop3s rtsp scp sftp smb smbs smtp smtps telnet tftp
Features: AsynchDNS HSTS HTTP2 HTTPS-proxy IDN IPv6 Kerberos Largefile MultiSSL NTLM SPNEGO SSL SSPI TLS-SRP Unicode UnixSockets alt-svc brotli libz zstd
However the output is as following:
*   Trying 3.125.197.172:443...
* Connected to nginx.org (3.125.197.172) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*  CAfile: D:\curl-7.74.0_2-win64-mingw\bin\curl-ca-bundle.crt
*  CApath: none
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS alert, protocol version (582):
* error:1409442E:SSL routines:ssl3_read_bytes:tlsv1 alert protocol version
* Closing connection 0
curl: (35) error:1409442E:SSL routines:ssl3_read_bytes:tlsv1 alert protocol version

Why does this happen? Can anyone explain the reason? It seems like the nginx main site is not supporting TLSv1.3
Thank you very much!

-------------- next part --------------
A non-text attachment was scrubbed...
Name: publickey - D4v1d_4n0 at protonmail.ch - 0x340A848D.asc
Type: application/pgp-keys
Size: 736 bytes
Desc: not available
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20210122/4a7f7084/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 249 bytes
Desc: OpenPGP digital signature
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20210122/4a7f7084/attachment-0001.bin>