> -Original Message-
> From: Costin Manolache
>
> It's most likely a bug. I know Nacho is using JNI with IIS - and the
> code looks fine.
>
Yeah, it was... Just fixed it in the cvs. We were sending reply msg and
the handler was feeding post msg.
Looks fine now (tested with 100K POST d
Mladen Turk wrote:
> Hi,
>
> Apache isn't the bugger here. The jni itself is unable to process the
> POST data.
> The channel_jni is invoked for the getChunk (id 6), but then nothing
> happens (at least I wasn't been able to trace any jni_send).
> It invokes the response dispatcher, but then noth
Hi,
Apache isn't the bugger here. The jni itself is unable to process the
POST data.
The channel_jni is invoked for the getChunk (id 6), but then nothing
happens (at least I wasn't been able to trace any jni_send).
It invokes the response dispatcher, but then nothing happens. (Think
that this mess
Mladen Turk wrote:
Hi,
Seems that we have some problems reading POST data from Apache2.
My proposal is to add the read ahead buffer.
Looking at some modules I found that most of them has that feature.
For example mod_isapi has a default read ahead buffer length of 49152
bytes (48 k). (Why?)
Ques
Mladen Turk wrote:
> Hi,
>
> Seems that we have some problems reading POST data from Apache2.
> My proposal is to add the read ahead buffer.
> Looking at some modules I found that most of them has that feature.
> For example mod_isapi has a default read ahead buffer length of 49152
> bytes (48 k)
Hi,
Seems that we have some problems reading POST data from Apache2.
My proposal is to add the read ahead buffer.
Looking at some modules I found that most of them has that feature.
For example mod_isapi has a default read ahead buffer length of 49152
bytes (48 k). (Why?)
Question:
Can we make so
