lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] Commented: (SOLR-2381) The included jetty server does not support UTF-8
Date Wed, 09 Mar 2011 13:20:59 GMT


Robert Muir commented on SOLR-2381:

bq. Quickest fix would be to use the working code snippet from jetty-7.3.1 and replace the
buggy jetty-6.1.26-patched-JETTY-1340.

There's nothing quick about fixing bugs in jetty at all: for example the 6.1 branch's unit
test suite does not even reliably pass out of box, making it difficult to test changes.

I'm certainly going to fix it, but its going to take probably a day of my time to ensure that
its done safely (just like it took a day for me to fix the previous jetty bug on this issue).

Unfortunately, as we are switching from FAST System to Solr, all our Interfaces are using
We never had any problems with FAST, XML and UTF-8. 
It would be a mess reworking everything to JSON just for Solr.

I'm not really concerned at all with what FAST does or doesn't do.

I still stand by my statement that I strongly recommend against the use of XML (in general,
nothing to do with Jetty) if you need correct unicode support and are using java-based components.
This is just my practical advice based on building applications that have to work with all
of unicode.

You won't be reworking just for Solr, its pretty likely as your system grows you will run
into other unicode bugs in java-based XML libraries, too.

> The included jetty server does not support UTF-8
> ------------------------------------------------
>                 Key: SOLR-2381
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Robert Muir
>            Assignee: Robert Muir
>            Priority: Blocker
>             Fix For: 3.1, 4.0
>         Attachments: SOLR-2381.patch, SOLR-2381_xmltest.patch, SOLR-ServletOutputWriter.patch,
jetty-6.1.26-patched-JETTY-1340.jar, jetty-util-6.1.26-patched-JETTY-1340.jar,,
> Some background here:
> Some possible solutions:
> * wait and see if we get resolution on To
be honest, I am not even sure where jetty is being maintained (there is a separate jetty project
at with another bugtracker, but the older releases are at codehaus).
> * include a patched version of jetty with correct utf-8, using that patch.
> * remove jetty and include a different container instead.

This message is automatically generated by JIRA.
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message