> -----Original Message-----
> From: Matt Sergeant [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, September 11, 2001 5:36 AM
> To: 'Brian Wheeler'; [EMAIL PROTECTED]
> Subject: RE: AxKit & Last-Modified header
>
>
> > -----Original Message-----
> > From: Brian Wheeler [mailto:[EMAIL PROTECTED]]
> >
> > $r->header_out("Last-Modified"=>'');
> > and
> > $r->header_out("Last-Modified"=>undef);
> >
> > but the header still comes out.
> >
> > Thoughts? Am I on the right track?
>
> Maybe:
>
> $r->headers_out->unset('Last-Modified');
hmmm, I don't know the AxKit architecture really, but I don't think you can
get rid of the Last-Modified header when using default-handler since it
calls set_last_modified() explicitly. IIRC AxKit uses the default-handler as
its caching engine, right?
if that's true, you might want to try fiddling with mod_expires and see if
you can get the results you want from it.
from mod_perl you might be able to enforce a stale page by setting
$r->mtime(0) before the Apache default content handler runs, which ought to
result in a Last-Modified header of Jan 1, 1970 (untested, but I'm pretty
sure I tried it once)
HTH
--Geoff
