httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 17661] New: - Truncated POST-String by more than 8000 chars
Date Wed, 05 Mar 2003 08:17:41 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17661>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17661

Truncated POST-String by more than 8000 chars

           Summary: Truncated POST-String by more than 8000 chars
           Product: Apache httpd-2.0
           Version: 2.0.43
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: All
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: Stephan.Decker.sd@bayer-ag.de


Environment:
Perl 5.0
SGI Irix 6.5

I receive a truncated POST-String after a commit of a form.
The bug only occurred in conjunction with perl(i.e. not with php) and after 
upgrading to apache 2.0.43.
In the earlier version of apache (1.3.22) the POST-functionality was still O.K.

To to test the POST-String, I use the following example.
The CONTENT_LENGTH var is alright (> 8000), but $in is truncated!

read (STDIN, $in, $ENV{'CONTENT_LENGTH'});
print "Content Length: $ENV{'CONTENT_LENGTH'}\n\n<P>\n";
print "Data Input: $in\n\n<P>\n";
print "Data Length: ", length $in;

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message