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 6644] New: - Whitespace after Content-type header value leads to POST method failure
Date Fri, 22 Feb 2002 13:13:08 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=6644>.
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=6644

Whitespace after Content-type header value leads to POST method failure

           Summary: Whitespace after Content-type header value leads to POST
                    method failure
           Product: Tomcat 4
           Version: Unknown
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: HTTP/1.1 Connector
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: vnesek@yahoo.com


Whitespace after Content-type header value leads to POST method failure.
For example:
"POST /foo HTTP/1.1"
"Host: bar"
"Content-type: application/x-www-form-urlencoded "
"Content-length: 3"
""
"a=b"

will not correcty extract POST parameters. If whitespace after
application/x-www-form-urlencoded is removed everything works fine.

I am not sure what is correct behaviour regarding to HTTP/1.1, but
there are some libs that for whatever reason append offending blank.

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


Mime
View raw message