> > Thanks for this. I had put 'PerlInputFilterHandler
> > iPAQApache::ResetBrowser' inside the proxy block, and it
> should have
> > been outside like you said.
>
> So it did work this time, right? Perhaps we should issue a
> warning if a
> connection filter is found insider <Location> or alike.
Worked perfectly this time :) I think a warning would be nice if it's
not supposed to be there. If it's put within the <Proxy> tags, it only
recieves the request data, not the headers. When it's outside, it
receives headers and data.
>
> >>PerlInputFilterHandler iPAQApache::ResetBrowser
> >>
> >>Is this the correct directive?
> >
> >
> > The directive is correct, but you don't show your code and your
> > config, so I have no idea if the rest is correct or not. This
> > directive is used to configure both, connection and request level
> > filters. It's the attribute of
> > the handler subroutine is what makes the difference and the
> placement in
> >
> > httpd.conf.
> >
> > You need to declare it as:
> >
> > package iPAQApache::ResetBrowser;
> > use base qw(Apache::Filter);
> > sub handler : FilterConnectionHandler { your code is here } 1;
> >
> > and you need to put it outside of <Location> or similar block in
> > httpd.conf just like shown at:
> >
> http://perl.apache.org/docs/2.0/user/handlers/filters.html#Con
nection_In
> put_Filters
>
******** _/ ***********************************************
***** _/ ****** Chris Pringle **
**** _/ ***** **
*** _/_/_/ _/_/_/ ***** Personal Systems Group (PSG) **
*** _/ _/ _/ _/ ***** Hewlett Packard - Bristol **
*** _/ _/ _/_/_/ ***** **
**** _/ INVENT ****** Tel - +44 (0) 117 31 29664 **
****** _/ ******** Email - [EMAIL PROTECTED] **
******* _/ *************************************************
