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

Erlend Garåsen commented on CONNECTORS-1564:
--------------------------------------------

[~michael-o], do you have time to give me a hint on how I can build Apache from 
trunk? I have compiled it many times before, but never from trunk. I'm 
struggling with the following error when I try to compile apr (inside 
`srclib/apr`):

{{configure: error: No XML parser found!  Please specify --with-expat or 
--with-libxml2}}

`libxml2-devel-2.9.1-6.el7_2.3.x86_64` and `libxml2-2.9.1-6.el7_2.3.x86_64` are 
already installed.

I have found those libraries inside the `/usr/lib64` folder, but I get the same 
error when I try to use the `--with-libxml2` option. The same error shows up if 
I try to run the HTTPd's configure script.

My plan is to place a new `mod_proxy_http.so` file in my modules folder. If 
trunk is not compatible with Apache 2.4, then I will try to start the compiled 
Apache version and configure it similarly as the one we are using today.

> Support preemptive authentication to Solr connector
> ---------------------------------------------------
>
>                 Key: CONNECTORS-1564
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-1564
>             Project: ManifoldCF
>          Issue Type: Improvement
>          Components: Lucene/SOLR connector
>            Reporter: Erlend Garåsen
>            Assignee: Karl Wright
>            Priority: Major
>         Attachments: CONNECTORS-1564.patch
>
>
> We should post preemptively in case the Solr server requires basic 
> authentication. This will make the communication between ManifoldCF and Solr 
> much more effective instead of the following:
>  * Send a HTTP POST request to Solr
>  * Solr sends a 401 response
>  * Send the same request, but with a "{{Authorization: Basic}}" header
> With preemptive authentication, we can send the header in the first request.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to