Actually, it's the same issue (and even error stack) reported here:

http://tomcat.10.x6.nabble.com/Tomcat-8-5-4-uses-RFC-6265-by-default-which-does-not-appear-to-be-Servlet-3-1-compliant-td5054685.html



On 13 November 2017 at 09:00, Mark Thomas <ma...@apache.org> wrote:

> On 12/11/17 22:25, M. Manna wrote:
> > Hi,
> >
> > We are currently encountering an issue where some of our REST  API calls
> > are failing because of a white-space not being encoded (i.e. %20). This
> has
> > started with 8.5.16 and our previous version didn't have this problem -
> > 8.0.29.
> >
> > Is this something anyone has seen before? I am assuming that it's RFC
> 6265
> > where whitespace is not allowed? But is there any work around?
>
> You are going to need to be more specific about the problem. You need to
> provide enough information for someone else to reproduce the issue and
> investigate it.
>
> Mark
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Reply via email to