You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

29 lines
1.2 KiB

  1. From 9fe4cb64cd9514a72bcd4b2fd8781620da9e1f76 Mon Sep 17 00:00:00 2001
  2. From: Willy Tarreau <w@1wt.eu>
  3. Date: Wed, 2 Jul 2014 19:01:22 +0200
  4. Subject: [PATCH 12/12] DOC: provide an example of how to use ssl_c_sha1
  5. As suggested by Aydan Yumerefendi, a little bit of examples never hurts.
  6. (cherry picked from commit 2d0caa38e040b081903e50faa56bae52599b3949)
  7. ---
  8. doc/configuration.txt | 4 ++++
  9. 1 file changed, 4 insertions(+)
  10. diff --git a/doc/configuration.txt b/doc/configuration.txt
  11. index e53bb21..fcc6454 100644
  12. --- a/doc/configuration.txt
  13. +++ b/doc/configuration.txt
  14. @@ -10722,6 +10722,10 @@ ssl_c_sha1 : binary
  15. Returns the SHA-1 fingerprint of the certificate presented by the client when
  16. the incoming connection was made over an SSL/TLS transport layer. This can be
  17. used to stick a client to a server, or to pass this information to a server.
  18. + Note that the output is binary, so if you want to pass that signature to the
  19. + server, you need to encode it in hex or base64, such as in the example below:
  20. +
  21. + http-request set-header X-SSL-Client-SHA1 %[ssl_c_sha1,hex]
  22. ssl_c_sig_alg : string
  23. Returns the name of the algorithm used to sign the certificate presented by
  24. --
  25. 1.8.5.5