From b48837e5c0f80ad716880c9a9d412e1a3814a264 Mon Sep 17 00:00:00 2001 From: savagebidoof Date: Sun, 30 Apr 2023 22:54:38 +0200 Subject: [PATCH] Small cleanup --- .../02-portLevelMtls/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename {Istio/10-PeerAuthentication => 10-PeerAuthentication}/02-portLevelMtls/README.md (97%) diff --git a/Istio/10-PeerAuthentication/02-portLevelMtls/README.md b/10-PeerAuthentication/02-portLevelMtls/README.md similarity index 97% rename from Istio/10-PeerAuthentication/02-portLevelMtls/README.md rename to 10-PeerAuthentication/02-portLevelMtls/README.md index 0dfb971..aeb0aa2 100644 --- a/Istio/10-PeerAuthentication/02-portLevelMtls/README.md +++ b/10-PeerAuthentication/02-portLevelMtls/README.md @@ -312,7 +312,7 @@ listening on eth0, link-type EN10MB (Ethernet), snapshot length 262144 bytes ##### Curl -Even tho, we have set in the [PeerAuthentication configuration](#peerauthentication) mode to `STRICT`, unlike in the [previous example](../01-disable-mTLS/#https-1), where the mode was also set to `STRICT`, in this example we configured the `portLevelMtls` field for the port `443`, successfully disabling `mTLS` for this port, and allowing to proceed with the request towards the `HTTPS` backend; which was performed without the need of disabling `mTLS` for the whole deployment. +Even tho, we have set in the [PeerAuthentication configuration](#peerauthentication) mode to `STRICT`, unlike in the [previous example](01-disable-mTLS/#https-1), where the mode was also set to `STRICT`, in this example we configured the `portLevelMtls` field for the port `443`, successfully disabling `mTLS` for this port, and allowing to proceed with the request towards the `HTTPS` backend; which was performed without the need of disabling `mTLS` for the whole deployment. ```shell curl 192.168.1.50/https