Skip to content

Commit d4284fb

Browse files
authored
Broken link fixed
1 parent ded4e22 commit d4284fb

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/spring-apps/how-to-integrate-azure-load-balancers.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ Azure already provides [different load-balance solutions](/azure/architecture/gu
2828

2929
In the examples below, we will load balance requests for a custom domain of `www.contoso.com` towards two deployments of Azure Spring Apps in two different regions: `eastus.azuremicroservices.io` and `westus.azuremicroservices.io`.
3030

31-
We recommend that the domain name, as seen by the browser, is the same as the host name which the load balancer uses to direct traffic to the Azure Spring Apps back end. This recommendation provides the best experience when using a load balancer to expose applications hosted in Azure Spring Apps. If the domain exposed by the load balancer is different from the domain accepted by Azure Spring Apps, cookies and generated redirect URLs (for example) can be broken. For more information, see [Host name preservation](/azure/architecture/best-practices/host-name-preservation.md).
31+
We recommend that the domain name, as seen by the browser, is the same as the host name which the load balancer uses to direct traffic to the Azure Spring Apps back end. This recommendation provides the best experience when using a load balancer to expose applications hosted in Azure Spring Apps. If the domain exposed by the load balancer is different from the domain accepted by Azure Spring Apps, cookies and generated redirect URLs (for example) can be broken. For more information, see [Host name preservation](/azure/architecture/best-practices/host-name-preservation).
3232

3333
## Prerequisites
3434

@@ -73,7 +73,7 @@ To integrate with Azure Spring Apps service, complete the following configuratio
7373
### Add Custom Probe
7474

7575
1. Select **Health Probes** then **Add** to open custom **Probe** dialog.
76-
1. The key point is to select *No* for **Pick host name from backend HTTP settings** option and explicitly specify the host name. For more information, see [Application Gateway configuration for host name preservation](/azure/architecture/best-practices/host-name-preservation.md#application-gateway).
76+
1. The key point is to select *No* for **Pick host name from backend HTTP settings** option and explicitly specify the host name. For more information, see [Application Gateway configuration for host name preservation](/azure/architecture/best-practices/host-name-preservation#application-gateway).
7777

7878
![App Gateway 2](media/spring-cloud-load-balancers/app-gateway-2.png)
7979

@@ -96,7 +96,7 @@ To integrate with Azure Spring Apps service and configure an origin group, use t
9696

9797
1. Specify **origin type** as *Azure Spring Apps*.
9898
1. Select your Azure Spring Apps instance for the **host name**.
99-
1. Keep the **origin host header** empty, so that the incoming host header will be used towards the backend. For more information, see [Azure Front Door configuration for host name preservation](/azure/architecture/best-practices/host-name-preservation.md#azure-front-door).
99+
1. Keep the **origin host header** empty, so that the incoming host header will be used towards the backend. For more information, see [Azure Front Door configuration for host name preservation](/azure/architecture/best-practices/host-name-preservation#azure-front-door).
100100

101101
![Front Door 2](media/spring-cloud-load-balancers/front-door-2.png)
102102

0 commit comments

Comments
 (0)