Implementing Cache-Control: no-cache for an HTTP client to trigger cache invalidation would be a handy enhancement.

Currently, to monitor that xcaches can reach an origin server, we've needed to deploy cronjobs to remove cache entries of test files. Being able to force a cache to forward the request to the origin would be helpful.

In addition, this might help with allowing cvmfs clients to retrieve updated content via xcache. Glancing at the cvmfs code, it seems to retry with no-cache if there's a mismatch.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1886", "url": "https://github.com/xrootd/xrootd/issues/1886", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1