UTF-8 encoding problem with servlet and apache HttpClient

Question

I have a servlet that sends a string with utf-8 encoding. Also I have a client written with apache httpcomponents library.

My problem is reading the response in utf-8. Some special characters like ñ or ç are not read correctly. If I test the server with an html page sending a request, the string is correct and the encoding is UTF-8 without BOM.

Some snippets: Servlet

response.setContentType ("application/json; charset=UTF-8");
PrintWriter out = response.getWriter ();
out.write (string);

Client

entity = response.getEntity ();
entity.getContentEncoding (); //returns null
resultado = EntityUtils.toString (entity, HTTP.UTF_8); //Some characters are wrong

Has anyone had the same problem?

SOLVED: Sorry guys the client and server were working correctly. I'm writting an android app and it seems that the logcat (where I print the messages) doesn't support utf-8 encoding.

Thomas · Accepted Answer · 2010-12-14 22:23:38Z

7

Have you tried

response.setCharacterEncoding("utf-8");

instead of setting the encoding via setContentType? It shouldn't make a difference according to the documentation, but who knows...

Also, make sure you didn't call response.getWriter() anywhere in your code before setting the character encoding, because the latter would not have any effect in that case.

edited Dec 14, 2010 at 22:23

answered Dec 14, 2010 at 22:18

Thomas

17.5k4 gold badges49 silver badges74 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

Thomas Over a year ago

Can you identify whether the problem is on the servlet side or on the client side?

Hiro2k Over a year ago

Yeah you should check it out with something like Wireshark.

Gabriel Llamas Over a year ago

I've also tested the connection with wireshark and I've seen that the special characters are sended incorrectly, but firefox shows it correctly :S. Tested with setCharacterEncoding and text/plain content-type but still fails.

Miklos Krivan Over a year ago

You are right there was no any differences adding or not adding response.setCharacterEncoding("utf-8") after setting contentType with charset information. But when I changed the position of calling response.getWriter() immediately worked perfect. Many thanks.

Perception · Accepted Answer · 2012-06-07 11:12:31Z

5

Make sure stream bytes are in UTF-8 format:

out.write((yourstring.getBytes("UTF-8"));

edited Jun 7, 2012 at 11:12

Perception

80.8k19 gold badges190 silver badges197 bronze badges

answered Jun 7, 2012 at 6:04

mohammed irfan tirupattur

611 silver badge4 bronze badges

Comments

Jin · Accepted Answer · 2017-10-04 08:22:58Z

5

StandardCharsets.UTF_8 can be used with EntityUtil to get the proper encoding.

Here is a sample snippet:

HttpEntity entity = response.getEntity();
String webpage = EntityUtils.toString(entity, StandardCharsets.UTF_8);

answered Oct 4, 2017 at 8:22

Jin

1012 silver badges7 bronze badges

Comments

Ali Karaca · Accepted Answer · 2019-10-01 10:13:14Z

1

I've got a similar problem that i solved by using UTF-8 encoding as following:

IOUtils.toString(response.getEntity().getContent(), Charsets.UTF_8)

Namespace:

import com.google.common.base.Charsets;

answered Oct 1, 2019 at 10:13

Ali Karaca

3,9611 gold badge38 silver badges43 bronze badges

Collectives™ on Stack Overflow

UTF-8 encoding problem with servlet and apache HttpClient

4 Answers 4

4 Comments

Comments

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

4 Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related