From 5b3f89219ee0b24f05d2c6a6e9dbfd32a2d66793 Mon Sep 17 00:00:00 2001 From: Craig Brookes Date: Tue, 12 Dec 2023 11:23:01 +0000 Subject: [PATCH] Update doc/user-guides/secure-protect-connect.md Co-authored-by: Jason Madigan <4467+jasonmadigan@users.noreply.github.com> --- doc/user-guides/secure-protect-connect.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/user-guides/secure-protect-connect.md b/doc/user-guides/secure-protect-connect.md index 23f23e9f3..c0f89efea 100644 --- a/doc/user-guides/secure-protect-connect.md +++ b/doc/user-guides/secure-protect-connect.md @@ -139,7 +139,7 @@ EOF With this HTTPRoute in place the service we deployed later is exposed via the gateway. We should be able to access our endpoint via HTTPS: ``` -curl -k --resolve api.${KUADRANT_ZONE_ROOT_DOMAIN}:443:172.18.200.1 "https://api.$KUADRANT_ZONE_ROOT_DOMAIN/cars" +curl -k --resolve api.${KUADRANT_ZONE_ROOT_DOMAIN}:443:${INGRESS_HOST} "https://api.$KUADRANT_ZONE_ROOT_DOMAIN/cars" ```