From 0617a1b0e0163f5d5b6e5932efbf3274dd72a851 Mon Sep 17 00:00:00 2001 From: Nick Reilingh Date: Wed, 16 Mar 2022 10:00:08 -0400 Subject: [PATCH] Fix routing overview examples --- docs/content/routing/overview.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/content/routing/overview.md b/docs/content/routing/overview.md index 3a99fe9e2..59b3e4a8c 100644 --- a/docs/content/routing/overview.md +++ b/docs/content/routing/overview.md @@ -21,7 +21,7 @@ If they do, the router might transform the request using pieces of [middleware]( ## Example with a File Provider -Below is an example of a full configuration file for the [file provider](../providers/file.md) that forwards `http://domain/whoami/` requests to a service reachable on `http://private/whoami-service/`. +Below is an example of a full configuration file for the [file provider](../providers/file.md) that forwards `http://example.com/whoami/` requests to a service reachable on `http://private/whoami-service/`. In the process, Traefik will make sure that the user is authenticated (using the [BasicAuth middleware](../middlewares/http/basicauth.md)). Static configuration: @@ -122,7 +122,7 @@ http: In this example, we've defined routing rules for http requests only. Traefik also supports TCP requests. To add [TCP routers](./routers/index.md) and [TCP services](./services/index.md), declare them in a TCP section like in the following. - ??? example "Adding a TCP route for TLS requests on whoami.example.com" + ??? example "Adding a TCP route for TLS requests on whoami-tcp.example.com" **Static Configuration**