You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wink.apache.org by "Nick Gallardo (JIRA)" <ji...@apache.org> on 2010/03/05 15:00:27 UTC

[jira] Updated: (WINK-262) Content-Type of HTTP Response contains no charset.

     [ https://issues.apache.org/jira/browse/WINK-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Gallardo updated WINK-262:
-------------------------------

    Fix Version/s: 1.1

> Content-Type of HTTP Response contains no charset.
> --------------------------------------------------
>
>                 Key: WINK-262
>                 URL: https://issues.apache.org/jira/browse/WINK-262
>             Project: Wink
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 1.0
>         Environment: Jetty Server 6.1
>            Reporter: Kaloyan Kolev
>             Fix For: 1.1
>
>
> I have the following handler:
> {code}
> 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();
> 	}
> }
> {code}
> When I open the resource I get the following HTTP response:
> {code}
> Content-Type:	application/xml
> Content-Length:	274
> Server:	Jetty(6.1.x)
> {code}
> 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?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.