[ https://issues.apache.org/jira/browse/SLING-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571015#action_12571015 ]
Bertrand Delacretaz commented on SLING-263: ------------------------------------------- You're right Carsten, that "select servlet by content-type" business is old remains from microsling where we used the expected Content-Type of the response to select renderers. Moving to extension-based selection, and letting the servlets set the Content-Type including encoding, makes sense. > json render servlet does not set charset of content type > -------------------------------------------------------- > > Key: SLING-263 > URL: https://issues.apache.org/jira/browse/SLING-263 > Project: Sling > Issue Type: Bug > Components: Launchpad > Reporter: Tobias Bocanegra > Assignee: Felix Meschberger > > the launchpad JsonRenderServlet uses incomplete response content type not > specifying the charset. > Index: > launchpad/launchpad-servlets/src/main/java/org/apache/sling/launchpad/servlets/LaunchpadDefaultServlet.java > =================================================================== > --- > launchpad/launchpad-servlets/src/main/java/org/apache/sling/launchpad/servlets/LaunchpadDefaultServlet.java > (revision 629192) > +++ > launchpad/launchpad-servlets/src/main/java/org/apache/sling/launchpad/servlets/LaunchpadDefaultServlet.java > (working copy) > @@ -94,7 +94,7 @@ > > getServlets = new HashMap<String, Servlet>(); > getServlets.put("html", new DefaultHtmlRendererServlet("text/html")); > - getServlets.put("json", new JsonRendererServlet("application/json")); > + getServlets.put("json", new JsonRendererServlet("application/json; > charset=utf-8")); > getServlets.put("txt", defaultGetServlet); > getServlets.put("res", streamServlet); > } -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.