The source for upstream changes is under lcf/upstream-changes/httpclient, not under trunk.
As for the metadata, how are you determining that no metadata is being indexed? If this is Solr you are indexing into, have you set up the appropriate metadata/field mappings? Karl On 9/12/10, Martijn v Groningen <martijn.is.h...@gmail.com> wrote: > To authenticate with Share point I had to include the domain as well. > Also the ui reported an error if I didn't specify the username in a > domain / username format. Maybe this http client issue was just > particular with the Sharepoint / Domain Controller installation I was > working with. I also couldn't find the source of afc version of http > client. Is it hosted in another source repository? > > I still don't understand why for the documents I crawled, I didn't > have any metadata associated with it. In the job configuration I was > able to choose which metadata I wanted to include. You have an idea > what might be the cause of this? > > Regards, > > Martijn > > On 12 September 2010 18:40, Karl Wright <daddy...@gmail.com> wrote: >> Hi Martijn, >> >> The ACF version of httpclient has support for NTLMv1, NTLMv2, and NTLM2 >> protocols. The standard client does not. >> >> What this means practically for you depends on how the Windows domain >> controller you are working with is configured. You cannot use the >> off-the-shelf httpclient and still authenticate if the domain controller >> is >> configured to not allow LM connections, which is what Microsoft recommends >> people do. >> >> Since the ACF version of httpclient will always try to connect using >> NTLMv2, >> this means that you must be more rigorous about setting up your client >> machine. First, it must have a name, and it must have a machine account >> in >> the domain. Second, NTLMv2 is much more picky about how you specify user >> and domain. The end user documentation provides details that may be >> helpful >> to you in this regard. >> >> Thanks, >> Karl >> >> >> On Sun, Sep 12, 2010 at 5:00 AM, Martijn v Groningen >> <martijn.is.h...@gmail.com> wrote: >>> >>> Hi All, >>> >>> I've configured the Sharepoint connector (to connect to sharepoint >>> 3.0), Solr connector and a job that adds documents into Solr. The only >>> thing that I'm missing is the meta data from Sharepoint. Per document >>> I need to know which users can access it. In the metadata tab on the >>> job page I've configured the metadata to be included, but this doesn't >>> end up in my Solr index. Does anybody know what I should do to also >>> have the metadata in my index? >>> >>> I also had another issue with the Sharepoint connector which I managed >>> to solve. But I'm curious to know if someone else encountered a >>> similar issue. >>> When I was setting up the sharepoint connecter I always got a 401 >>> message on the connectors page as status. I was sure I entered the >>> correct credentials. After some debugging I noticed that the NLTM data >>> that was send to Solr was different then when I did a http post with >>> Firefox poster plugin to a Sharepoint webservice url (I check this >>> with Wireshark). After writing a little test case with httpclient used >>> in afc, I got the same 401 error. I then ran the test with a clean >>> http client (version 3.1), that ran as expected. I got a response code >>> 200 back with a soap response. I then used this version of http client >>> (with some class filesfrom the afc provided jar that were missing is >>> the plain jar file) and the connector worked as expected as I was able >>> to index documents. Did someone else have this particular issue? I >>> noticed that acf is using httpclient 3.1 (from the manifest file), but >>> I'm curious to know why http client was modified. >>> >>> BTW I've been using the latest trunk version (I did a checkout last >>> tuesday). I'm also new to Sharepoint >>> >>> Cheers, >>> >>> Martijn >> >> >
