> I've now tried any combination of: > ( $r | $subr ) ->assbackwards( 0 | 1 );
blarg. yes, that was supposed to be $subr->assbackwards(), not $r->assbackwards. > The only one with any effect was: $r->assbackwards(1); which resulted in > no headers at all. Not quite what I was hoping for ;o) hmph, that's odd. the issue is that you want the subrequest to go directly to the client, with headers, right? $subr->assbackwards(0) ought to do that. can you check the result of my $ab = $subr->assbackwards; ? I'd hope it's set to 1. for the record and archives, this is exactly what $sub->run(1); # sets sub->assbackwards(0); did in mod_perl 1.0. in mp2 we require you to call $sub->assbackwards() yourself. > > But thanks anyway. > > My gut feeling (nothing to go by, by the way) is that I somehow need to > tell apache2 that, it shouldn't strip the headers when running a > subrequest. yes, that's what the assbackwards flag is for :) > > Maby I should just go back to apache1.3 & mod_perl, that does what I > want it to. well, if you like. but we can probably make this work, too. after all, it ought to work, unless httpd 2.0 prohibits it, which IIRC it doesn't. but it's been a while since I looked at that code. > > Or maby, the problem is that in > "xs/Apache2/SubRequest/Apache2__SubRequest.h" "mpxs_ap_run_sub_req" runs > "modperl_wbucket_flush" to make sure all that is printed before ->run() > is outputed, however this might (I havn't diged deep enough into the > code yet) send the headers, and the run the script forcing apache to > discart them. headers are handled by a separate filter. maybe that's where the issue is, though. IIRC, I was having lots of issues using subrequests due to that flush call, but I'm not sure what it was (since it was 2 years ago). you might want to check the dev@perl.apache.org archives. --Geoff
