John D.Lima wrote: [...]
I was rather hoping to avoid setting up the logic to examine bucket contents.
Reading between the line [sic] I guess the answer is no, $r->custom_response
doesn't work in the request output filter?
Does the connection filter give me access to the $r->headers_out() as well?
In my case, I'm reporting (to the client) an error page when the server fails
to set a particular HTTP response header. I want to do something with that
header value, possibly sending an error page on to the client. With the request
filter, I just $xyz = $f->r->headers_out{'XYZ'} and go on.
Once you are outside (post) the response phase, you can't use its comfy API, because the request has been sent already. In the connection filter you have an access to the raw HTTP headers and the response body.
Seems you have an excellent example for this in your recent -FixupHeaders package
and other tuts. I'll forge ahead with using the bucket code.
Good ;)
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
