> -----Original Message-----
> From: Geoffrey Young [mailto:[EMAIL PROTECTED]]
>
> > -----Original Message-----
> > From: Matt Sergeant [mailto:[EMAIL PROTECTED]]
> >
> > > -----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?
"It depends" :-)
But yes, you might be right, depending on how the content gets delivered.
You could always add in a blank AxOutputTransformer, which will force AxKit
to just use print(), even for cached content.
Matt.
________________________________________________________________________
This email has been scanned for all viruses by the Star Internet Virus Screen.
The service is provided in partnership with MessageLabs, the email security company.
For more information on a higher level of virus protection visit www.star.net.uk
________________________________________________________________________
