Pass-through request options

[tlvince]

Firstly, thanks for easysoap. It's a particularly useful lighter alternative to node-soap in cases where you only need a client.

The soap server I'm using uses HTTPs without a valid certificate (beyond my control). It also expects the SOAPAction header to be set per request, which although is currently supported, such headers are also included in the Soap envelope itself (via getRequestHeadParams), which is causing unexpected behaviour.

Since rejectUnauthorized is already being handled manually, generalising this handle any params would be useful.

[moszeed]

Hi, thanks for the nice words.

Yes, my Roadmap is to remove this rejectUnauthorized from the request.js and let users pass options directly to the request module.

But currently, there is no time for this, i`m open for Pull Requests.

[ozette]

Does this mean there is currently no way to specify for example secureProtocol to enforce a specific tls protocol version? In my use case I added secureProtocol: "method" option manually to the source code i.e. soapcall's request({ .. }) declaration.