This is no longer the case, get the latest version and you should be
able to configure the packet size
Filip
Dave McMurtrie wrote:
Hi list,
I'm not sure if you'd prefer this to go to the user list, but I think
it probably belongs here, so I'll start here.
We have an application that is occasionally bumping into the 8K max
packet size of mod_jk, which causes our users to get a "Request Entity
Too Large" page.
I find the following in the logs:
Mon Mar 26 11:27:54 2007] [9849:0000] [error
ajp_marshal_into_msgb::jk_ajp_common.c (441): failed appending the
auth type
The exact thing that it fails to append differs at times, but it's
obvious that the reason is because the browser is sending more than 8K
of data in the request.
I started to look at the mod_jk code and it seems that the 8K limit
ends up being governed by the DEF_BUFFER_SZ constant which is (8 *
1024). 6 bytes are used for non-payload protocol stuff, so that ends
up meaning that the protocol allows for 8186 bytes of payload in a
given request. I gathered that the protocol defines the bytes at
index 2 and 3 of the packet as a length specifier. This value is
stored as two unsigned char values, so the true protocol limit of a
given packet should be 65536 bytes (65530 bytes of payload).
I'm wondering why the 8K limit was implemented, and I'm also wondering
if there's any reason it can't be changed. A quick glance makes it
look like this would be as simple as redifining DEF_BUFFER_SZ. I'm
going to spend more time looking at the code today so I can get a
better understanding of how it works overall, but I'd like to get an
expert opinion on the matter.
Thoughts?
Thanks,
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
