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

Erlend GarĂ¥sen commented on CONNECTORS-661:
-------------------------------------------


Maybe I'm reading the lines incorrectly, but isn't the first the request and 
the latter the response?

{code}
> <xml/>HTTP/1.1 100 Continue
HTTP/1.1 100 Continue

< HTTP/1.1 401 Unauthorized
HTTP/1.1 401 Unauthorized
{code}

So do we really have two status codes in the response?

{quote}
As far as MCF is concerned - I'm leery of fixing problems in the wrong place in 
order to work around somebody else's bugs. I think the proper course of action 
is to see if you can find a solution on your end - perhaps with a patched 
version of Resin. But absolutely a ticket should be created against Resin, or 
this will not get addressed.
{quote}

I agree. I will try to reproduce this by using a newer version of Resin on my 
laptop without Apache/mod_caucho in order to figure out whether this is a Resin 
bug. If it is, I will open a ticket.
                
> Solr Connector cannot index documents when Solr is protected by authentication
> ------------------------------------------------------------------------------
>
>                 Key: CONNECTORS-661
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-661
>             Project: ManifoldCF
>          Issue Type: Bug
>          Components: Lucene/SOLR connector
>    Affects Versions: ManifoldCF 1.1.1
>            Reporter: Karl Wright
>            Assignee: Karl Wright
>            Priority: Critical
>             Fix For: ManifoldCF 1.2
>
>
> The Solr connector cannot deal with Solr servers that are protected by 
> authentication.  The reason is that HttpClient forces a retry based on the 
> WWW-authenticate header that is returned, but the HttpEntity is not 
> resettable and thus the retry fails for that reason.
> This is a regression, because the Solr connector used to properly support 
> basic auth, and now no longer does.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to