mirrors/haproxy
1
0
Fork 0
mirror of https://git.haproxy.org/git/haproxy.git/ synced 2025-09-22 06:11:32 +02:00
Code Issues Projects Releases Wiki Activity

DOC: ssl: surround keywords with quotes

Browse Source 
In order to make external tools easily detect keywords in the documentation,
let's surround them by quotes as it is done for other keywords.
This commit is contained in:
Cyril Bont 2012-10-09 22:45:34 +02:00 committed by Willy Tarreau
parent 0d44fc6472
commit 9c1eb1e8be
1 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
doc/configuration.txt
View File

@ -8313,30 +8313,30 @@ ssl_sni <string>
layer which deciphered it and found a Server Name Indication TLS extension
sent by the client, matching the specified string. In HTTPS, the SNI field
(when present) is equal to the requested host name. This match is different
from req_ssl_sni above in that it applies to the connection being deciphered
by haproxy and not to SSL contents being blindly forwarded. See also
ssl_sni_end and ssl_sni_req below. This requires that the SSL library is
build with support for TLS extensions enabled (check haproxy -vv).
from "req_ssl_sni" above in that it applies to the connection being
deciphered by haproxy and not to SSL contents being blindly forwarded.
See also "ssl_sni_end" and "ssl_sni_req" below. This requires that the SSL
library is build with support for TLS extensions enabled (check haproxy -vv).
ssl_sni_end <string>
Returns true when the incoming connection was made over an SSL/TLS transport
layer which deciphered it and found a Server Name Indication TLS extension
sent by the client, ending like the specified string. In HTTPS, the SNI field
(when present) is equal to the requested host name. This match is different
from req_ssl_sni above in that it applies to the connection being deciphered
by haproxy and not to SSL contents being blindly forwarded. This requires
that the SSL library is build with support for TLS extensions enabled (check
haproxy -vv).
from "req_ssl_sni" above in that it applies to the connection being
deciphered by haproxy and not to SSL contents being blindly forwarded. This
requires that the SSL library is build with support for TLS extensions
enabled (check haproxy -vv).
ssl_sni_req <regex>
Returns true when the incoming connection was made over an SSL/TLS transport
layer which deciphered it and found a Server Name Indication TLS extension
sent by the client, matching the specified regex. In HTTPS, the SNI field
(when present) is equal to the requested host name. This match is different
from req_ssl_sni above in that it applies to the connection being deciphered
by haproxy and not to SSL contents being blindly forwarded. This requires
that the SSL library is build with support for TLS extensions enabled (check
haproxy -vv).
from "req_ssl_sni" above in that it applies to the connection being
deciphered by haproxy and not to SSL contents being blindly forwarded. This
requires that the SSL library is build with support for TLS extensions
enabled (check haproxy -vv).
ssl_verify_caerr <errorID>
Returns true when the incoming connection was made over an SSL/TLS transport