Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Contentful (axios) throws: TypeError [ERR_INVALID_PROTOCOL]: Protocol "https:" not supported. Expected "http:"
See original GitHub issueEnvironment
| Name | Version |
|---|---|
| msw | 0.39.0 |
| node | v16.13.0 |
| OS | Windows 10 |
Request handlers
See a complete reproducible repo here. Just npm i and then node app.js.
Current behavior
Mocking a minimal get request to Contentful’s readonly API causes msw/NodeClientRequest.Client request to throw:
TypeError [ERR_INVALID_PROTOCOL]: Protocol "https:" not supported. Expected "http:"
…akin to previous issues, but something new must be going on here. Under the hood Contentful uses axios, which might shed some light on the cause. If I revert back to 0.36.8 this issue does not happen (but has its own set of issues).
Expected behavior
For msw to intercept the request successfully and return a mocked response.
Screenshots
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Just for other peoples’ future reference. This was a matter of passing node’s
https.Agent()to the Contentful client paramhttpsAgentduring instantiation. Thanks for your help @kettanaito.🎉 This issue has been resolved in version 0.39.1 🎉
The release is available on:
Your semantic-release bot 📦🚀