Mailing-List: contact users-help@trafficserver.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@trafficserver.apache.org
Received-SPF: pass (athena.apache.org: domain of mokplan@gmail.com designates
 209.85.216.42 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=SeS9/Tq93gThynsNkooeb7s6EPTPcT2cJLgDr1Bu3KLAwabvi0c0mmO+qE6Si6QOZL
         19+IhhdDOEWm3FvMORCoEp22dQiz4Qc+MddIxisN9+OEiBZzgBU1ouDRx3tcaNlGq9av
         nO5iOJNJN3aFfSS81i4h5vKo18Jwvh44sETzc=
MIME-Version: 1.0
Date: Mon, 16 May 2011 22:24:39 +0300
Message-ID: <BANLkTi=uPYZ8GLAiCw+c0tnqrrr5P5Z2Eg@mail.gmail.com>
Subject: ATS and PURGE
From: Moshe Kaplan <mokplan@gmail.com>
To: users@trafficserver.apache.org
Content-Type: multipart/alternative; boundary=00163641725b58528c04a3699b7b

--00163641725b58528c04a3699b7b
Content-Type: text/plain; charset=ISO-8859-1

Hi,

Another question regarding PURGE,
We want to support the following user case:

   1. Purge single file from the cache (each time another file).
   2. Do that immediately based on external event using external software.

When we used PURGE (using cURL) in order to invalidate an object we found
out the following behavior:

   1. GIF and JPG files were correctly invalidated (With 200 OK)
   2. HTML files were not invalidated (404)

When we investigated it, we founded out that probably it's due to the fact
ATS saves several variations of the HTML file based on Accept-Encoding and
User-Agent.
We confirmed that by doing GET and PURGE using with cURL that results with
200, while browsing to the same page and then PURGE using cURL resulted with
404.

Is there any option to PURGE the all versions of a given cached URL
regardless of its variations?

Thanks in advance,
Moshe

--00163641725b58528c04a3699b7b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<div><br></div><div>Another question regarding PURGE,</=
div><div>We want to support the following user case:</div><div><ol><li>Purg=
e single file from the cache (each time another file).</li><li>Do that imme=
diately=A0based on external event using external software.</li>
</ol></div><div>When we used PURGE (using cURL) in order to invalidate an o=
bject we found out the following behavior:</div><div><ol><li>GIF and JPG fi=
les were correctly invalidated (With 200 OK)</li><li>HTML files were not in=
validated (404)</li>
</ol><div>When we investigated it, we founded out that probably it&#39;s du=
e to the fact ATS saves several variations of the HTML file based on=A0Acce=
pt-Encoding and User-Agent.</div></div><div>We confirmed that by doing GET =
and PURGE using with cURL that results with 200, while browsing to the same=
 page and then PURGE using cURL resulted with 404.</div>
<div><br></div><div>Is there any option to PURGE the all versions of a give=
n cached URL regardless of its variations?</div><div><br></div><div>Thanks =
in advance,</div><div>Moshe</div></div>

--00163641725b58528c04a3699b7b--