Insecure is still using port 443 and https naming convention
Vad1mo opened this issue · 1 comments
Vad1mo commented
#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.
travisgroth commented