Hi Noel,
How the Solr connector processes 403 responses is also a SolrJ (client
library) consideration. I vaguely recall fixing something in this area not
too long ago but I can't locate it.
Karl
On Thu, Apr 7, 2016 at 10:59 AM, Devenney, Noel <
noel.deven...@fmr.com.invalid> wrote:
> Hi
Hi Karl,
Well, it's not untrue to say Solr are providing an authorisation check, it
seems to me that the Solr exceptions thrown end up buried somehow in Manifold
code? I'm not exactly sure how because I do see code to handle them but they're
not being caught when Solr returns authorisation
[
https://issues.apache.org/jira/browse/CONNECTORS-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Wright updated CONNECTORS-1286:
Component/s: (was: Solr-5.x component)
Solr 6.x component
> Solr
Hi Noel,
I appreciate the effort in reaching out to the Solr team.
As you know, MCF can only use what Solr provides to check connection
status. If there is no check we can do that verifies authorization, then
obviously I can't reflect authorization problems in the status.
Please let us know
Hi Karl, thanks for your response.
The version of ManifoldCF we're using is 2.1 and the Solr version is 4.10.3.
The ping request is being used and the authentication credentials are being
used along with it, but it seems to me that the /ping endpoint normally doesn't
require authentication. We
