Hi Filip,
On Wed, Oct 15, 2008 at 10:44 PM, Filip Hanik - Dev Lists
<[EMAIL PROTECTED]> wrote:
> use mod_proxy_http or mod_jk,
I am now but I don't understand why it behaved as it did - any idea?
>> I have an application which parses XML. It sits behind an Apache
>> Httpd 2.2 server using
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert,
Robert Koberg wrote:
> On Oct 15, 2008, at 5:44 PM, Filip Hanik - Dev Lists wrote:
>
>> use mod_proxy_http or mod_jk,
>
> I have seen a few posts recommending mod_proxy_http a little bit over
> mod_jk. Why is that?
Note that mod_jk and mod_
On Oct 15, 2008, at 5:44 PM, Filip Hanik - Dev Lists wrote:
use mod_proxy_http or mod_jk,
I have seen a few posts recommending mod_proxy_http a little bit over
mod_jk. Why is that?
I used mod_jk recently simply because it was on the tomcat site. I
just assumed it was the default/best op
use mod_proxy_http or mod_jk,
Filip
Stephen Nelson-Smith wrote:
Hi,
I have an application which parses XML. It sits behind an Apache
Httpd 2.2 server using mod_proxy_ajp. I am finding that if I POST
more than about 1600 chars, the POST gets truncated, and I get an XML
parse error.
Httpd log
Hi,
I have an application which parses XML. It sits behind an Apache
Httpd 2.2 server using mod_proxy_ajp. I am finding that if I POST
more than about 1600 chars, the POST gets truncated, and I get an XML
parse error.
Httpd logs show:
[Tue Sep 30 19:40:27 2008] [debug] mod_proxy_ajp.c(206): pr