Skip to content
This repository was archived by the owner on Sep 2, 2025. It is now read-only.

Commit 65e074b

Browse files
author
ada
committed
Updated wording
1 parent b8e3705 commit 65e074b

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

synthetics/browser-test/set-up-browser-test.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -458,13 +458,13 @@ To set a cookie, a key and value must be provided. A domain and path may optiona
458458

459459
Host overrides
460460
---------------------------------------
461-
Add host override rules to reroute requests from one host to another. For example, you can create a host override to test an existing production site against page resources loaded from a development site or a specific CDN edge node.
461+
Add host override rules to reroute requests from one host to another. For example, you can create a host override to test an existing production site against page resources loaded from a development site or from a specific CDN edge node.
462462

463-
You can also indicate whether to retain the original HOST header by activating :strong:`Keep host headers`. If activated, the original request's headers remain intact (recommended). If deactivated, a change in the HOST header to the new host might occur, potentially leading to an internal direct (307). :strong:`Keep host headers` is activated by default.
463+
You can also indicate whether to retain the original ``HOST`` header by activating :strong:`Keep host headers`. If activated, the original request's headers remain intact (recommended). If deactivated, a change in the ``HOST`` header to the new host might occur, potentially leading to an internal direct (307). :strong:`Keep host headers` is activated by default.
464464

465465

466466
.. note::
467-
Host overrides apply only to the exact hostname specified. They don't automatically apply to subdomains. If you need to override subdomains, you must create a separate host override for each fully qualified domain name (FQDN). In other words, if you create a host override for ``google.com`` to ``mygoogle.com``, requests to ``google.com`` are redirected to ``mygoogle.com``. If you also want to redirect requests to ``mail.google.com`` to ``mail.mygoogle.com`` you must do this explicitly by creating a separate host override for ``mail.mygoogle.com``.
467+
Host overrides apply only to the exact hostname you specify. They don't automatically apply to subdomains. In other words, host overrides don't support wildcards. If you need to override any subdomains, you must create a separate host override for each subdomain's fully qualified domain name (FQDN). For example, if you create a host override for ``domainA.com`` to ``domainB.com``, requests to ``domainA.com`` are redirected to ``domainB.com``, but requests to ``mail.domainA.com`` are not automatically redirected to ``mail.domainB.com``. You must explicitly create a separate host override for ``mail.domainA.com``.
468468

469469

470470
.. _browser-wait-times:

0 commit comments

Comments
 (0)