> Ryan Bloom wrote:
> >
> > > [EMAIL PROTECTED] wrote:
> > > >
> > > > rbb         02/04/05 09:50:37
> > > >
> > > >   Modified:    modules/generators mod_autoindex.c
> > > >   Log:
> > > >   This is a HACK!
> > >
> > > Why would it be difficult for the core to preserve OLD_WRITE in
the
> > subreq
> > > filter chain?  We knew how to do that in 2.0.32.  One would hope
we
> > get
> > > smarter
> > > as we get more experienced.
> >
> > Because in pre-2.0.32 code, fast_internal_redirects didn't remove
all of
> > the RESOURCE filters.  It does now, because that is the correct
thing to
> > do.  The problem is that there is one RESOURCE filters that we want
to
> > keep, OLD_WRITE.
> 
> OK, so maybe we proved that OLD_WRITE isn't an ordinary RESOURCE
filter.
> Calling it something else might do the trick.

The problem is that it MUST be a RESOURCE filter, or it will be put in
the wrong location in the filter stack.

Ryan


Reply via email to