Skip to content

Commit 999f300

Browse files
authored
Merge pull request #3248 from ahardin-rh/host-name-typo
Fixed host name spelling
2 parents 098fabf + 0785fd5 commit 999f300

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

architecture/core_concepts/routes.adoc

+6-6
Original file line numberDiff line numberDiff line change
@@ -328,11 +328,11 @@ routes with different path fields are defined in the same namespace,
328328
those paths are added. If multiple routes with the same path are
329329
used, the oldest takes priority.
330330

331-
A consequence of this behavior is that if you have two routes for a hostname: an
332-
older one and a newer one. If someone else has a route for the same hostname
331+
A consequence of this behavior is that if you have two routes for a host name: an
332+
older one and a newer one. If someone else has a route for the same host name
333333
that they created between when you created the other two routes, then if you
334-
delete your older route, your claim to the hostname will no longer be in effect.
335-
The other namespace now claims the hostname and your claim is lost.
334+
delete your older route, your claim to the host name will no longer be in effect.
335+
The other namespace now claims the host name and your claim is lost.
336336

337337
.A Route with a Specified Host:
338338
====
@@ -438,7 +438,7 @@ below].
438438
== Path Based Routes
439439
Path based routes specify a path component that can be compared against
440440
a URL (which requires that the traffic for the route be HTTP based) such
441-
that multiple routes can be served using the same hostname, each with a
441+
that multiple routes can be served using the same host name, each with a
442442
different path. Routers should match routes based on the most specific
443443
path to the least; however, this depends on the router implementation. The
444444
following table shows example routes and their accessibility:
@@ -499,7 +499,7 @@ TLS termination in {product-title} relies on
499499
link:https://en.wikipedia.org/wiki/Server_Name_Indication[SNI] for serving
500500
custom certificates. Any non-SNI traffic received on port 443 is handled with
501501
TLS termination and a default certificate (which may not match the requested
502-
hostname, resulting in validation errors).
502+
host name, resulting in validation errors).
503503
====
504504

505505
Secured routes can use any of the following three types of secure TLS

0 commit comments

Comments
 (0)