hi doug...
I've been playing around with Apache::Filter in 2.0 and found
something I don't understand.
if I call
$r->update_mtime($time);
$r->set_last_modified();
_after_ I read/write to the filter, the the Last-Modified header
doesn't get set properly by default_handler but if I call them before
the filter stuff all is as expected. simiarly, if I leave out the
call to set_last_modified(), default_handler doesn't see the new mtime
when it calls set_last_modified().
this all seems a bit strange to me, but maybe there's some hidden
interaction I'm missing. is the request_rec gleaned from the filter
via $filter->r a different one than the real request_rec
default_handler sees?
I would think that an output filter should have the option to
update $r->mtime then leave it to later filters/content handlers to
decide if they are able to properly set Last-Modified. in my
particular case, it's an HTML::Clean based filter - if I could set the
mtime only, then default_handler could call set_last_modified() but a
dynamic handler could skip it. but this is all new to me, and I
probably haven't done the reading I should.
anyway, just a thought. for those interested, here's my work to date.
http://www.modperlcookbook.org/~gyoung/modules/experimental/Apache-Clean-2.00b.tar.gz
I still have to figure out how to call per-server cleanups to handle
configuration changes, but it's pretty close to being a complete port
from 1.3 to 2.0. Apache-Test++ :)
--Geoff
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
