On Tuesday 25 October 2011, Noah Robin wrote:
I ran some tests on this and the following modified version will
work:
Header always set Cache-Control max-age=%{CACHE_LIFETIME}e
env=CACHE_LIFETIME
RewriteRule /example http://www.example.com/
[E=CACHE_LIFETIME:604800]
..however, this still
On Oct 27, 2011, at 3:35 PM, Stefan Fritsch wrote:
On Tuesday 25 October 2011, Noah Robin wrote:
I ran some tests on this and the following modified version will
work:
Header always set Cache-Control max-age=%{CACHE_LIFETIME}e
env=CACHE_LIFETIME
RewriteRule /example
I ran some tests on this and the following modified version will work:
Header always set Cache-Control max-age=%{CACHE_LIFETIME}e
env=CACHE_LIFETIME
RewriteRule /example http://www.example.com/ [E=CACHE_LIFETIME:604800]
..however, this still leaves an open question in my mind: How to solve for
Hello all,
Recent versions of Firefox, IE, and Chrome will now cache HTTP 301 and
302 responses based on the cache control headers, (roughly) in line
with the HTTP spec. This is, in general, a good thing, but can cause
some issues, as I've discussed here: http://rwec.co.uk/q/cached-redirs
When
A more advanced version would be to allow custom HTTP headers using an
[HH=Foo:Bar] syntax or similar, but this may be going a bit far.
Does env=xxx in the Header directive then R=...,E= in RewriteRule work?
On 23/10/2011 20:54, Eric Covener wrote:
A more advanced version would be to allow custom HTTP headers using an
[HH=Foo:Bar] syntax or similar, but this may be going a bit far.
Does env=xxx in the Header directive then R=...,E= in RewriteRule work?
Hi Eric,
I haven't got a test environment
