You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@shindig.apache.org by "John Hjelmstad (JIRA)" <ji...@apache.org> on 2010/07/27 23:02:16 UTC

[jira] Resolved: (SHINDIG-1395) MutableContent causing lossy content encoding

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

John Hjelmstad resolved SHINDIG-1395.
-------------------------------------

    Resolution: Fixed

Committed http://codereview.appspot.com/1903045/show, resolving this issue. Thanks!

> MutableContent causing lossy content encoding
> ---------------------------------------------
>
>                 Key: SHINDIG-1395
>                 URL: https://issues.apache.org/jira/browse/SHINDIG-1395
>             Project: Shindig
>          Issue Type: Bug
>          Components: Java
>            Reporter: Gagandeep Singh
>            Assignee: Gagandeep Singh
>            Priority: Critical
>
> MutableContent.getRawContentBytes and MutableContent.getContent are buggy because they serialize the Document into a utf8 string disregarding the original encoding of the page that is known to the HttpResponse object.
> Here is how it goes wrong for accel servlet:
> AccelServlet.doFetch ->
> DefaulltResponseRewriterRegistry.rewriteHttpResponse ->
> HttpResponseBUilder.create ->
> new HttpResponse ->
> HttpResponseBuilder.getResponse ->
> MutableContent.getRawContentBytes()
> NOTE: This could also be  problem with gadgets. Need to verify.

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