Mercurial > hg > nginx-quic
annotate conf/scgi_params @ 7419:c5d7a72abadc stable-1.14
SSL: logging level of "no suitable signature algorithm".
The "no suitable signature algorithm" errors are reported by OpenSSL 1.1.1
when using TLSv1.3 if there are no shared signature algorithms. In
particular, this can happen if the client limits available signature
algorithms to something we don't have a certificate for, or to an empty
list. For example, the following command:
openssl s_client -connect 127.0.0.1:8443 -sigalgs rsa_pkcs1_sha1
will always result in the "no suitable signature algorithm" error
as the "rsa_pkcs1_sha1" algorithm refers solely to signatures which
appear in certificates and not defined for use in TLS 1.3 handshake
messages.
The SSL_R_NO_COMMON_SIGNATURE_ALGORITHMS error is what BoringSSL returns
in the same situation.
author | Maxim Dounin <mdounin@mdounin.ru> |
---|---|
date | Tue, 25 Sep 2018 14:00:04 +0300 |
parents | 62869a9b2e7d |
children |
rev | line source |
---|---|
3637 | 1 |
2 scgi_param REQUEST_METHOD $request_method; | |
3 scgi_param REQUEST_URI $request_uri; | |
4 scgi_param QUERY_STRING $query_string; | |
5 scgi_param CONTENT_TYPE $content_type; | |
6 | |
7 scgi_param DOCUMENT_URI $document_uri; | |
8 scgi_param DOCUMENT_ROOT $document_root; | |
9 scgi_param SCGI 1; | |
10 scgi_param SERVER_PROTOCOL $server_protocol; | |
6168
62869a9b2e7d
Added the REQUEST_SCHEME parameter.
Maxim Dounin <mdounin@mdounin.ru>
parents:
4333
diff
changeset
|
11 scgi_param REQUEST_SCHEME $scheme; |
4333
352a7b025f2e
Added HTTPS param with Apache-like behaviour to fastcgi/scgi/uwsgi_params (fixes #38).
Valentin Bartenev <vbart@nginx.com>
parents:
3637
diff
changeset
|
12 scgi_param HTTPS $https if_not_empty; |
3637 | 13 |
14 scgi_param REMOTE_ADDR $remote_addr; | |
15 scgi_param REMOTE_PORT $remote_port; | |
16 scgi_param SERVER_PORT $server_port; | |
17 scgi_param SERVER_NAME $server_name; |