This repository has been archived by the owner on Mar 30, 2023. It is now read-only.
Configure Application Gateway Custom probe #201
Comments
russcam
added a commit
that referenced
this issue
Jul 16, 2018
This commit configures a custom probe for Application Gateway. Custom probes now support status codes other than 200-399, so configure the probe to also consider a 401 response as healthy. This removes the need to configure anonymous access to the cluster base path. Closes #201
russcam
added a commit
that referenced
this issue
Jul 18, 2018
This commit configures a custom probe for Application Gateway. Custom probes now support status codes other than 200-399, so configure the probe to also consider a 401 response as healthy. This removes the need to configure anonymous access to the cluster base path. Looked at condesing both gateway resources into one, but Application Gateway validation does not allow an empty object for webApplicationFirewallConfiguration; it fails validation with error: ApplicationGatewayFirewallCannotBeEnabledForSelectedSku : Application Gateway /subscriptions/<subscription id>/resourceGroups/<resource group>/providers/Microsoft.Network/applicationGateways/es-app-gateway does not support WebApplicationFirewall with the selected SKU tier Standard Closes #201
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Application Gateway custom probes now support the ability to provide multiple HTTP status codes that should be taken as healthy response for the backend pool. Previously, a healthy response was only considered when the response code was in the 200-399 range.
A custom health probe should be configured to allow 401 responses when X-Pack Security is enabled, which would remove the need to allow anonymous access to the base path
/.The text was updated successfully, but these errors were encountered: