Nick Kew wrote:
On 28 Sep 2008, at 23:38, Gordon Mohr wrote:
Using mod_expires in Apache 2.2.X, I want everything *except* 5XX
status code responses (like 503, service unavailable/busy) to have an
Expires header added.
That doesn't make sense. For many response codes, it'
Using mod_expires in Apache 2.2.X, I want everything *except* 5XX status
code responses (like 503, service unavailable/busy) to have an Expires
header added.
I don't see a switch to limit mod_expires by response code.
It looks like a 'Header unset' conditional on the existence of an
environme
Nick Kew wrote:
On Tue, 23 Sep 2008 18:17:11 -0700
Gordon Mohr <[EMAIL PROTECTED]> wrote:
It looked like 'early' might have
some chance of removing the original Expires without disturbing the
mod_expires addition.
Not a chance. It happens long before the proxy has bee
Nick Kew wrote:
On Tue, 23 Sep 2008 16:49:19 -0700
Gordon Mohr <[EMAIL PROTECTED]> wrote:
Any ideas what I'm doing wrong, if anything?
Sounds like you're using an older Apache version than you think:
that's exactly what I'd expect from Apache 2.0.x, which didn
I'm trying to use the 'early' keyword on a Header directive in Apache
2.2.4 on Ubuntu, and having no success.
My first attempt was:
Header unset MyHeader early
And I got an error: "header unset takes two arguments"
OK, I thought, maybe 'unset' is special (even though I'd really like to
use i
