If you can, I would set up a Traffic Server configured like your production
machines, turn on the 'http' and 'cache' debug tags and run a connection to the
problematic origin through it and see what shows up. That might indicate why
ATS doesn't want to cache the asset. I double checked the spelling on the
configuration value (because if you have a typo you're not told) but it seems
correct.
On Monday, February 29, 2016 10:40 AM, jhasle <[email protected]> wrote:
Any thoughts on what else could be the problem?
--
View this message in context:
http://apache-traffic-server.24303.n7.nabble.com/Problems-with-caching-retrieving-from-cache-from-a-particular-origin-tp2193p2197.html
Sent from the Apache Traffic Server mailing list archive at Nabble.com.
