[1/2] git commit: Thundering herd section-- background fill description error

[ml...@apache.org]

Updated Branches:
  refs/heads/master 425ceaf96 -> 17f782e7b


Thundering herd section-- background fill description error


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

Branch: refs/heads/master
Commit: 23839ca386dd0508b911a7b26824ac23b02b9987
Parents: 425ceaf
Author: Miles Libbey <ml...@apache.org>
Authored: Wed Oct 9 14:21:22 2013 -0700
Committer: Miles Libbey <ml...@apache.org>
Committed: Wed Oct 9 14:21:22 2013 -0700

----------------------------------------------------------------------
 doc/admin/http-proxy-caching.en.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/trafficserver/blob/23839ca3/doc/admin/http-proxy-caching.en.rst
----------------------------------------------------------------------
diff --git a/doc/admin/http-proxy-caching.en.rst b/doc/admin/http-proxy-caching.en.rst
index 1be97d9..42ef6c4 100644
--- a/doc/admin/http-proxy-caching.en.rst
+++ b/doc/admin/http-proxy-caching.en.rst
@@ -794,7 +794,7 @@ The configurations necessary to enable this in ATS are:
 All four configurations are required, for the following reasons:
 
 -  enable_read_while_writer turns the feature on. It's off (0) by default
--  The background fill feature should be allowed to kick in for every possible request. This is necessary, in case the writer ("first client session") goes away, someone needs to take over the session. The original client's request can go away after background_fill_active_timeout seconds, and the object will continue fetching in the background. The object then can start being served to another request after background_fill_completed_threshold % of the object has been fetched from origin.
+-  The background fill feature should be allowed to kick in for every possible request. This is necessary, in case the writer ("first client session") goes away, someone needs to take over the session. Hence, you should set the background fill timeouts and threshold to zero; this assures they never times out and always is allowed to kick in. 
 -  The proxy.config.cache.max_doc_size should be unlimited (set to 0), since the object size may be unknown, and going over this limit would cause a disconnect on the objects being served.
 
 Once all this enabled, you have something that is very close, but not quite the same, as Squid's Collapsed Forwarding.

[2/2] git commit: Fix auto-numbering formatting

[ml...@apache.org]

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 <ml...@apache.org>
Authored: Wed Oct 9 14:22:47 2013 -0700
Committer: Miles Libbey <ml...@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: