![]() OCSP Client Revocation check is enabled, but OCSP responder isn't provided in the certificate.įor more information about troubleshooting mutual authentication, see Error code troubleshooting.OCSP Client Revocation check is enabled, but unable to be contacted.OCSP Client Revocation check is enabled and the certificate is revoked.Client certificate chain doesn't match certificate chain configured in the defined SSL Policy.DN validation is enabled and the DN of the client certificate doesn't match the DN of the specified certificate chain. ![]() Client certificate isn't presented, but mutual authentication is enabled.Missing Content Length header for POST requestįor cases when mutual authentication is configured, several scenarios can lead to an HTTP 400 response being returned the client, such as: Header field name and URI contain non-ASCII Character The workaround is to code it as a percentage. Presence of malformed or illegal character Some common reasons for the request to be non-compliant to RFC are: Category Mutual authentication is configured and unable to properly negotiate.HTTP traffic is initiated to a listener with HTTPS, with no redirection configured.Non-HTTP / HTTPS traffic is initiated to an application gateway with an HTTP or HTTPS listener. ![]() HTTP 400 response codes are commonly observed when: Metrics supported by Application Gateway V2 SKU Diagnostic logs 400 – Bad Request See the following articles for more information. For example, CDN and other authentication providers. Clients can also receive 4xx response from other proxies between the client device and Application Gateway. Metrics and logging enable further troubleshooting. These issues can range from the client initiating requests to an unmatched hostname, request timeout, unauthenticated request, malicious request, and more.Īpplication Gateway collects metrics that capture the distribution of 4xx/5xx status codes has a logging mechanism that captures information such as the URI client IP address with the response code. 4XX response codes (client error)Ĥ00-499 response codes indicate an issue that is initiated from the client. HTTP 307 responses are presented when a redirection rule is specified with the Temporary value. HTTP 302 responses are presented when a redirection rule is specified with the See Other value. ![]() HTTP 302 responses are presented when a redirection rule is specified with the Found value. ![]() HTTP 301 responses are presented when a redirection rule is specified with the Permanent value. For more information about redirects, see Application Gateway redirect overview. Redirects can be configured on a rule as-is or via a path map rule. 3XX response codes (redirection)ģ00-399 responses are presented when a client request matches an application gateway rule that has redirects configured. HTTP response codes can be returned to a client request whether or not a connection was initiated to a backend target. Common causes and troubleshooting steps are provided to help you determine the root cause of error HTTP Response code. This article gives reasons on why Azure Application Gateway returns specific HTTP response codes. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |