docker-https-proxy
docker-https-proxy copied to clipboard
phase2
Handles HTTPS proxying with automatic self-signed certs for SSL termination.
'build' can be specified either as a string containing a path to the build context. Specify the 'image' instead when start the container from image.
I think that's what you meant. Build only works if the project has been downloaded.
Not sure if this project has been abandoned? I've made a fork here: https://github.com/RTC1/docker-https-proxy Added AltName support so the generated certs work in Chrome
Would it be possible to change X-Forwarded-Port to an environment var instead of statically set to 443? I run multiple docker instances and usually have them on non-standard ports. Thanks,
## Goal In order to proxy URLs that encode key parameter details as part of the domain, we need better built-in support for multiple domains or wildcard domains. ## Environment...
https://blog.cloudflare.com/deprecating-old-tls-versions-on-cloudflare-dashboard-and-api/ These are old versions of TLS and deprecated for good security reasons. Let's drop support to support forward looking practices by default.