Hmm, tested with OS 1.4.1:
Route "https" is invalid: spec.tls.insecureEdgeTerminationPolicy: Invalid
value: "Redirect": InsecureEdgeTerminationPolicy is only allowed for
edge-terminated routes
but the doc (
https://docs.openshift.com/container-platform/3.4/architecture/core_concepts/routes.html)
On Wed, Apr 19, 2017 at 2:35 PM, Clayton Coleman
wrote:
> 1.4 added the ability to specify insecureEdgeTerminationPolicy for
> passthrough
Good, thanks :)
___
users mailing list
users@lists.openshift.redhat.com
1.4 added the ability to specify insecureEdgeTerminationPolicy for
passthrough.
On Wed, Apr 19, 2017 at 2:31 PM, Philippe Lafoucrière <
philippe.lafoucri...@tech-angels.com> wrote:
> Hi,
>
> It seem impossible to register a route with both "passthrough" tls
> termination and standard http.
> The
Hi,
It seem impossible to register a route with both "passthrough" tls
termination and standard http.
The "insecure" route is being rejected because the https route already
exposes the same host.
Is there a reason for that?
I'm using passthrough because the underlying service has its own ssl