ok, that make sense, so I modified my filter1 to just register the filter, print out some text, and return ok, that's it. and it still doesn't print anything if filter2 comes after it? Does that sound wrong to anybody but me?
On Friday 07 December 2001 12:47 pm, you wrote: > I tried out your config and handlers pretty much verbatim and got them > to work just fine. the only real change was that I needed to comment > out > > > return $status unless $status == OK; > > from filter one, since $fh is $r->filename for the first filter, which > brings up 404 when the file is not found. > > that said, yes I see the same thing, but only for 404s. I think the > problem is that you need to deal with your error code properly. > > > now, according to what I've read, this should print out the "Filter > > 1Filter 2", which is what I need to let me get real work done, but all I > > get is Filter 2. So all powerful list, WTF am I missing (it's gotta be > > something obvious, it always is). > > $fh is $r->filename for the first filter in the chain. if > $r->filename does not exist, you need to handle this. $status is one > way of handling it. checking for $fh (which will be undef if > $r->filename does not exist) is another. basically, you definitely > don't want to read from $fh if $fh is not defined :) > > this situation should probably be protected against in Apache::Filter > better, but it basically looks like it is a problem with your logic. > > HTH > > --Geoff -- Jayce^
