Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: pass (herse.apache.org: domain of jslive@gmail.com designates
 209.85.146.182 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=AXaMwROYO+l3/yd3oXtjU0KRsk8r2lvwt935ITwbAqh/LIU0Tk6G9Dre0wVGP73mSpQ7rXk6lp9uGpsuteW7GyG/sv8lFWNWCKWPHGPNg94F+8nT4xSBj2+IkkiQ7BAdUvTVHrNRD8iBhyjpD0gm9Nyql8eyT3U+fpqpzf2ZykQ=
Message-ID: <e498c1660707230623l172f49d2pe429143d0ec68d6b@mail.gmail.com>
Date: Mon, 23 Jul 2007 09:23:17 -0400
From: "Joshua Slive" <joshua@slive.ca>
Sender: jslive@gmail.com
To: users@httpd.apache.org
In-Reply-To: <46A469FB.7000707@televes.es>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <46A0A74C.50200@televes.es>
	 <e498c1660707200615g54021161k7ae781a5e2ec8c09@mail.gmail.com>
	 <46A469FB.7000707@televes.es>
Subject: Re: [users@httpd] Want to avoid 304 error

On 7/23/07, Bello Martinez Sergio <serbel@televes.es> wrote:
> Thank you for your respose.
> I've checked that browsers don=B4t work as you say they're supposed to
> work. When Apache aswers with a 304 response, the only cache-related
> header it includes by default into the response is 'Cache-Control:
> must-revalidate'.
> Internet Explorer 6.0 does nothing with it, after receiving this
> response, cache remains the same (entity expiry dates remains the same)
> so each time browser needs those elements, it sends a new http request
> an it receives a new 304 response. In the case of Firefox 2.0, the cache
> is updated, but not in the way I'd like: instead of this, entity's
> expiry date are updated to '1970-01-01 01:00:00', so the result is the
> same, each time the browser needs one of these elements, we have a
> request-304 response (with a worse performance)

must-revalidate is certainly not something that apache returns by
default or with the default handler. In fact, no cache-control
parameters are set by default. So I think you need to examine your
application.

Although must-revalidate should technically not effect the caching
decision of the client in most cases, it is a widely abused parameter
and it wouldn't surprise me at all if clients treat this as marking
the response as instantly stale. I would therefore guess that your
problem would be eliminated if you dropped this parameter.

Joshua.

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org