On Tue, 5 Jun 2001, Ben Laurie wrote:
> [EMAIL PROTECTED] wrote:
> >
> > On Tue, 5 Jun 2001, Graham Leggett wrote:
> >
> > > sterling wrote:
> > >
> > > > reset_filters always removed all filters (including TLS). This is a
> > > > problem in general - I think the only reason the filters are all removed
> > > > on error is to prevent infinite recursion (in the case where the error
> > > > came from one of the filters). Optimally, if I add a filter, it should
> > > > get called even on error -
> > >
> > > In theory though on error we should only be removing the request
> > > filters, not the connection filters. The TLS filter would be a
> > > connection filter, and would then not be affected... right?
> >
> > That's not the way the code works right now. Right now, we remove all
> > filters. There is no really good way around this. Basically, we are
> > trying to get to a position that we know is good, so that we can return as
> > much information as possible.
>
> Return to whom? Clearly if you remove the TLS filter, it won't be the
> user!
Yep, right now TLS is broken. I don't have a great idea for how to fix it
though. :-(
Ryan
_______________________________________________________________________________
Ryan Bloom [EMAIL PROTECTED]
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------
