tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GOMEZ Henri <hgo...@slib.fr>
Subject RE: Ajp13 change in recent TC 3.3
Date Mon, 17 Sep 2001 20:49:26 GMT
>| -----Original Message-----
>| What about that patch which allways set ContentLength
>| but try to get others datas only in contentLength is set
>| and not -1 ....
>| 
>| 
>| --- Ajp13.java.orig	Mon Sep 17 11:16:05 2001
>| +++ Ajp13.java	Mon Sep 17 11:16:30 2001
>| @@ -411,8 +411,8 @@
>|  	MessageBytes clB=headers.getValue("content-length");
>|          int contentLength = (clB==null) ? -1 : clB.getInt();
>|  	if( dL > 0 ) d("Content-Length: " + contentLength );
>| -    	if(contentLength != 0) {
>| -	    req.setContentLength( contentLength );
>| +        req.setContentLength( contentLength );
>| +    	if(contentLength != 0 && contentLength != -1) {
>|  	    /* Read present data */
>|  	    int err = receive(inBuf);
>|              if(err < 0) {
>
>CL=-1 means the request is chunked, and we must read until
>we get an end of stream, so this patch would break that.
>
>Definitely the changes require upgrading jk when Tomcat
>is upgraded to 3.3.. there's no way around that.

I understand, Larry you should add a note about that.

If you want to use TC 3.3, you should upgrade to mod_jk
present in TC 3.3 or JTC. The mod_jk upgrade is still 
compatible with previous TC 3.2 release....


Mime
View raw message