On 07/07/17 09:38, Lazar Kirchev wrote:
> Thanks Mark,
>
> Here is the issue: https://bz.apache.org/bugzilla/show_bug.cgi?id=61264
Thanks.
Mark
>
> Lazar
>
> On Fri, Jul 7, 2017 at 11:22 AM, Mark Thomas wrote:
>
>> On 07/07/17 08:44, Lazar Kirchev wrote:
>>> Hello,
>>>
>>> Prior to Tomcat
Thanks Mark,
Here is the issue: https://bz.apache.org/bugzilla/show_bug.cgi?id=61264
Lazar
On Fri, Jul 7, 2017 at 11:22 AM, Mark Thomas wrote:
> On 07/07/17 08:44, Lazar Kirchev wrote:
> > Hello,
> >
> > Prior to Tomcat 8.5.15 if the Content-Type request header specifies an
> > invalid charset
On 07/07/17 08:44, Lazar Kirchev wrote:
> Hello,
>
> 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
Hello,
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 b
