[WINK-262] Content-Type of HTTP Response contains no charset.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0
• Fix Version/s: 1.1
• Component/s: Server
• Labels: charset missing

Environment

Jetty Server 6.1

• Assignee: Michael Rheinheimer
• Reporter: Kaloyan Kolev
• Created: 05/Mar/10 12:00
• Updated: 13/Jul/13 20:13
• Resolved: 30/Mar/10 03:46

Description

I have the following handler:

import javax.ws.rs.GET;
import javax.ws.rs.Path;
import javax.ws.rs.Produces;
import javax.ws.rs.core.Context;
import javax.ws.rs.core.MediaType;
import javax.ws.rs.core.Request;
import javax.ws.rs.core.Response;

import org.apache.wink.common.model.atom.AtomEntry;
import org.apache.wink.common.model.atom.AtomText;

@Path("contentType")
public class ContentTypeTest {
	@GET
	@Produces( { MediaType.APPLICATION_XML, MediaType.TEXT_XML, MediaType.APPLICATION_JSON, "text/javascript" })
	public Response getRepresentation(@Context Request req) {
		AtomEntry e = new AtomEntry();
		e.setTitle(new AtomText(
				"\u5341\u5341\u5341\u5341\u5341\u5341\u5341\u5341\u5341\u5341\u5341\u5341\u4e00\u69cb\u30bd\u30c1\u2010"));
		return Response.ok(e).build();
	}
}

When I open the resource I get the following HTTP response:

Content-Type:	application/xml
Content-Length:	274
Server:	Jetty(6.1.x)

You can see that the charset is not specified and the content is not properly decoded e.g. by RestClient - http://code.google.com/p/rest-client/

However I can see that the XML is properly encoded by opening the resource in FF and enforcing UTF-8 decoding.

Shouldn't wink put the encoding used during serialization if different than ASCII?