Return-Path: X-Original-To: apmail-trafficserver-users-archive@www.apache.org Delivered-To: apmail-trafficserver-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2D8626F5C for ; Mon, 25 Jul 2011 18:55:15 +0000 (UTC) Received: (qmail 80751 invoked by uid 500); 25 Jul 2011 18:55:14 -0000 Delivered-To: apmail-trafficserver-users-archive@trafficserver.apache.org Received: (qmail 80609 invoked by uid 500); 25 Jul 2011 18:55:13 -0000 Mailing-List: contact users-help@trafficserver.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@trafficserver.apache.org Delivered-To: mailing list users@trafficserver.apache.org Received: (qmail 80601 invoked by uid 99); 25 Jul 2011 18:55:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Jul 2011 18:55:13 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of Sairam.Chilappagari@disney.com designates 204.128.192.17 as permitted sender) Received: from [204.128.192.17] (HELO msg1.disney.com) (204.128.192.17) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Jul 2011 18:55:04 +0000 Received: from int2.disney.pvt (int2.disney.pvt [153.7.110.7]) by msg1.disney.com (Switch-3.4.4/Switch-3.4.3) with ESMTP id p6PIsgas007132 for ; Mon, 25 Jul 2011 18:54:42 GMT Received: from sm-cala-xht01.swna.wdpr.disney.com (SM-CALA-XHT01.swna.wdpr.disney.com [153.7.248.16]) by int2.disney.pvt (Switch-3.4.4/Switch-3.4.3) with ESMTP id p6PIsf5t025605 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Mon, 25 Jul 2011 18:54:41 GMT Received: from sm-cala-vxmb06a.swna.wdpr.disney.com ([fe80::8920:73be:eaf5:e3af]) by sm-cala-xht01.swna.wdpr.disney.com ([2002:9907:f810::9907:f810]) with mapi; Mon, 25 Jul 2011 11:54:41 -0700 From: "Chilappagari, Sairam" To: "users@trafficserver.apache.org" Date: Mon, 25 Jul 2011 11:54:37 -0700 Subject: Caching the Query Parameters. Thread-Topic: Caching the Query Parameters. Thread-Index: AcxK/E9dkvHQWm/ESZugby2elNWTvA== Message-ID: In-Reply-To: <20110722103132.GA32155@oc1046828364.ibm.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.12.0.110505 acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Source-IP: SM-CALA-XHT01.swna.wdpr.disney.com [153.7.248.16] X-Virus-Checked: Checked by ClamAV on apache.org 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=3D1&val2=3D2 http://api.com/foo?val2=3D2&val1=3D1 Thank you.