Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maintenance/docs #446

Merged
merged 16 commits into from
Nov 27, 2023
Prev Previous commit
Next Next commit
Fix list rendering
Reformat the list to work on docs.kuadrant.io
  • Loading branch information
Boomatang committed Nov 10, 2023
commit 2529f35810deeb5e97e38fbd9ef8cd5fb5b63de7
3 changes: 3 additions & 0 deletions docs/user-guides/host-override.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,7 @@ Overriding the host attribute of the HTTP request can be useful to support use c
<br/>

In this guide:

- [Example of host override for path prefix-based lookup](#example-of-host-override-for-path-prefix-based-lookup)
- [Example of host override for wildcard subdomain lookup](#example-of-host-override-for-wildcard-subdomain-lookup)

Expand All @@ -26,6 +27,7 @@ In this guide:
## Example of host override for path prefix-based lookup

In this use case, 2 different APIs (i.e. **Dogs API** and **Cats API**) are served under the same base domain, and differentiated by the path prefix:

- `pets.com/dogs` → Dogs API
- `pets.com/cats` → Cats API

Expand Down Expand Up @@ -91,6 +93,7 @@ Notice that the host subdomains `dogs.pets.com` and `cats.pets.com` are not real
## Example of host override for wildcard subdomain lookup

In this use case, a single **Pets API** serves requests for any subdomain that matches `*.pets.com`, e.g.:

- `dogs.pets.com` → Pets API
- `cats.pets.com` → Pets API

Expand Down