[
https://issues.apache.org/jira/browse/SOLR-16504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17631960#comment-17631960
]
David Smiley commented on SOLR-16504:
-------------------------------------
[~janhoy] I thought you might help contribute to this discussion since you
added the HEAD request for authentication. The ultimate point, as I understand
it, was to communicate a helpful message as to the nature of the problem (e.g.
bad credentials). Wouldn't this happen for the "real" request? Separately,
the Http2 client has less support for the authentication carriers than Http1.
I'm not sure how the client picks up the credentials. Jan, have you looked
into the matrix of support of our authentication plugins across our clients?
I'm worried this isn't well tested and we'll introduce a regression. That
point is not _only_ for this issue (the CLI tools) but is an overall concern
for the switch to the Jetty client from Apache.
> Convert CLI tools to Jetty HTTP 2 client.
> -----------------------------------------
>
> Key: SOLR-16504
> URL: https://issues.apache.org/jira/browse/SOLR-16504
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: David Smiley
> Priority: Major
> Labels: newdev
>
> Affected classes: SolrCLI, ExportTool, PackageTool, SolrLogPostTool
> The aforementioned classes are in the org.apache.solr.util package and are
> CLI tools (have a main method, are executed outside the context of a Solr
> server). These should be converted to our non-legacy Solr clients based on
> Jetty HttpClient. (i.e. don't use CloudLegacySolrClient or HttpSolrClient
> which are based on Apache HttpClient).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
