Java REST Chunked Encoding

Question

I'm trying to read some information with a REST-Service that uses chunk-encoding.

String encodedURL = URLEncoder.encode(url, "UTF-8");
WebClient client = org.apache.cxf.jaxrs.client.WebClient.create(encodedURL).accept("text/html");
Response response = client.get();

The response contains a status, metadata and the entity. The metadata contains the following information:

{Date=[Thu, 13 Oct 2011 13:27:02 GMT], Vary=[Accept-Encoding, User-Agent], Transfer-Encoding=[chunked], Keep-Alive=[timeout=15, max=100], Content-Type=[text/html; charset=charset=UTF-8], Connection=[Keep-Alive], X-Pad=[avoid browser bug], Server=[Apache/2.2.3 (Linux/SUSE)]}

and the entity contains an instance of the type sun.net.www.protocol.http.HttpURLConnection$HttpInputStream.

I the past, I've been using the following line of of code, to get the entire result string:

String resultString = client.get(String.class);

But somehow, this line throws an exception:

.Problem with reading the response message, class : class java.lang.String, ContentType : text/html;charset=charset=UTF-8. org.apache.cxf.jaxrs.client.ClientWebApplicationException: .Problem with reading the response message, class : class java.lang.String, ContentType : text/html;charset=charset=UTF-8.

... caused by:

Caused by: java.io.UnsupportedEncodingException: charset=UTF-8 at sun.nio.cs.StreamDecoder.forInputStreamReader(Unknown Source) at java.io.InputStreamReader.(Unknown Source) at org.apache.cxf.helpers.IOUtils.toString(IOUtils.java:180) at org.apache.cxf.helpers.IOUtils.toString(IOUtils.java:166) at org.apache.cxf.jaxrs.provider.PrimitiveTextProvider.readFrom(PrimitiveTextProvider.java:51) at org.apache.cxf.jaxrs.client.AbstractClient.readBody(AbstractClient.java:435) ... 49 more

Is there a straightforward solution to the get the entire content of the response?

Thank you!

kon

Brad Larson · Accepted Answer · 2012-10-15 02:45:19Z

2

You can use

@Produces("application/json; charset=UTF-8")

annotations for the jax-rs services

edited Oct 15, 2012 at 2:45

Brad Larson

170k45 gold badges401 silver badges574 bronze badges

answered Sep 20, 2012 at 21:49

user1687299

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

Comments

Codo · Accepted Answer · 2011-10-13 13:35:02Z

1

I'm afraid that the server side sends garbage and causes the exception to be thrown on the client side.

The problematic piece is the Content-type HTTP header information. It is set to:

text/html; charset=charset=UTF-8

As you can see, the word charset is repeated. Thus, your client tries to decode it using an encoding called charset=UTF-8, which of course doesn't exist.

The best solution would be if the problem was fixed on the server side. But I don't know if you can get it fixed there. If not, the next best approach is to tried to fix the HTTP header before you try to get the response contents.

answered Oct 13, 2011 at 13:35

Codo

79.7k18 gold badges176 silver badges218 bronze badges

1 Comment

kon Over a year ago

Thank you Codo! I somehow missed this completely.

Collectives™ on Stack Overflow

Java REST Chunked Encoding

2 Answers 2

Comments

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related