[
https://issues.apache.org/jira/browse/SOLR-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12618260#action_12618260
]
Lars Kotthoff commented on SOLR-632:
------------------------------------
The only workaround is to disable the test :)
Switching to 6.1.11 means that for anybody using Solr with something that does
HTTP caching error messages might be cached. In practice it's probably not a
big deal, as most caching configurations don't cache non-200 responses anyway.
This could have a negative impact if the cache is instructed to store
everything that doesn't explicitely allow caching and the time content is
cached is very long or an error occurs only for a short time and more or less
fixes itself.
> Upgrade bundled Jetty with latest from vendor
> ---------------------------------------------
>
> Key: SOLR-632
> URL: https://issues.apache.org/jira/browse/SOLR-632
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 1.3
> Reporter: Norberto Meijome
> Assignee: Erik Hatcher
> Priority: Minor
> Fix For: 1.3
>
> Original Estimate: 0.25h
> Remaining Estimate: 0.25h
>
> The Jetty that is bundled for the example application is version 6.1.3, which
> is over a year old.
> We should upgrade Jetty to the latest, 6.1.11.
> I am not sure how to attach a patch to remove files, so these are the steps :
> Using as base the root of 'apache-solr-nightly':
> DELETE:
> example/lib/jetty-6.1.3.jar
> example/lib/jetty-util-6.1.3.jar
> example/lib/servlet-api-2.5-6.1.3.jar
> ADD
> example/lib/jetty-6.1.11.jar
> example/lib/jetty-util-6.1.11.jar
> example/lib/servlet-api-2.5-6.1.11.jar
> ---
> The files to be added can be found in Jetty's binary distribution file :
> http://dist.codehaus.org/jetty/jetty-6.1.11/jetty-6.1.11.zip
> I couldn't find any noticeable changes in jetty.xml that should be carried
> over.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
