You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
POST parameters are currently ignored because of incorrect MIME type handling. POST parameters are only parsed in situations where Content-Type header sent by the client equalsapplication/x-www-form-urlencoded. (Which is practically never since that is incorrect behavior from browser as it's missing the charset parameter.)
Possible solutions:
Make Request class in sapi/request.cc to check whether Content-Type header starts withapplication/x-www-form-urlencoded. (Bad)
Implement some kind of MIME type parser which separates the actual MIME type from character encoding. (Good)
Side note: One major issue is also that we currently support only UTF-8 character encoding. While all browsers should send their data encoded with UTF-8, some older browsers might send it in ISO-8859-1 or whatever if character encoding is not correctly specified in <form> tag or Content-Type header sent by the server. We actually might need to implement support for other character encodings which is going to be painful.
The text was updated successfully, but these errors were encountered:
POST parameters are currently ignored because of incorrect MIME type handling. POST parameters are only parsed in situations where
Content-Type
header sent by the client equalsapplication/x-www-form-urlencoded
. (Which is practically never since that is incorrect behavior from browser as it's missing thecharset
parameter.)Possible solutions:
Request
class insapi/request.cc
to check whetherContent-Type
header starts withapplication/x-www-form-urlencoded
. (Bad)Side note: One major issue is also that we currently support only UTF-8 character encoding. While all browsers should send their data encoded with UTF-8, some older browsers might send it in ISO-8859-1 or whatever if character encoding is not correctly specified in
<form>
tag orContent-Type
header sent by the server. We actually might need to implement support for other character encodings which is going to be painful.The text was updated successfully, but these errors were encountered: