I believe I have made some progress now. It looks like this is a problem
with mod_perl and mod_jk interacting poorly. I haven't investigated why
yet, but mod_perl is calling ap_should_client_block in the authentication
phase of Apache, which plays havoc with mod_jk's call in the handler.
Mo
At 06:50 PM 1/18/2005, Ryan Bloom wrote:
>Actually, both 1.2.6 and 1.2.8 of mod_jk. What do you mean re-piping body
>content? I haven't forced http/1.0 yet, I was about to trace through
>Apache to find the problem. My initial investigation looks like the
>problem is in Apache somewhere, look
Actually, both 1.2.6 and 1.2.8 of mod_jk. What do you mean re-piping body
content? I haven't forced http/1.0 yet, I was about to trace through
Apache to find the problem. My initial investigation looks like the
problem is in Apache somewhere, looks like
ap_setup_client_block/ap_should_clien
Hi Ryan, fancy meeting up here :) You don't mention, so
I'll confirm - you are using mod_jk 1.2.8 (brand new release)?
This sure sounds like the (rather obscure) issues with re-piping
body content, and taking a simple guess, if you drop back and
force http/1.0 (eliminate chunking) the issue goes a
