I believe the mapping is done as is. So ordering will differentiate resulting value paths.
You could do a regex mapping using the regex_remap plugin to funnel various paths to a desired origin. Personally I've never had an issue where I had multiple params most likely as I keep them in strict order and in my log reports I aggregate multiple paths if need. - J On Jul 25, 2011, at 3:10 PM, Chilappagari, Sairam wrote: > Thanks for the reply Jason. > > My question is when you enable the Dynamic Content Caching feature, does the > order of query parameters matter? > > > From: Jason Giedymin <[email protected]> > Reply-To: "[email protected]" <[email protected]> > Date: Mon, 25 Jul 2011 12:00:32 -0700 > To: "[email protected]" <[email protected]> > Subject: Re: Caching the Query Parameters. > > By default, ATS doesn't cache dynamic content but you can turn that on via: > > Caching Dynamic Content > > A URL is considered dynamic if it ends in .asp or contains a question mark > (?), a semicolon (;), or cgi. By default, Traffic Server does not cache > dynamic content. You can configure Traffic Server to cache dynamic content, > although it's recommended for specialized proxy situations only. > > proxy.config.http.cache_urls_that_look_dynamic > Set this variable to 1 to cache dynamic content. > > > (these docs might be old!) > http://trafficserver.apache.org/docs/v2/admin/http.htm > > > On Jul 25, 2011, at 2:54 PM, Chilappagari, Sairam wrote: > >> Hi, >> >> I know ATS has ability to cache the URLs with query parameters. But my >> question is, does query parameters order matter when retrieving the >> content from the cache? >> >> >> For ex: >> >> Does ATS use the same cached content for the following URIs? >> >> http://api.com/foo?val1=1&val2=2 >> http://api.com/foo?val2=2&val1=1 >> >> Thank you. >> >> >> >> >
