You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2017/07/07 08:38:12 UTC

[Bug 61264] New: Default charset used when Content-Type request header specifies invalid charset

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: dev@tomcat.apache.org
          Reporter: lazar.kirchev@gmail.com
  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: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


[Bug 61264] Default charset used when Content-Type request header specifies invalid charset

Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=61264

Mark Thomas <ma...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 OS|                            |All
         Resolution|---                         |FIXED

--- Comment #1 from Mark Thomas <ma...@apache.org> ---
Fixed in:
- trunk for 9.0.0.M24 onwards
- 8.5.x for 8.5.18 onwards

Thanks for the report.

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org