Open jmunozro opened 3 years ago
@jmunozro please add current workaround
Current workaround: deploying a simple socat-based proxy that just forwards a different port to 443 as a workaround, so I can use a different port number in Gloo
This issue has been marked as stale because of no activity in the last 180 days. It will be closed in the next 180 days unless it is tagged "no stalebot" or other activity occurs.
Is your feature request related to a problem? Please describe. A requirement we saw in customers is the possibility to use gloo as a transparent proxy, meaning the traffic will be just opaque. One practical case to avoid having to inspect TLS at all. TLS will be performed end-to-end, but shouldn't require Gloo's involvement.
Describe the solution you'd like
useTLS
should not be forced true for port 443, that should be a default setting not an obligationAdditional context