> "Ryan Bloom" <[EMAIL PROTECTED]> writes: > > > > But I guess the problem is a misuse of r->proto_input_filters > > > vs. r->input_filters on this path??? > > > > Nope. This problem is in the proxy itself. > > That's what I meant... I had tried half of your fix with no luck (and > worse, no understanding :) ). > > > Make_fake_proxy_req isn't > > setting r->proto_input_filters or r->proto_output_filters. That means > > that the rest of the logic is wrong. I'll try to get around to fixing > > this tonight, but I may not get to it. > > Thanks for fixing it!
Glad I got to it last night. Now, is there anything I can do to help people understand the recent changes better? Ryan
