Here you will find a list of common library problems and possible solutions to overcome them.
This is the most common exception that the library might throw. More specific exceptions will extend from this one.
This happens whenever the HTTP adapter being used throws an Http\Client\Exception.
There might be several reasons for it, so pay attention to the actual message.
Most of the time, cURL is being used under the hood, so here's a list of common errors that might happen.
This error happens when libcURL tries to use a protocol it doesn't have support for. Either because the SSL/TLS library doesn't support it (GnuTLS), or simply because it was disabled at build time by the vendor (Ubuntu).
In the majority of cases, it's because CURL_SSLVERSION_SSLv2 is being set, or even CURL_SSLVERSION_DEFAULT (which may default to the former), but it should always be confirmed from the error message.
Try using CURL_SSLVERSION_SSLv3 instead.
For more information about the security protocols supported by libcURL, refer to the SSL library comparison list
This is the error when the protocol handshake fails. The error message will most likely be the following:
Unknown SSL protocol error in connection to accounts.accesscontrol.windows.net:443
If CURL_SSLVERSION_SSLv2 or CURL_SSLVERSION_SSLv3 are being used, try using CURL_SSLVERSION_TLSv1_0 instead.
Note that CURL_SSLVERSION_TLSv1_0 is only available since PHP 5.5.19/5.6.3 and cURL 7.34.
The error message associated with this error code might be:
GnuTLS recv error (-9): A TLS packet with unexpected length was received.
This happens when libcURL is built against GnuTLS and the fact that this library is more strict when dealing with the TLS protocol.
There's an explanation about it in the GnuTLS mailing list:
Several sites terminate the TLS connection without following the TLS protocol (i.e. sending closure alerts), but rather terminate the TCP connection directly. This is a relic of SSLv2 and it seems other implementations ignore this error. GnuTLS doesn't and thus prints this error.
Given that this is a mix of SharePoint not following the TLS protocol correctly and GnuTLS being strict about it, there's not much that can be done except for using a different PHP/libcURL version.
If other cURL errors emerge, check the libcURL error list to help find the root cause.
This issue occurs when folder/file operations like move or copy use long file or folder names.
Read more about SharePoint URL length limitations here.
This usually happens when using App-only Policy without the AllowAppOnlyPolicy attribute being set to true in the AppPermissionRequests node.
More information about the SharePoint hosted app manifest configuration can be found here.