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

Koji Sekiguchi resolved SOLR-1489.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 4.0
                   3.1

Marking resolved as duplicate of SOLR-2381.

> A UTF-8 character is output twice (Bug in Jetty)
> ------------------------------------------------
>
>                 Key: SOLR-1489
>                 URL: https://issues.apache.org/jira/browse/SOLR-1489
>             Project: Solr
>          Issue Type: Bug
>         Environment: Jetty-6.1.3
> Jetty-6.1.21
> Jetty-7.0.0RC6
>            Reporter: Jun Ohtani
>            Assignee: Koji Sekiguchi
>            Priority: Critical
>             Fix For: 3.1, 4.0
>
>         Attachments: SOLR-1489.patch, error_utf8-example.xml, 
> jetty-6.1.22.jar, jetty-util-6.1.22.jar, jettybugsample.war, jsp-2.1.zip, 
> servlet-api-2.5-20081211.jar
>
>
> A UTF-8 character is output twice under particular conditions.
> Attach the sample data.(error_utf8-example.xml)
> Registered only sample data, click the following URL.
> http://localhost:8983/solr/select?q=*%3A*&version=2.2&start=0&rows=10&omitHeader=true&fl=attr_json&wt=json
> Sample data is only "B", but response is "BB".
> When wt=phps, error occurs in PHP unsrialize() function.
> This bug is like a bug in Jetty.
> jettybugsample.war is the simplest one to reproduce the problem.
> Copy example/webapps, and start Jetty server, and click the following URL.
> http://localhost:8983/jettybugsample/filter/hoge
> Like earlier, B is output twice. Sysout only B once.
> I have tested this on Jetty 6.1.3 and 6.1.21, 7.0.0rc6.
> (When testing with 6.1.21or 7.0.0rc6, change "bufsize" from 128 to 512 in 
> web.xml. )

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to