Frank Maas wrote:
>> but the thing about output filters is they should do something like
>>
>> return DECLINED unless $r->content_type =~ m/something_I_can_handle/;
>>
>> so your xml filter should decline (or better, remove itself) from the
>> filter chain if it's not xml you're being asked to
> but the thing about output filters is they should do something like
>
> return DECLINED unless $r->content_type =~ m/something_I_can_handle/;
>
> so your xml filter should decline (or better, remove itself) from the
> filter chain if it's not xml you're being asked to process.
yup, I'll tell
Frank Maas wrote:
>>> This object does some basic things for generating XML, hence the
>>> content_type. This, again, works fine. Now the problem - if an
>>> unexisting action for this "XML subclass" is requested, the AUTOLOAD
>>> kicks in. The AUTOLOAD sets the content-type back to HTML
>>>
>> This object does some basic things for generating XML, hence the
>> content_type. This, again, works fine. Now the problem - if an
>> unexisting action for this "XML subclass" is requested, the AUTOLOAD
>> kicks in. The AUTOLOAD sets the content-type back to HTML
>> ($r->content_type('text/html'
On Fri, 28 Apr 2006 10:02:33 +0200
Frank Maas <[EMAIL PROTECTED]> wrote:
> This object does some basic things for generating XML, hence the
> content_type. This, again, works fine. Now the problem - if an
> unexisting action for this "XML subclass" is requested, the AUTOLOAD
> kicks in. The AUTOL
