Skip to content

[enterprise-3.9] Add note for path-based routes. #9013

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

Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 8 additions & 2 deletions architecture/networking/routes.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -303,8 +303,13 @@ Path based routes specify a path component that can be compared against
a URL (which requires that the traffic for the route be HTTP based) such
that multiple routes can be served using the same host name, each with a
different path. Routers should match routes based on the most specific
path to the least; however, this depends on the router implementation. The
following table shows example routes and their accessibility:
path to the least; however, this depends on the router implementation.
The host name and path are passed through to the backend server so it should be
able to successfully answer requests for them.
For example: a request to http://example.com/foo/ that goes to the router will
result in a pod seeing a request to http://example.com/foo/.

The following table shows example routes and their accessibility:

.Route Availability
[cols="3*", options="header"]
Expand Down Expand Up @@ -351,6 +356,7 @@ the router does not terminate TLS in that case and cannot read the contents
of the request.
====


[[secured-routes]]
== Secured Routes
Secured routes specify the TLS termination of the route and, optionally,
Expand Down