Repository navigation
Releases: gggeek/phpxmlrpc
Release list
Fixed: compatibility with php 7.2 for legacy api
This release makes the legacy api of the library compatible with php 7.2 by removing one more deprecation warning.
Fixed: compatibility with php 7.2 for old branch
This release makes the library compatible with php 7.2 by removing one more deprecation warning.
NB moving to version 4 of the library is the recommended option unless you absolutely can not upgrade, as it comes with many improvements and is fully API compatible with version 3.
Fixed: compatibility with php 7.2 for old branch
This release makes the library compatible with php 7.2 by removing the deprecation warnings.
NB moving to version 4 of the library is the recommended option unless you absolutely can not upgrade, as it comes with many improvements and is fully API compatible with version 3.
Minor fixes
-
fixed: error when using https in non-curl mode
-
fixed: compatibility of tests with php 7.2
-
fixed: html injection in sample code
-
fixed: warnings emitted by the legacy server in xmlrpcs.inc
-
fixed: encoding of php variables of type 'resource' when using xmlrpc_encode in php-compatibility mode
-
fixed: bad html tag in sample code
-
improved: text of error messages
one fix, one new feature
-
fixed: compatibility with Basic/Digest/NTLM auth when using client in cURL mode (issue #58)
-
improved: added unit tests for Basic and Digest http auth. Also improved tests suite
-
improved: support for doing https calls without resorting to cURL
-
new: allow to force usage of curl for http 1.0 calls, as well as plain socket for https calls, via the method
Client::setUseCurl()
Fixed: compatibility with Lighttpd as target server with client in curl mode and biggish requests
4.2.2 Docs
Fixed: compatibility with php 7.2
4.2.1 Fix last commit
Make old version of the library compatible with php 7
This release makes the library compatible with php 7 by removing the deprecation warnings.
NB moving to version 4 of the library is the recommended option unless you absolutely can not upgrade, as it comes with many improvements.
The only other changes are:
- addition of a 'setSSLVersion' method to the client class
- updates to the test suite
Allow DateTimeImmutable objects be detected as date when encoding
Only a small improvement his time around
Fix one bug in the server class
Bug only triggered when not using the compatibility shim with old versions