Please see if you notice anything glaringly wrong in what I'm doing.
Basically my problem is that my filter isn't passing data along, eg what I
print in filter1 isn't getting output, even though filter2 get's the
filehandle and loops over it. My setup is pretty akin to what the docs offer
in
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
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
Jason Hall wrote:
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?
try this:
package One;
use
AHAH!!! I found it.. thanks, your example showed the difference.
What it was is that I was sending my header before my final filter, which as
I now am guessing, maps STDOUT, which this needs. I'm recommending to the
author to put a note in about where the headers should be printed.
Thanks
Jason Hall wrote:
AHAH!!! I found it.. thanks, your example showed the difference.
What it was is that I was sending my header before my final filter, which as
I now am guessing, maps STDOUT, which this needs.
well, you should be able to print your headers from any filter in the
chain
