randall commented on a change in pull request #6691:
URL: https://github.com/apache/trafficserver/pull/6691#discussion_r425292469
##########
File path: plugins/experimental/slice/client.cc
##########
@@ -119,15 +126,30 @@ handle_client_req(TSCont contp, TSEvent event, Data
*const data)
void
handle_client_resp(TSCont contp, TSEvent event, Data *const data)
{
- DEBUG_LOG("%p handle_client_resp %s", data, TSHttpEventNameLookup(event));
+ // DEBUG_LOG("%p handle_client_resp %s", data, TSHttpEventNameLookup(event));
Review comment:
can this be removed if it's not needed?
##########
File path: doc/admin-guide/plugins/slice.en.rst
##########
@@ -194,30 +216,59 @@ adding in range request headers ("Range: bytes="). A
special
header X-Slicer-Info header is added and the pristine URL is
restored.
-For each of these blocks separate sequential TSHttpConnect(s) are made
-back into the front end of ATS and all of the remap plugins are rerun.
-Slice skips the remap due to presence of the X-Slicer-Info header and
-allows cache_range_requests.so to serve the slice block back to Slice
-either via cache OR parent request.
-
-Slice assembles a header based on the first slice block response and
-sends it to the client. If necessary it then skips over bytes in
-the first block and starts sending byte content, examining each
-block header and sends its bytes to the client until the client
-request is satisfied.
-
-Any extra bytes at the end of the last block are consumed by
-the Slice plugin to allow cache_range_requests to finish
-the block fetch to ensure the block is cached.
+For each of these blocks separate sequential TSHttpConnect(s) are
+made back into the front end of ATS. By default of the remap plugins
+are rerun. Slice skips the remap due to presence of the X-Slicer-Info
+header and allows cache_range_requests.so to serve the slice block back
+to Slice either via cache OR parent request.
+
+Slice assembles a header based on the very first slice block response
+and sends it to the client. If necessary it then skips over bytes in the
+first block and starts sending byte content, examining each block header
+and sends its bytes to the client until the client request is satisfied.
+
+Any extra bytes at the end of the last block are consumed by the the
+Slice plugin to allow cache_range_requests to finish the block fetch to
+ensure the block is cached.
+
+Self Healing
+------------
+
+The slice plugin uses the very first slice as a reference slice which
+uses content-length and last-modifed and/or etags to ensure assembled
Review comment:
modified
##########
File path: doc/admin-guide/plugins/cache_range_requests.en.rst
##########
@@ -125,13 +125,13 @@ special header:
.. code::
- X-CRR-IMS: Tue, 19 Nov 2019 13:26:45 GMT
+ X-Crr-Ims: Tue, 19 Nov 2019 13:26:45 GMT
When this header is provided and a `cache hit fresh` is encoutered the
Review comment:
encountered
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
