-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Insecure is still using port 443 and https naming convention #88
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#83 introduced insecure.
Unfortunately it is incomplete. For example when using together with Traefik, then Traefik is guessing based on port number 443 and the port (name?) if the service should called plain or over tls.
The setups with HTTP traffic over port 443 confuses Traefik as it assumes by port number & port name that the upstream service is secure which it isn't.
If
insecure=true
change Ports from 443 to 80 and rename port from https to http.The text was updated successfully, but these errors were encountered: