Support HTTPS
See original GitHub issueCurrently Smocker can work as a http proxy if you try to call an API using http_proxy variable. The call will be redirected to Smocker.
You can test this by:
- starting Smocker:
make start
- making a call using Smocker as http proxy
export http_proxy=http://localhost:8080/
curl -v http://jsonplaceholder.typicode.com/todos/1
Then you should see the call on Smocker.
But when we try to make a call using HTTPS and HTTPS_PROXY, the http client send a CONNECT request on the proxy server which is not handled correctly by Smocker. It will respond to the call with a “No mock found matching the request” which will cancel the https request on client side.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:10 (3 by maintainers)
Top Results From Across the Web
Enabling HTTPS on your servers - web.dev
If you don't already have HTTPS service available on your servers, enable it now (without redirecting HTTP to HTTPS; see below). Configure your ......
Read more >Check if a site's connection is secure - Google Chrome Help
In Chrome, open a web page. To check a site's security, to the left of the web address, check the security status symbol:...
Read more >What is HTTPS? | Cloudflare
HTTPS is a secure way to send data between a web server and a web browser. ... by logging into a bank account,...
Read more >HTTPS - Wikipedia
Hypertext Transfer Protocol Secure (HTTPS) is an extension of the Hypertext Transfer Protocol (HTTP). It is used for secure communication over a computer ......
Read more >What is SSL, TLS and HTTPS? - DigiCert
If not, contact our sales or support teams here. ... HTTPS (Hyper Text Transfer Protocol Secure) appears in the URL when a website...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
we could bundle Smocker with self signed certificates and optionally allow to start it with TLS enabled. If we do this it will be easy to replace the self signed certs with valid certs by just overriding them
Can you write how to test it with mkcert in the readme ? I’m curious about it.