@@ -86,14 +86,6 @@ include::architecture/topics/sticky_sessions.adoc[]
86
86
[[env-variables]]
87
87
include::architecture/topics/router_environment_variables.adoc[]
88
88
89
- [[time-units]]
90
- == Timeouts
91
- `TimeUnits` are represented by a number followed by the unit: `us`
92
- *(microseconds), `ms` (milliseconds, default), `s` (seconds), `m` (minutes), `h`
93
- *(hours), `d` (days).
94
-
95
- The regular expression is: [1-9][0-9]*(us\|ms\|s\|m\|h\|d)
96
-
97
89
[[load-balancing]]
98
90
== Load-balancing Strategy
99
91
@@ -303,9 +295,9 @@ Path based routes specify a path component that can be compared against
303
295
a URL (which requires that the traffic for the route be HTTP based) such
304
296
that multiple routes can be served using the same host name, each with a
305
297
different path. Routers should match routes based on the most specific
306
- path to the least; however, this depends on the router implementation.
298
+ path to the least; however, this depends on the router implementation.
307
299
The host name and path are passed through to the backend server so it should be
308
- able to successfully answer requests for them.
300
+ able to successfully answer requests for them.
309
301
For example: a request to http://example.com/foo/ that goes to the router will
310
302
result in a pod seeing a request to http://example.com/foo/.
311
303
@@ -851,7 +843,7 @@ This controller watches ingress objects and creates one or more routes to
851
843
satisfy the conditions of the ingress object. The controller is also responsible
852
844
for keeping the ingress object and generated route objects synchronized. This
853
845
includes giving generated routes permissions on the secrets associated with the
854
- ingress object.
846
+ ingress object.
855
847
856
848
For example, an ingress object configured as:
857
849
0 commit comments