-
Notifications
You must be signed in to change notification settings - Fork 164
Closed
Labels
backendIssues related to the platform backend.Issues related to the platform backend.good first issueGood for newcomers.Good for newcomers.low priorityLow priority issues to be done eventually.Low priority issues to be done eventually.t-core-servicesIssues with this label are in the ownership of the core services team.Issues with this label are in the ownership of the core services team.validatedIssues that are resolved and their solutions fulfill the acceptance criteria.Issues that are resolved and their solutions fulfill the acceptance criteria.
Description
We recently added a new option ignoreProxyCertificate. We should add tests covering it.
How to do it (roughly):
- Run a plain Node.js HTTP server that would just return
Hello world. - Use e.g. https://www.npmjs.com/package/local-ssl-proxy to wrap the server with a self-signed SSL certificate.
- Run a
proxy-chainserver that would point to the HTTPS endpoint created in 2. - Send a normal request via the
proxy-chainproxy. - If
ignoreProxyCertificateis set totrue, you should getHello world, otherwise you'll get a SSL error about being unable to verify the leaf signature.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
backendIssues related to the platform backend.Issues related to the platform backend.good first issueGood for newcomers.Good for newcomers.low priorityLow priority issues to be done eventually.Low priority issues to be done eventually.t-core-servicesIssues with this label are in the ownership of the core services team.Issues with this label are in the ownership of the core services team.validatedIssues that are resolved and their solutions fulfill the acceptance criteria.Issues that are resolved and their solutions fulfill the acceptance criteria.