Sourced from phpxmlrpc/phpxmlrpc's releases.

4.10.0

• changed: the minimum php version required has been increased to 5.4

• changed: dropped support for parsing cookie headers which follow the obsolete Cookie2 specification

• new: it is now possible to make the library generate warning messages whenever a deprecated feature is used, such as calling deprecated methods, using deprecated method parameters, or reading/writing deprecated object properties. This is disabled by default, and can be enabled by setting PhpXmlRpc\PhpXmlRpc::xmlrpc_silence_deprecations = false. Note that the deprecation warnings will be by default added to the php error log, and not be displayed on screen. If you prefer them to be handled in some other way, you should take over the Logger, as described below here

• new: allow to specify other charsets than the canonical three (UTF-8, ISO-8859-1, ASCII), when mbstring is available, both for outgoing and incoming data (issue #42).

  For outgoing data, this can be set in $client->request_charset_encoding and $server->response_charset_encoding. The library will then transcode the data fed to it by the application into the desired charset when serializing it for transmission.

  For incoming data, this can be set using PhpXmlRpc::$internal_encoding. The library will then transcode the data received from 3rd parties into the desired charset when handling it back to the application.

  An example of using this feature has been added to demo file windowscharset.php

• new: allow the library to pass to the application DateTime objects instead of string for all received dateTime.iso8601 xml-rpc values. This includes both client-side, for data within the $response->value(), and server-side, for data passed to xml-rpc method handlers, and works for both 'xmlrpcvals' and 'phpvals' modes. In order to enable this, you should set PhpXmlRpc\PhpXmlRpc::$xmlrpc_return_datetimes = true.

  NB: since the xml-rpc spec mandates that no Timezone is used on the wire for dateTime values, the DateTime objects created by the library will be set to the default php timezone, set using the 'date.timezone' ini setting.

  NB: if the received strings are not parseable as dates, NULL will be returned instead of an object, but that can be avoided by setting PhpXmlRpc\PhpXmlRpc::$xmlrpc_reject_invalid_values = true, see below.

• improved: be more strict in the Response constructor and in Request::addParam: both of those will now generate an error message in the log if passed unexpected values

• improved: be more strict in the data accepted as valid for dateTime xml-rpc values. Clearly invalid dates such as a month '13', day '32' or hour '25' will cause an error message to be logged or the value to be rejected, depending on configuration

• improved: be more strict in the data accepted as valid for 'float' and 'int' xml-rpc values. If you need to allow different formats for numbers, you can set a custom value to PhpXmlRpc\PhpXmlRpc::$xmlrpc_double_format and PhpXmlRpc\PhpXmlRpc::$xmlrpc_int_format

• new: allow the library to be stricter in parsing the received xml: by setting PhpXmlRpc\PhpXmlRpc::$xmlrpc_reject_invalid_values = true, incoming xml which has data not conforming to the expected format for value elements of type date, int, float, double, base64 and methodname will be rejected instead of passed on to the application. The same will apply for elements of type struct-member which miss either the name or the value

... (truncated)

• 7103864 fix doc gen task
• 28398f1 tag for release
• 957adb0 add cmd to set up git hook
• 1149eec improve api docs
• e7bfce1 docs
• 1a1b0dd test fixes
• 135d8af fix test container build for newer images/docker
• 047008a improve test docker container build
• acae578 test fixes
• 3e447bc test fixes
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)