On Oct 23, 2007, at 2:51 AM, Ian Ward Comfort wrote:
On Oct 22, 2007, at 11:24 PM, Mladen Turk wrote:
By adding some additional instrumentation to the code, I can see
that each AJP packet is constructed with ((1 + 17) * 13) = 234
envvar attributes -- the whole set of attributes is appended 18
times in succession. (Often this overflows the default maximum
packet size.)
Can you use JkLogLevel debug and attach the packet dumps as well
as the the config?
[1] http://rescomp.stanford.edu/~icomfort/jk/logging.patch
[2] http://rescomp.stanford.edu/~icomfort/jk/httpd.conf
[3] http://rescomp.stanford.edu/~icomfort/jk/workers.properties
[4] http://rescomp.stanford.edu/~icomfort/jk/mod_jk_log
[5] http://rescomp.stanford.edu/~icomfort/jk/ajp.dump
On Oct 31, 2007, at 8:11 AM, [EMAIL PROTECTED] wrote:
http://issues.apache.org/bugzilla/show_bug.cgi?id=43753
Summary: JkEnvVar and Limit of content length HTTP
request POST
Product: Tomcat 6
Version: 6.0.10
Component: Connectors
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
In the httpd.conf Apache 2.0, JkEnvVar is assigned to SERVER_NAME
When I add a virtualhost with a new ServerName, I have immediately
an HTTP error :
Error 413 Request entity too large! The POST method does not allow
the data transmitted, or the data volume exceeds the capacity limit.
I suppose that error is linked to the number of declaration
ServerName (60)
These sound like the same issue to me. Has anyone had a chance to
look at the code?
I could take a stab at a patch quickly, but I'd certainly want
someone more familiar with the codebase to review it.
--
Ian Ward Comfort <[EMAIL PROTECTED]>
System Administrator, Student Computing, Stanford University
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
