trafficserver-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mlib...@apache.org
Subject [2/2] git commit: Fix auto-numbering formatting
Date Wed, 09 Oct 2013 21:22:55 GMT
Fix auto-numbering formatting


Project: http://git-wip-us.apache.org/repos/asf/trafficserver/repo
Commit: http://git-wip-us.apache.org/repos/asf/trafficserver/commit/17f782e7
Tree: http://git-wip-us.apache.org/repos/asf/trafficserver/tree/17f782e7
Diff: http://git-wip-us.apache.org/repos/asf/trafficserver/diff/17f782e7

Branch: refs/heads/master
Commit: 17f782e7b7b7a49be47341ba912b3695b6924f69
Parents: 23839ca
Author: Miles Libbey <mlibbey@apache.org>
Authored: Wed Oct 9 14:22:47 2013 -0700
Committer: Miles Libbey <mlibbey@apache.org>
Committed: Wed Oct 9 14:22:47 2013 -0700

----------------------------------------------------------------------
 doc/admin/security-options.en.rst | 23 +++++------------------
 1 file changed, 5 insertions(+), 18 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/trafficserver/blob/17f782e7/doc/admin/security-options.en.rst
----------------------------------------------------------------------
diff --git a/doc/admin/security-options.en.rst b/doc/admin/security-options.en.rst
index 6227b70..6fa3bef 100644
--- a/doc/admin/security-options.en.rst
+++ b/doc/admin/security-options.en.rst
@@ -101,24 +101,11 @@ Server connections only**.
 
 The figure above depicts the following:
 
-# The client sends an HTTPS request for content. Traffic
-Server receives the request and performs the SSL 'handshake' to
-authenticate the client (depending on the authentication options
-configured) and determine the encryption method that will be used. If
-the client is allowed access, then Traffic Server checks its cache for
-the requested content.
-
-# If the request is a cache hit and the content is fresh, then
-Traffic Server encrypts the content and sends it to the client. The
-client decrypts the content (using the method determined during the
-handshake) and displays it.
-
-# If the request is a cache miss or cached content is stale,
-then Traffic Server communicates with the origin server via HTTP and
-obtains a plain text version of the content. Traffic Server saves the
-plain text version of the content in its cache, encrypts the content,
-and sends it to the client. The client decrypts and displays the
-content.
+#. The client sends an HTTPS request for content. Traffic Server receives the request and
performs the SSL 'handshake' to authenticate the client (depending on the authentication options
configured) and determine the encryption method that will be used. If the client is allowed
access, then Traffic Server checks its cache for the requested content.  
+
+#. If the request is a cache hit and the content is fresh, then Traffic Server encrypts the
content and sends it to the client. The client decrypts the content (using the method determined
during the handshake) and displays it.
+
+#. If the request is a cache miss or cached content is stale, then Traffic Server communicates
with the origin server via HTTP and obtains a plain text version of the content. Traffic Server
saves the plain text version of the content in its cache, encrypts the content, and sends
it to the client. The client decrypts and displays the content.
 
 To configure Traffic Server to use the SSL termination option for
 client/Traffic Server connections, you must do the following:


Mime
View raw message