[
https://issues.apache.org/jira/browse/SOLR-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491746
]
Ken Krugler commented on SOLR-214:
----------------------------------
There's some complex interplay of the content-type in the request, the charset
(if any) in the request, and the container being used. So some interesting
questions are:
# exactly how the content is being posted (e.g. via the example script?)
# what request header values are being sent along with the post.
# what servlet container (and version) is being used.
> deficit of InputStreamReader support in anonymous class of ContentStream
> ------------------------------------------------------------------------
>
> Key: SOLR-214
> URL: https://issues.apache.org/jira/browse/SOLR-214
> Project: Solr
> Issue Type: Bug
> Reporter: Koji Sekiguchi
> Attachments: UseInputStreamReader.patch
>
>
> After SOLR-197 is applied, POSTed Japanese XML contents turn into garbled
> characters in the index.
> I can see the garbled characters through Luke. The issue was never seen
> before SOLR-197.
> The cause of this problem is that the deficit of InputStreamReader support in
> the anonymous class of ContentStream in
> SolrRequestParsers.parseParamsAndFillStreams() method.
> Before SOLR-197, InputStreamReader was used in
> XmlUpdateRequestHandler.handleRequestBody() method:
> // Cycle through each stream
> for( ContentStream stream : req.getContentStreams() ) {
> String charset = getCharsetFromContentType( stream.getContentType() );
> Reader reader = null;
> if( charset == null ) {
> reader = new InputStreamReader( stream.getStream() );
> }
> else {
> reader = new InputStreamReader( stream.getStream(), charset );
> }
> rsp.add( "update", this.update( reader ) );
>
> // Make sure its closed
> try { reader.close(); } catch( Exception ex ){}
> }
> The patch will apply this effect to SolrRequestParsers.
> regards,
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
