If you're using the bucket brigade API you'd have to intercept the
headers and modify them there. You might have an easier time doing
something like this using the stream API, but i don't really know, just
taking a shot in the dark. I'd think that it's certainly possible
though, somehow.
Th
Marc M. Adkins wrote:
Can I not return Apache2::Const::NOT_FOUND from handler()?
I've never used filters for this, but you can certainly return NOT_FOUND
from a handler.
Colin
Thought I had it. Used $filter->r->status() to set the status code on
the request from within the output filter. That would have made sense
and resulted in a big "d'oh!" Sadly it doesn't seem to change the
result either.
Time to do something else for a while. Thanks in advance for any hint
Hmmm...it's a bucket brigade FilterRequestHandler output filter. It
seems to not care what return code I use, whatever is in the bucket
brigade goes out. Can I not return Apache2::Const::NOT_FOUND from
handler()? That seems odd.
Marc M. Adkins wrote:
I'm trying to cause a 404 error from an
I'm trying to cause a 404 error from an output filter and it isn't doing
what I expect. Is this even possible?
mma