You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Lewis John McGibbney (JIRA)" <ji...@apache.org> on 2013/01/12 21:04:12 UTC

[jira] [Resolved] (NUTCH-910) Cached.jsp has a bug with encoding

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

Lewis John McGibbney resolved NUTCH-910.
----------------------------------------

    Resolution: Won't Fix

this is a legacy issue so we won't be fixing it.
                
> Cached.jsp has a bug with encoding
> ----------------------------------
>
>                 Key: NUTCH-910
>                 URL: https://issues.apache.org/jira/browse/NUTCH-910
>             Project: Nutch
>          Issue Type: Bug
>          Components: web gui
>    Affects Versions: 1.0.0
>         Environment: Any enironment
>            Reporter: Attila Pados
>            Priority: Minor
>   Original Estimate: 2m
>  Remaining Estimate: 2m
>
> cached.jsp
> Pages that has a non default encoding, or not utf-8 etc, the cached content is displayed screwed. This is quite annoying, but doesn't harm critically functionality.
> add       :   Metadata parseData = bean.getParseData(details).getParseMeta();
> original :  Metadata metaData = bean.getParseData(details).getContentMeta();
> replace: String encoding = (String) parseData.get("CharEncodingForConversion");
> In the cached jsp, the encoding variable is tried to retrieved from the wrong metadata source, contentMeta, which doesn't include this value.
> It resides in the parseMetadata instead. 
> First line is not a replacement above, it has to be added.  Original metadata is needed there for other things.
> Then below, the encoding value line has to be changed, that is a replacement.
> This fix is for 1.0 nutch version, i didn't found an issue in the list that would cover this, just a mail found with google, on a mailing list that refered to it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira