Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
Received-SPF: pass (athena.apache.org: domain of uhlar@fantomas.sk designates
 195.168.3.66 as permitted sender)
Date: Wed, 29 Aug 2007 21:32:26 +0200
From: Matus UHLAR - fantomas <uhlar@fantomas.sk>
To: users@httpd.apache.org
Message-ID: <20070829193226.GB30207@fantomas.sk>
Mail-Followup-To: users@httpd.apache.org
References: <46A0A74C.50200@televes.es>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-2
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <46A0A74C.50200@televes.es>
User-Agent: Mutt/1.5.13 (2006-08-11)
Subject: Re: [users@httpd] Want to avoid 304 error

On 20.07.07 14:15, Bello Martinez Sergio wrote:
> I've configured Apache so that some elements (i.e. .js, .gif, .jpeg, 
> etc) are stored in browser's cache during a time. When I access to a 
> page contaning any of those elements, the browser doesn�t make a request 
> to the server, it get the content from cache instead. Until this moment, 
> all is ok.
> The problem arises when the time I chose for element's caching finishes. 
> After this moment, each time the browser need one of those cached 
> elements, It makes a http request to the server and the response 
> includes a 304 error (I know it�s not an error, only a 'not modified' 
> message). The problem is that when a page contains many of these 
> elements (.js, .gif, etc), performance get worse (pairs request-reponse 
> 304 take time),

the request-response are always there, unless you send Expires: header for
objects. And if uses forces refresh, they will be re-fetched anyway.
> and there isn't a way to tell the browser to use cache's 
> information again, unless you modify files at server side.
> So I want to know or if there is a way to configure Apache so that 
> browsers renew cache's elements expiry date when they receive a 304 
> error, or to configure Apache to not to answer with error 304, but to 
> reply with the corresponding file, even though this file's been not 
> modified.

Why do you think that if browser will always fetch the content, it will be
faster? The whole meaning of 304 status is that the data don't have to be
fetched, so the loading will be faster. In case of 200 status, all content
will be sent from server to browser again, and THIS is the case where it
might get really slow.

-- 
Matus UHLAR - fantomas, uhlar@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
I don't have lysdexia. The Dog wouldn't allow that.

---------------------------------------------------------------------
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