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 20898] New: - Form POST of more than 4096 bytes fails with SSL
Date Thu, 19 Jun 2003 03:00:45 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=20898>.
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=20898

Form POST of more than 4096 bytes fails with SSL

           Summary: Form POST of more than 4096 bytes fails with SSL
           Product: Apache httpd-2.0
           Version: 2.0.46
          Platform: PC
        OS/Version: Other
            Status: NEW
          Severity: Major
          Priority: Other
         Component: mod_ssl
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: cjames53@yahoo.com


Create a form with more than 4096 of data and POST it to a CGI on an https 
port.  The CGI hangs.  It appears to get the first 4096 bytes, then gets 
stuck.  The same POST works on a non-SSL port.

Note: this may be related to a similar bug reported in the squid development 
group, where they report: "The problem lies in squid's select() logic. SSL 
buffers decrypted bytes, so SSL_pending() will show there are more bytes to 
read in the SSL stream, but select() on the filehandle will never return after 
the client write the last (encrypted) byte."

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


Mime
View raw message