Justin Erenkrantz wrote:
--On Tuesday, September 7, 2004 2:48 PM +1000 Ian Holsman
<[EMAIL PROTECTED]> wrote:
Not really, but I'd like to see a patch posted to this list first before
committing it. There's a couple ways I could see implementing this, but
not sure which way you are intending t
Just a thought... why does this restriction exist in the first place?
Because, a long time ago, queries contained mostly user-defined
strings that were not likely to result in a later hit, so it wasn't
worth the effort. Now, some web applications use a bogus query
string in order to override cachi
Justin Erenkrantz wrote:
--On Tuesday, September 7, 2004 2:48 PM +1000 Ian Holsman
<[EMAIL PROTECTED]> wrote:
ok.. so I've started playing with mod-cache again, and I noticed the
following:
- there is no way to cache something with query-args which doesn't return
a expires tag.
proposal: add a Ca
--On Tuesday, September 7, 2004 2:48 PM +1000 Ian Holsman
<[EMAIL PROTECTED]> wrote:
ok.. so I've started playing with mod-cache again, and I noticed the
following:
- there is no way to cache something with query-args which doesn't return
a expires tag.
proposal: add a CacheIgnoreNoExpires direct
ok.. so I've started playing with mod-cache again, and I noticed the
following:
- there is no way to cache something with query-args which doesn't
return a expires tag.
proposal: add a CacheIgnoreNoExpires directive so that we can cache them
- Even if we add a optional function to ignore the qu
