Not quite. File modification times, when included, are sent in a Last-Modified header. That is treated differently and introduces its own set of challenges, I don't recommend it. What's missing is the header to say how long to cache things. When that's missing, squid makes a calculation based on how old the Date header is, but the better thing to do is to include the Cache-control header so squid doesn't need to guess.

In any case, the best solution would be to put those data files into regular CVMFS instead of caching them in squid via stashcache. Then they would be able to take advantage of the cvmfs client cache in addition to squid. Data files such as those which behave a lot like code as far as the infrastructure is concerned should be distributed with the code. See the cvmfs documentation on repository content.

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

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1073?email_source=notifications\u0026email_token=AA7NRDTRQVFKBHPM6DVA5K3QP4VGFA5CNFSM4JDSBUTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEB6NV4I#issuecomment-545053425", "url": "https://github.com/xrootd/xrootd/issues/1073?email_source=notifications\u0026email_token=AA7NRDTRQVFKBHPM6DVA5K3QP4VGFA5CNFSM4JDSBUTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEB6NV4I#issuecomment-545053425", "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