On Jun 26, 2013, at 4:28 AM, Réjean Bouchard <[email protected]> wrote:
> You're right! But if you use the web UI, do a regex search and click on one > of the file name, it's impossible for the UI to do the same PURGE, DELETE or > URL_Lookup . That why I need those "real file name" to be saved in the > cache. Does your workflow really depend on being able to search the cache with a regex? The recommended way to remove objects from the cache is to use the PURGE method. My opinion is that the web UI should be removed and that cache management tools should be separated from the Traffic Server core. That's low priority and a bit tricky due to some implementation details, but eventually I hope to remove it :) J > > Thank You! > Réjean Bouchard > Nexweb > > -----Message d'origine----- > De : Leif Hedstrom [mailto:[email protected]] > Envoyé : 21 juin 2013 11:03 > À : [email protected] > Cc : Réjean Bouchard > Objet : Re: Want to get the original URL > > On 6/21/13 6:44 AM, Réjean Bouchard wrote: >> In my case, the cache_vary_headers is off. Here is all "vary" lines >> in my records.config : >> >> CONFIG proxy.config.http.cache.enable_default_vary_headers INT 0 >> CONFIG proxy.config.http.cache.vary_default_text STRING NULL CONFIG >> proxy.config.http.cache.vary_default_images STRING NULL CONFIG >> proxy.config.http.cache.vary_default_other STRING NULL >> >> I attach the entire file with this mail. I currently use version 3.2.4. >> What version did you use? The question is: how can we purge a file if >> the original URL is not available? > > If you send a "PURGE" request it also goes through the remap rules, and will > purge the appropriate entry in cache. > > curl -X PURGE http://ts1.example.com/test.txt > > I don't know if the cache inspector does the same (I'd imagine it would, but > not sure, I never use it). > > -- Leif
