Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of dmikusa@pivotal.io designates
 74.125.82.181 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <SNT148-W32BC3C8203715984A62CD8B0C40@phx.gbl>
References: <SNT148-W32BC3C8203715984A62CD8B0C40@phx.gbl>
Date: Wed, 3 Sep 2014 08:27:08 -0400
Message-ID: 
 <CAAqVxAxOqO=_1xOd6RYq2n3XVKzPS734PMqzayzYCudD8oBrjg@mail.gmail.com>
Subject: Re: UTF-8 encoded request URI
From: Daniel Mikusa <dmikusa@pivotal.io>
To: Tomcat Users List <users@tomcat.apache.org>
Content-Type: multipart/alternative; boundary=bcaec53d57afc9a77f0502285af1

--bcaec53d57afc9a77f0502285af1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Wed, Sep 3, 2014 at 7:45 AM, Lulseged Zerfu <zlulseged@hotmail.com>
wrote:

> Hi  I am getting bad request from tomcat when I send UTF-8 encoded reques=
t
> to my application.


Can you give an example of the request?  Are the non-ascii characters in
the URL or in the payload of your request (or both)?


> I have configured connector in my server.xml with URIEncoding=3D=E2=80=9D=
UTF-8=E2=80=9D.


Not necessary with Tomcat 8.  The default for URIEncoding is "UTF-8".
 Unless you have set the system
property org.apache.catalina.STRICT_SERVLET_COMPLIANCE=3Dtrue.  That will
override the URIEncoding and set it to "ISO-8859-1".

I have set charset in the request to UTF-8. How can I solve 400 Bad
> request? How can I tell tomcat to decode request URI instead of respondin=
g
> with 400 Bad request?


You seem certain that the 400 error is due to the encoding.  Perhaps it's
something else?  What have you done to troubleshoot this?  Have you tried
stepping through things with a debugger?

Dan


> I will appreciate any help.
> I am using tomcat 8.0.11 on windows 8 x64. I have also tried with tomcat
> 7.0.55. BRLulseged

--bcaec53d57afc9a77f0502285af1--