Return-Path: 
 <users-return-74137-apmail-httpd-users-archive=httpd.apache.org@httpd.apache.org>
Delivered-To: apmail-httpd-users-archive@www.apache.org
Received: (qmail 70051 invoked from network); 23 Jul 2007 18:59:21 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 23 Jul 2007 18:59:21 -0000
Received: (qmail 35908 invoked by uid 500); 23 Jul 2007 18:59:11 -0000
Delivered-To: apmail-httpd-users-archive@httpd.apache.org
Received: (qmail 35898 invoked by uid 500); 23 Jul 2007 18:59:11 -0000
Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
list-help: <mailto:users-help@httpd.apache.org>
list-unsubscribe: <mailto:users-unsubscribe@httpd.apache.org>
List-Post: <mailto:users@httpd.apache.org>
List-Id: <users.httpd.apache.org>
Delivered-To: mailing list users@httpd.apache.org
Received: (qmail 35882 invoked by uid 99); 23 Jul 2007 18:59:11 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Jul 2007 11:59:11 -0700
X-ASF-Spam-Status: No, hits=2.0 required=10.0
	tests=RCVD_ILLEGAL_IP,RCVD_IN_WHOIS_BOGONS,SPF_HELO_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (herse.apache.org: local policy)
Received: from [212.163.42.137] (HELO televes.com) (212.163.42.137)
    by apache.org (qpsmtpd/0.29) with SMTP; Mon, 23 Jul 2007 11:59:08 -0700
Received: from tvesnt.televes.com [1.1.1.131] by televes.com with ESMTP
  (SMTPD32-4.07) id AB23254D0140; Mon, 23 Jul 2007 21:01:55 +03d0
Received: from [1.1.3.46] (tr345.televes.com [1.1.3.46]) by tvesnt.televes.com
 with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id PJBYL6TH; Mon, 23 Jul 2007 20:53:42 +0200
Message-ID: <46A4FA60.5030009@televes.es>
Date: Mon, 23 Jul 2007 20:58:40 +0200
From: Bello Martinez Sergio <serbel@televes.es>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: users@httpd.apache.org
References: <46A0A74C.50200@televes.es>
	 <e498c1660707200615g54021161k7ae781a5e2ec8c09@mail.gmail.com>
	 <46A469FB.7000707@televes.es>
	 <e498c1660707230623l172f49d2pe429143d0ec68d6b@mail.gmail.com>
	 <46A4B70E.9050900@televes.es>
	 <e498c1660707230715h5b8777adv855e4f50ebd64920@mail.gmail.com>
	 <46A4EE88.8070409@televes.es>
 <e498c1660707231119g20279fc3lcdffa8ec8145e801@mail.gmail.com>
In-Reply-To: <e498c1660707231119g20279fc3lcdffa8ec8145e801@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Virus-Checked: Checked by ClamAV on apache.org
Subject: Re: [users@httpd] Want to avoid 304 error

Ok, thanks. So, the reason of my error was to suppose that including

   <IfModule mod_expires.c>
               ExpiresActive On
               ExpiresByType text/javascript "access plus 2 minutes"
       </IfModule>

(note that the value '2 minutes' is for testing purposes only) would 
apply this header to response even if the return code is 304. That's not 
true.
So, the solution I tell you in a previous post, thats including

   <LocationMatch "\.js$">
       Header append Cache-Control "max-age=120"
   </LocationMatch>

makes Apache to include a 'Cache-Control: max-age=120' header in that 
response. But this is not enough, because it seems that Firefox doesnt 
take into account this header if response code is 304. It set 1970 as 
new expiry date no matter the value in this header.


Joshua Slive escribi�:
> On 7/23/07, Bello Martinez Sergio <serbel@televes.es> wrote:
>
>> - Headers request/response after expiry time:
>
>>
>>     HTTP/1.x 304 Not Modified
>>     Date: Mon, 23 Jul 2007 17:49:31 GMT
>>     Server: Apache/2.0.54 (Linux/SUSE)
>>     Connection: Keep-Alive
>>     Keep-Alive: timeout=15, max=98
>
> So, here's your problem. The server reports that the resource is not
> modified, but does not send a new Cache-Control: max-age or Expires
> header. The old headers are therefore kept as valid, meaning that the
> resource is not-modified, but expired.
>
> Here's a similar set of headers from apache's core handler:
> Original:
> HTTP/1.1 200 OK
> Date: Mon, 23 Jul 2007 18:11:38 GMT
> Server: Apache/2.3.0-dev (Unix)
> Last-Modified: Wed, 11 Jul 2007 08:03:12 GMT
> ETag: "9276b6-4527-4f313000"
> Accept-Ranges: bytes
> Content-Length: 17703
> Cache-Control: max-age=86400
> Expires: Tue, 24 Jul 2007 18:11:38 GMT
> Vary: Accept-Encoding
> Connection: close
> Content-Type: text/html
>
> If-Modifed-Since request:
> HTTP/1.1 304 Not Modified
> Date: Mon, 23 Jul 2007 18:11:52 GMT
> Server: Apache/2.3.0-dev (Unix)
> ETag: "9276b6-4527-4f313000"
> Expires: Tue, 24 Jul 2007 18:11:52 GMT
> Cache-Control: max-age=86400
> Vary: Accept-Encoding
>
> Note the Cache-Control and Expires headers which update the client's
> freshness info.
>
> Then the question is: why aren't these headers getting sent on your
> 304 responses. I don't know whether this is a problem with your
> application or with apache, but given that I know nothing about your
> app, I'm putting my guess there ;-)
>
> 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

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