Hi Muhammad, 

One way to check the value of the cache key would be to add 
etc/trafficserver/plugin.config

xdebug.so

and them adding -H 'X-Debug: X-Cache-Key’ to the curl command-line parameters 
and you should see the following header in the response:

< X-Cache-Key: 
/www.example.com/80/popular/Mozilla/5.0/H1:v1/H2:v2/C1=v1;C2=v2/path/to/data?a=1&b=2&c=3

A complete example can be found in the cachekey documentation:

  
https://github.com/apache/trafficserver/blob/master/doc/admin-guide/plugins/cachekey.en.rst



Hi Dev, 

We discussed earlier that we plan to deprecate cacheurl soon, I was wondering 
if we can have 

   https://github.com/apache/trafficserver/pull/552 

reviewed and hopefully merged in the next release so Muhammad could use 
cachekey plugin instead of cacheurl. 

We have another user of the cachekey newest features who is waiting for this 
pull request to be merged (they are already running it in production with the 
change provided as a patch on top of the latest ATS release)


Cheers,
—Gancho


> On Apr 15, 2016, at 11:12 AM, Muhammad Faisal <[email protected]> wrote:
> 
> Hi,
> How we can verify if the configuration we have done in cacheurl.config is 
> actually working. I read the relevant docs but didnt find how the logging can 
> be done for this plugin.
>  
> --
> Regards,
> Faisal.

Reply via email to