Mailing-List: contact users-help@trafficserver.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@trafficserver.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Subject: Fwd: 200 responses transformed into 304 Not Modified
References: <2E861ADC-747F-4CCC-8624-4BA1BFDDDD57@webthing.com>
From: Nick Kew <niq@apache.org>
Content-Type: text/plain; charset=utf-8
Message-Id: <194E9A22-B435-4BE4-8A22-049C2571294E@apache.org>
Date: Mon, 9 Apr 2012 10:45:36 +0100
To: users@trafficserver.apache.org
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v1084)

Bah.  Bounced when sent with other "From" address :(=20

Begin forwarded message:

> On 9 Apr 2012, at 10:00, Igor Gali=C4=87 wrote:
>=20
>> I remember you reported this issue on IRC, and that you were using
>> Traffic Server 2.0.1 - please don't do that ;)
>> Anyway, did the upgrade to 3.0.x or 3.1.x help you with this?
>=20
> I've seen a possibly-related issue with 3.x: trafficserver returns 304
> to an unconditional request.  Haven't replied to the OP because it's
> not quite the same issue, and I don't have a useful insight on that.
>=20
> Provisional Diagnosis:
> * Request comes to TS.
> * TS has cached copy, but wants to revalidate with origin server.
> * TS sends conditional request.
> * Origin server correctly replies with 304.
> * TS erroneously propagates 304 to client!
>=20
> --=20
> Nick Kew