httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alf Eaton <>
Subject Re: [users@httpd] Force caching of responses with no explicit expiry date, where the request contains a query string
Date Sun, 28 Feb 2010 12:33:09 GMT
On 27 February 2010 04:12, Jonathan Zuckerman <> wrote:
> On Fri, Feb 26, 2010 at 6:39 AM, Alf Eaton <> wrote:
>> This seems to be something that's been around for a while, but I
>> haven't been able to find anything conclusive saying that it's
>> supposed to work this way:
>> I'm using Apache 2.2 as a forward proxy, aiming to cache all responses.
>> I've set CacheDefaultExpire to 86400 (1 day), so any requests that
>> don't have explicit expiry dates should still be cached.
>> In the logs, I'm still seeing the message.
>> "not cached. Reason: Query string present but no explicit expiration time"
>> It seems that if there's a query string in the request, the default
>> expiry date isn't applied, so the response isn't cached.
>> Is there a way to force responses that have no explicit expiry date to
>> be cached, even where the request contains a query string?
>> alf
>> Related:
>> ("mod_cache:
>> CacheDefaultExpire is ignored?")
>> ("mod_disk_cache problem")
>> ("mod_cache and query
>> strings")
> this might be helpful:

Thanks, I did try CacheIgnoreQueryString, but it treats all responses
the same regardless of their query string (i.e. requests with
different query strings all get the same cached response). I need to
be able to cache responses with different query strings distinctly -
as if they had query strings and an expiry header.


The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message