Clarify task wording (#2736)

This commit is contained in:
Frank Budinsky 2018-10-05 12:52:57 -04:00 committed by Martin Taillefer
parent 4fc57a7cc0
commit f6f3b79a75
2 changed files with 3 additions and 2 deletions

View File

@ -226,7 +226,7 @@ Let's see how you can configure a `Gateway` on port 80 for HTTP traffic.
## Accessing ingress services using a browser
Entering the `httpbin` service URL in a browser won't work because you can't tell the browser to pretend to be accessing `httpbin.example.com` like with `curl`. In a real world situation, this is not a problem because because you configure the requested host properly and DNS resolvable. Thus, you use the host's domain name in the URL, for example, `https://httpbin.example.com/status/200`.
Entering the `httpbin` service URL in a browser won't work because you can't tell the browser to pretend to be accessing `httpbin.example.com` like with `curl`. In a real world situation, this is not a problem because you configure the requested host properly and DNS resolvable. Thus, you use the host's domain name in the URL, for example, `https://httpbin.example.com/status/200`.
To work around this problem for simple tests and demos, use a wildcard `*` value for the host in the `Gateway` and `VirtualService` configurations. For example, if you change your ingress configuration to the following:

View File

@ -6,7 +6,8 @@ keywords: [traffic-management,ingress]
---
The [Control Ingress Traffic](/docs/tasks/traffic-management/ingress) task describes how to configure an ingress
gateway to expose an HTTP endpoint of a service to external traffic. This task extends that task to enable HTTPS access to the service using either simple or mutual TLS.
gateway to expose an HTTP endpoint of a service to external traffic.
This task shows you how to do the same, but using HTTPS access to the service with either simple or mutual TLS.
## Before you begin