lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Høydahl (JIRA) <j...@apache.org>
Subject [jira] [Commented] (SOLR-8887) Solr Security features cannot export the internal, deprecated DefaultHttpClient class as part of their user facing API.
Date Mon, 21 Nov 2016 10:03:59 GMT

    [ https://issues.apache.org/jira/browse/SOLR-8887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15683077#comment-15683077
] 

Jan Høydahl commented on SOLR-8887:
-----------------------------------

Looks like this issue can be closed as a duplicate then?

> Solr Security features cannot export the internal, deprecated DefaultHttpClient class
as part of their user facing API.
> -----------------------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-8887
>                 URL: https://issues.apache.org/jira/browse/SOLR-8887
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Mark Miller
>            Priority: Critical
>             Fix For: 6.0
>
>
> Seems security now really depends on HttpClientConfigurer. That class was only used for
tests previously, and was at best completely unsupported. We can't promise an API that locks
us into an internal, low level, class from a lib. Especially a deprecated one. Solr wants
to own the http layer, not get locked into impls.
> We need to stop using DefaultHttpClient, and it's going to break this stuff.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message