Re: Query strings are not forwarded

2016-11-02 Thread Randeep
Hi, Its true. I started using this plugin for removing the query strings from the requests. But when I checked the documentation, I found that the same plugin can be used to whitelist user-agents also. https://docs.trafficserver.apache.org/en/6.2.x/admin-guide/plugins/cachekey.en.html?highlight=c

Re: Query strings are not forwarded

2016-10-28 Thread Miles Libbey
On Fri, Oct 28, 2016 at 6:04 AM, Sudheer Vinukonda wrote: > Not sure to follow - what exactly are you trying to do? Afaik, cachekey > plugin only manipulates the otherwise default cache key (which is the full > request URL) used against the configured cache object(s) and modifies it as > specif

Re: Query strings are not forwarded

2016-10-28 Thread Sudheer Vinukonda
Not sure to follow - what exactly are you trying to do? Afaik, cachekey plugin only manipulates the otherwise default cache key (which is the full request URL) used against the configured cache object(s) and modifies it as specified. I don't believe it can "block" any requests or user-agents. >

Re: Query strings are not forwarded

2016-10-28 Thread Randeep
Hi Sudheer, Sorry. I had added it. While pasting here somehow it was not selected. I was was checking the whitelisting of a user agent. Query string was working. map http://jitp1.domain.com/ http://bglrcache1.domain.com/ @plugin=cachekey.so @pparam=--ua-whitelist=player:/opt/ats/etc/trafficserver

Re: Query strings are not forwarded

2016-10-28 Thread Sudheer Vinukonda
Hmm...where's the pparam to strip query string? Please make sure to read through the documentation on cachekey. Specifically, the query param section you are looking for and the examples. Here's a relevant extract - URI query parameters Ignore the query string (all query parameters) The follo

Re: Query strings are not forwarded

2016-10-28 Thread Randeep
Hi Miles Libbey, Thanks for pointing it out. I changed it as below. map http://jitp1.domain.com/ http://bglrcache1.domain.com/ @plugin=cachekey.so @pparam=--ua-whitelist=player:/opt/ats/etc/trafficserver/randeep.config @pparam=--ua-capture=(stagefright\/[^\s]*).* Still now luck. [root@cachetest

Re: Query strings are not forwarded

2016-10-28 Thread Miles Libbey
On Thu, Oct 27, 2016 at 11:41 PM, Randeep wrote: > Hi, > > I used the cachekey plugin as below. But its not working. Am I doing it > wrong? > > My remap.config > map http://jitp1.domain.com/ http://bglrcache1.domain.com/ > @pparam=--ua-whitelist=lukupplayer:/opt/ats/etc/trafficserver/randeep.conf

Re: Query strings are not forwarded

2016-10-27 Thread Randeep
Hi, I used the cachekey plugin as below. But its not working. Am I doing it wrong? My remap.config map http://jitp1.domain.com/ http://bglrcache1.domain.com/ @pparam=--ua-whitelist=lukupplayer:/opt/ats/etc/trafficserver/randeep.config @pparam=--ua-capture=(stagefright\/[^\s]*).* cat /opt/ats/etc

Re: Query strings are not forwarded

2016-10-27 Thread Sudheer Vinukonda
You may try using cachekey plugin to ignore the query params only from the cache key and not from remap, instead of using regex_remap with no-query-string param, which will basically remove the query string from remap. There is an excellent documentation and some examples on how to do this at ht

Query strings are not forwarded

2016-10-27 Thread Randeep
Hi all, We are using ats to cache our live MPEG dash and HLS streams. We use version 6.2.0 with parent-child architecture. In the requests there are some query strings like timestamps for playing catchup,start-over,timeshift etc. Before the requests where not caching so we added @pparam=no-query