[CONNECTORS-777] SharePoint 2010 does not always qualify FileRef fields with proper relative paths

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: ManifoldCF 1.3
• Fix Version/s: ManifoldCF 1.4
• Component/s: SharePoint connector
• Assignee: Karl Wright
• Reporter: Karl Wright
• Created: 17/Sep/13 11:47
• Updated: 18/Sep/13 20:43
• Resolved: 18/Sep/13 20:43

Description

We're seeing instances where SharePoint 2010 (on AWS) does not qualify file references with the expected base-relative URL. For example:

DEBUG 2013-09-16 13:02:31,590 (Worker thread '23') - SharePoint: getListItems xml response: '<GetListItems xmlns="http://schemas.microsoft.com/sharepoint/soap/directory/"><GetListItemsResponse xmlns=""><GetListItemsResult FileRef="SitePages/Home.aspx"/></GetListItemsResponse></GetListItems>'
DEBUG 2013-09-16 13:02:31,590 (Worker thread '23') - SharePoint: Checking whether to include document '/SitePages/Home.aspx'
DEBUG 2013-09-16 13:02:31,590 (Worker thread '23') - SharePoint: File '/SitePages/Home.aspx' exactly matched rule path '/*'
DEBUG 2013-09-16 13:02:31,590 (Worker thread '23') - SharePoint: Including file '/SitePages/Home.aspx'
 WARN 2013-09-16 13:02:31,590 (Worker thread '23') - Sharepoint: Unexpected relPath structure; path is '/SitePages/Home.aspx', but expected <list/library> length of 26

Here, the fact that the FileRef does not start with a "/" may indicate that it should be treated as being relative to the current library URL. But without more data (and multiple installations) it will be hard to fully test this assumption.