tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 30152] New: - content length when length > Integer.MAX_VALUE
Date Fri, 16 Jul 2004 16:06:10 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=30152>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=30152

content length when length > Integer.MAX_VALUE

           Summary: content length when length > Integer.MAX_VALUE
           Product: Tomcat 4
           Version: 4.1.30
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Unknown
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: julian.reschke@gmx.de


Trying to do a HTTP PUT request with content length of a bit above 2GB.

Expected result:

1) req.getContentLength() returns -1 (unknown)
2) req.getHeader("content-length") returns raw string as seen in the HTTP message
3) req.getInputStream() actually returns an input stream from which the actual
number of bytes advertised in the request header can be read.

Current result:

1b) req.getContentLength() returns negative value but not -1
2b) req.getHeader("content-length") returns raw string as seen in the HTTP
message (ok!)
3b) no bytes can be read from req.getInputStream()

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message