[
https://issues.apache.org/jira/browse/SHINDIG-1220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thiago Arrais updated SHINDIG-1220:
-----------------------------------
Attachment: fix-guessing-charset.patch
I assumed that when not otherwise specified, the code should assume that the
response text is already UTF-8 encoded. The trunk code was getting lost because
the $charset variable was being fed into the preg_match function and rewritten.
> Charset guessing code in BasicRemoteContentFetcher gets lost when no charset
> is informed
> ----------------------------------------------------------------------------------------
>
> Key: SHINDIG-1220
> URL: https://issues.apache.org/jira/browse/SHINDIG-1220
> Project: Shindig
> Issue Type: Bug
> Components: PHP
> Reporter: Thiago Arrais
> Attachments: fix-guessing-charset.patch
>
>
> The BasicRemoteContentFetcher incorrectly converts content already UTF-8
> encoded when the response headers do not include a charset spec.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
