Details
-
Improvement
-
Status: Resolved
-
Critical
-
Resolution: Fixed
-
ManifoldCF 2.12
-
None
-
None
Description
During a job, it may occur, for some reasons (related to the SharePoint server configuration), that some resources of a SP site are not available (for instance if it requires some credentials to open a resource). In that case, the SP connector gets a 403 or a 503 response code from the SharePoint. The problem is that whenever it gets this kind of response code, the job is aborted with an error.
Since the response codes are clearly identified (403 and 503), it would be better that, at least for a 503 error, the connector ignores it, continues the job, and log something into the repo history instead of aborting the job