[
https://issues.apache.org/jira/browse/TC-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Durfey updated TC-213:
---------------------------
Labels: invalidation portal purge self_service (was: feature portal
purge)
Description:
We found that in some cases corrupted content can get trapped in the edge cache
with proper ETAGs, so invalidation requests are not able to cause the content
to reload. We also found there is a business case to remove content from cache.
We need a mechanism that works similar to invalidation but actually purges
content from the caches.
This would be done without wildcards as a restriction.
was:We found that in some cases corrupted content can get trapped in the edge
cache with proper ETAGs, so invalidation requests are not able to cause the
content to reload. We also found there is a business case to remove content
from cache. We need a mechanism that works similar to invalidation but actually
purges content from the caches.
> Purge Functionality - Add to Portal
> -----------------------------------
>
> Key: TC-213
> URL: https://issues.apache.org/jira/browse/TC-213
> Project: Traffic Control
> Issue Type: New Feature
> Components: Traffic Ops, Traffic Portal
> Reporter: Ashish Timilsina
> Labels: invalidation, portal, purge, self_service
>
> We found that in some cases corrupted content can get trapped in the edge
> cache with proper ETAGs, so invalidation requests are not able to cause the
> content to reload. We also found there is a business case to remove content
> from cache. We need a mechanism that works similar to invalidation but
> actually purges content from the caches.
> This would be done without wildcards as a restriction.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
