Support --ssl-no-verify option , for invalid SSL backend certificate

[LasneF]

User Story Description

As a developer,

I want to use prism proxy even with non valid https certificate,

so I can do internal validation testing with my own certificate.

Acceptance Criteria

Given a backend with invalid HTTPS certificate (can be because of expiry, or not able to verify the root certificate)
Given a specific Prism proxy option like -ssl-no-verify

I want that the call be transmitted seamlessly

current behavior

[11:45:34] » [CLI] ►  start     Prism is listening on http://127.0.0.1:4010
[11:45:40] » [HTTP SERVER] get /user i  info      Request received
[11:45:40] »     [PROXY] i  info      > Forwarding "get" request to https://myserver/users
types...
[11:45:40] » [HTTP SERVER] get /party-types ×  error     Request terminated with error: FetchError: request to https://myserver/users  failed, reason: unable to verify the first certificate

[chohmann]

@LasneF this is a reasonable feature request. We would welcome a PR to introduce this new flag. As a potential workaround in the meantime, you could try setting the environment variable NODE_TLS_REJECT_UNAUTHORIZED to 0.

[LasneF]

thanks @chohmann , it could be a feature ... or a tiny comment in the documentation would also make the deal