You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by GitBox <gi...@apache.org> on 2021/11/12 00:37:38 UTC

[GitHub] [trafficcontrol] ocket8888 commented on a change in pull request #6342: Add/update documentation for content invalidation jobs in TO API v4

ocket8888 commented on a change in pull request #6342:
URL: https://github.com/apache/trafficcontrol/pull/6342#discussion_r747904146



##########
File path: docs/source/admin/quick_howto/content_invalidation.rst
##########
@@ -22,8 +22,6 @@ Invalidating content on the CDN is sometimes necessary when the :term:`Origin` w
 
 .. impl-detail:: Given the size of a typical Traffic Control CDN and the amount of content that can be cached in it, removing the content from all the caches may take a long time. To speed up content invalidation, Traffic Control does not try to remove the content from the caches, but it makes the content inaccessible using the `regex_revalidate plugin for Apache Traffic Server <https://docs.trafficserver.apache.org/en/8.0.x/admin-guide/plugins/regex_revalidate.en.html>`_. This forces a "re-validation" of the content.
 
-.. Warning:: This method forces :term:`cache servers` to "re-validate" content, so in order to work properly the :term:`Origin` needs to support revalidation according to section 4.3.2 of :rfc:`7234`.
-

Review comment:
       I moved it to the section on "Invalidation Type" in the overview, which is linked to now from this section




-- 
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.

To unsubscribe, e-mail: issues-unsubscribe@trafficcontrol.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org