You mentioned applying the fixes from 2.2 to 2.0.  Would I get the source code 
for mod_cache.so and mod_disk_cache.so from the 2.2 project, put it in the 
proper directories on apache 2.0 and the rebuild?

Lance Campbell
Project Manager/Software Architect
Web Services at Public Affairs
University of Illinois
217.333.0382
http://webservices.uiuc.edu
 

-----Original Message-----
From: Axel-Stephane SMORGRAV [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, January 09, 2008 10:42 AM
To: users@httpd.apache.org
Subject: Re: [EMAIL PROTECTED] mod_cache

Both the max-age=0 and the no-cache request directives should force an 
end-to-end reload.

As I said earlier, there is a bug that causes Apache to ignore the 
Cache-Control request directives. That bug is fixed in 2.2.x, or you could 
apply the 2.0.x patch I referred to. 

Just in case you did not see it, I also replied to your original thread "RE: 
[EMAIL PROTECTED] mod_disk_cache"


-ascs
 
-----Message d'origine-----
De : Campbell, Lance [mailto:[EMAIL PROTECTED] Envoyé : mercredi 9 janvier 2008 
16:33 À : users@httpd.apache.org Cc : Axel-Stephane SMORGRAV Objet : RE: [EMAIL 
PROTECTED] mod_cache

Is there a header string I could pass in the newer version of 
mod_cache/mod_disk_cache that would cause it to refresh the cache with new 
content for the requested URL?

In version 2.0.59 there does not seem to be a header string that will do this.  
I got the idea that passing the following header string would do that:

"Cache-Control: max-age=0"

After looking at the code I found that this is not the case.  Using this string 
in the header simply tells mod_cache to not check the cache for the requested 
content.  So the next time mod_cache gets a request for the same URL without 
the above header string it will give back the old cached content. 

I am really looking for a way to tell mod_cache, "hey, refresh the cache with 
new content for the requested URL".

Thanks for any help you can give me.



Lance Campbell
Project Manager/Software Architect
Web Services at Public Affairs
University of Illinois
217.333.0382
http://webservices.uiuc.edu
 
-----Original Message-----
From: Axel-Stephane SMORGRAV [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 09, 2008 1:53 AM
To: users@httpd.apache.org
Subject: RE: [EMAIL PROTECTED] mod_cache

Yes you did.

http://issues.apache.org/bugzilla/show_bug.cgi?id=19441 

Many of the developers actively participate on this list also, so there is no 
need to post to the dev list. If you believe you have found a problem you 
should search Bugzilla for reports of problems similar to what you reported.

-ascs
________________________________

De : Campbell, Lance [mailto:[EMAIL PROTECTED] Envoyé : mercredi 9 janvier 2008 
07:44 À : users@httpd.apache.org Objet : [EMAIL PROTECTED] mod_cache


<![endif]--> 

I think I found an issue with mod_cache.  Where do I go to post a question to 
the development group for this mod?

 

Thanks,

 

Lance Campbell

Project Manager/Software Architect

Web Services at Public Affairs

University of Illinois

217.333.0382

http://webservices.uiuc.edu

 


---------------------------------------------------------------------
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: [EMAIL PROTECTED]
   "   from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
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: [EMAIL PROTECTED]
   "   from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
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: [EMAIL PROTECTED]
   "   from the digest: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to