Closed line-o closed 11 months ago
@duncdrum I just re-read the section explaining the REST endpoint and agree that it should include a section how to configure that connection - by hand - and also point out that the options returned from readOptionsFromEnv
can be used there, too.
@duncdrum your demand to better document connection options lead to a serious quality of life improvement :)
:tada: This PR is included in version 5.5.0 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
Features
aligned connection options allows to use the same options for both APIs, REST and XML-RPC
The legacy option
{ secure: true|false }
will now work for both APIs as setting the protocol does.{ protocol: "https:"|"http:" }
is now the preferred way to switch between encrypted and unencrypted connections and works for both APIs.Fixes
REST connection options read from environment can override default protocol (
https:
)Documentation
clarify connection options and usage - fixes #240