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.
Pin wildcard hostnames
See original GitHub issueFirst of all thank you for breathing life back into the ModernHttpClient. I have a question regarding defining hostnames for pins.
The current implementation seems to only accept complete hostnames like: test-example.com
We have several subdomains/enviornments for our app and I would like to pin them all using a single Pin entry. For example: dev.test-example.com, prod1.test-example.com, prod2.test-example.com.
The app should be able to deal with new sub-domains without us having to add a new certificate pin and rebuild. It would be totally cool to be able to pin something like *.test-example.com.
Is this possible with your current implementation or is it planned as a future enhancement?
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (5 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
It will be out today.
HA, I can easily do it. Expect a new version later today.