I'm suggesting finding the failed requests from the logs, and purging those URLs so future requests work.
David On Thu, Dec 21, 2017 at 9:20 AM, Veiko Kukk <[email protected]> wrote: > Thank you for your answer. > > Sure I can find those failures from logs, but it's no good because, well, > they have then already failed for client. > I've read about cache inspector, but it does not seem to be able to filter > based on HTTP status code. > > Veiko > > > 2017-12-21 14:21 GMT+02:00 David Carlin <[email protected]>: > >> Can you grab the list of objects from the log files? Thats only thing I >> can think of. >> >> The cache inspector exists, but I've never had any luck with it. I think >> our cache is too large for it: >> >> https://docs.trafficserver.apache.org/en/latest/admin-guide/ >> storage/index.en.html#inspecting-the-cache >> >> David >> >> On Thu, Dec 21, 2017 at 5:40 AM, Veiko Kukk <[email protected]> wrote: >> >>> Hi, >>> >>> We had configuration mistake that enforced Cache-Contro: >>> max-age=157784630 also to negative responses that then got cached. >>> >>> Now, after fixing config, we need to purge all those objects from cache. >>> It's even good enough if I could get list of objects with certain HTTP >>> status code, then I could write script that purges those objects one by one. >>> >>> How to do mass purge based on HTTP status code or just get list of >>> objects based on HTTP status code? >>> >>> >>> Veiko >>> >>> >> >
