> 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: [EMAIL PROTECTED] > ReportedBy: [EMAIL PROTECTED] > > > 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.
Yes, a trim() is missing here. The new (and still upcoming) HTTP connector is great at stripping out unneeded spaces (and canonicalizing multiline headers, also); the current one can't strip trailing spaces. Remy -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
