This is an automated email from the ASF dual-hosted git repository.
kichan pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/trafficserver.git
The following commit(s) were added to refs/heads/master by this push:
new f373e24 Slight clarification to documentation of TLS User Agent Hooks.
f373e24 is described below
commit f373e24471ac44d2639b315b9e493fe93cce8243
Author: Walter Karas <[email protected]>
AuthorDate: Fri Dec 28 19:20:13 2018 -0600
Slight clarification to documentation of TLS User Agent Hooks.
---
doc/developer-guide/plugins/hooks-and-transactions/ssl-hooks.en.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
a/doc/developer-guide/plugins/hooks-and-transactions/ssl-hooks.en.rst
b/doc/developer-guide/plugins/hooks-and-transactions/ssl-hooks.en.rst
index 902be51..a21e636 100644
--- a/doc/developer-guide/plugins/hooks-and-transactions/ssl-hooks.en.rst
+++ b/doc/developer-guide/plugins/hooks-and-transactions/ssl-hooks.en.rst
@@ -22,9 +22,9 @@
TLS User Agent Hooks
********************
-In addition to the HTTP oriented hooks, a plugin can add hooks to trigger code
-during the TLS handshake with the user agent. This TLS handshake occurs well
before
-the HTTP transaction is available, so a separate state machine is required to
track the
+In addition to the HTTP oriented hooks, a plugin can add hooks (by calling
:c:func:`TSHttpHookAdd`)
+to trigger code during the TLS handshake with the user agent. This TLS
handshake occurs well
+before the HTTP transaction is available, so a separate state machine is
required to track the
TLS hooks.
TLS Hooks
