Re: Invalid Content-Length error for the size greater than

I committed a patch for mod_jk using 64 Bit unsigned ints for content length. This patch still needs testing. I only verified, that it does not break normal operation (at least not on Solaris with Apache 2.2). I don't know, if anyone of those who were working on this bug until now (Bill?

Re: Invalid Content-Length error for the size greater than

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bill, Bill Barker wrote: This would let us see what mod_proxy_ajp is sending to Tomcat (which I very strongly suspect is wrong). Tomcat should still accept any valid numeric Content-Length header, even if it exceeds Integer.MAX_VALUE. The Java

Re: Invalid Content-Length error for the size greater than

Bill, I believe I am using mod_proxy_ajp connector because this is what I have on my httpd.conf: ProxyPass /axis ajp://192.168.11.10:8009/axis ProxyPassReverse /axis ajp://192.168.11.10:8009/axis The version of mod_proxy_ajp is Apache/2.2.3 Thanks On Tue, 2007-06-12 at 12:59 -0400, Christopher

Re: Invalid Content-Length error for the size greater than

Bill, As your comment earlier I did open a bug here is a link: http://issues.apache.org/bugzilla/show_bug.cgi?id=42608 I don't know It's a right place to open this DR and those developers have time to do anything with it. apache-tomcat is a new baby to me and I am not familiar with mod_jk

Re: Invalid Content-Length error for the size greater than

Daniel Dang [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Bill, As your comment earlier I did open a bug here is a link: http://issues.apache.org/bugzilla/show_bug.cgi?id=42608 I don't know It's a right place to open this DR and those developers have time to do anything with

Re: Invalid Content-Length error for the size greater than

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mark, Mark Thomas wrote: Christopher Schultz wrote: Since the Java part of the connector is bundled with Tomcat, is that considered to be part of mod_jk (which I always thought of as the c/c++ apache httpd module) or part of Tomcat? For instance,

Re: Invalid Content-Length error for the size greater than

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bill, Bill Barker wrote: Yes, the exception is thrown because the first character in the Content-Length header isn't a digit, so I'm guessing that it is coming in with a leading '-' from mod_jk. Otherwise, while the Java side could be

Re: Invalid Content-Length error for the size greater than

Christopher Schultz wrote: Mark Thomas wrote: I'd use Connector:AJP but it doesn't really matter. That appears to be a component of the Tomcat product... I'm curious why you make the distinction that this is /not/ a bug in Tomcat, but rather in mod_jk. If the bug goes under the Tomcat

Re: Invalid Content-Length error for the size greater than

Christopher Schultz [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mark, Mark Thomas wrote: Christopher Schultz wrote: Since the Java part of the connector is bundled with Tomcat, is that considered to be part of mod_jk (which I

Re: Invalid Content-Length error for the size greater than

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Filip, Filip Hanik - Dev Lists wrote: the servlet specification defines Content-Length as an int. even though in some places tomcat has it as a long, you are still running into this limitation so the problem is in the spec, and needs to be

Re: Invalid Content-Length error for the size greater than

Christopher Schultz wrote: Filip, Filip Hanik - Dev Lists wrote: the servlet specification defines Content-Length as an int. even though in some places tomcat has it as a long, you are still running into this limitation so the problem is in the spec, and needs to be corrected there I've

Re: Invalid Content-Length error for the size greater than

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mark, Mark Thomas wrote: Christopher Schultz wrote: Filip, Filip Hanik - Dev Lists wrote: the servlet specification defines Content-Length as an int. even though in some places tomcat has it as a long, you are still running into this

Re: Invalid Content-Length error for the size greater than

Christopher Schultz wrote: Mark Thomas wrote: It's fixed in Tomcat. See Bill's reply to your original post on this topic for possible mod_jk / AJP issues. Oh, sorry. I see that it's a bug in the Java half of the Jk connector. I haven't looked at the code, but from Bill's post it looks like

Re: Invalid Content-Length error for the size greater than

Mark Thomas [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Christopher Schultz wrote: Mark Thomas wrote: It's fixed in Tomcat. See Bill's reply to your original post on this topic for possible mod_jk / AJP issues. Oh, sorry. I see that it's a bug in the Java half of the Jk

RE: Invalid Content-Length error for the size greater than

From: Daniel Dang [mailto:[EMAIL PROTECTED] Subject: Invalid Content-Length error for the size greater than But when I tried to send 3GB binary data I got the following error below: Since Bill B already answered your question the first time you sent it, why did you send it again? -

Re: Invalid Content-Length error for the size greater than

the servlet specification defines Content-Length as an int. even though in some places tomcat has it as a long, you are still running into this limitation so the problem is in the spec, and needs to be corrected there Filip Daniel Dang wrote: Hi All I am using Apache-tomcat-5.5.16 version

Re: Invalid Content-Length error for the size greater than 2147483647

Daniel Dang [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Hi All, I tried to send 3G size data to apache-tomcat-5.5.16 using ajp connector and I got error below.. I think MessageByte.getInt() only allows 2.1Gigabytes data as an Integer only 32 bits because of I send more than