Re: Re: mod_jk cutting off request params?

2004-09-02 Thread Marcel Stör
Bill Barker [EMAIL PROTECTED] schrieb im Newsbeitrag news:[EMAIL PROTECTED]... I don't know of any problems with the Ajp12Connector (other than the fact that it is old :). It looks like it should get the query string from Apache fine. I also can't see why the request isn't showing up in the

SOLVED! Re: Re: mod_jk cutting off request params?

2004-09-02 Thread Marcel Stör
Marcel Stör wrote: Bill Barker [EMAIL PROTECTED] schrieb im Newsbeitrag news:[EMAIL PROTECTED]... I don't know of any problems with the Ajp12Connector (other than the fact that it is old :). It looks like it should get the query string from Apache fine. I also can't see why the request isn't

mod_jk cutting off request params?

2004-09-01 Thread Marcel Stör
Hi all, I'm confronted with a very strange problem. I've upgraded from Tomcat 3.2.4 to 3.3.2 (we're conservativ over here ;-)). As a result my Apache-Tomcat connection through mod_jk is broken. Ajp12 runs on 8007 and Coyote on 8080. If I access my app through

Re: mod_jk cutting off request params?

2004-09-01 Thread Bill Barker
I don't know of any problems with the Ajp12Connector (other than the fact that it is old :). It looks like it should get the query string from Apache fine. I also can't see why the request isn't showing up in the Tomcat access-log.Of course, AccessLogInterceptor doesn't flush it's output by