https://bz.apache.org/bugzilla/show_bug.cgi?id=61264
Bug ID: 61264
Summary: Default charset used when Content-Type request header
specifies invalid charset
Product: Tomcat 8
Version: 8.5.15
Hardware: PC
Status: NEW
Severity: normal
Priority: P2
Component: Catalina
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ----
Prior to Tomcat 8.5.15 if the Content-Type request header specifies an invalid
charset then the HttpServletRequest.getReader() throws a
UnsupportedEncodingException (from its javadoc:it should throw such an
exception if the character set encoding used is not supported and the text
cannot be decoded).
However, in Tomcat 8.5.15 with change
https://github.com/apache/tomcat85/commit/18e70aff0fd3e9195d2bf01e445c49ea9fd44d0b
this exception is silently ignored (in
org.apache.coyote.Request.getCharsetFromContentType() ) and then the default
charset is used (in
org.apache.catalina.connector.InputBuffer.checkConverter()).
According to Servlet 3.1 specification, section 3.11, the default charset
should be used if the client does not specify a charset in the request.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
