Skip to content

Commit be23b06

Browse files
authored
Update monitor-application-gateway-reference.md
1 parent f0ab992 commit be23b06

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/application-gateway/monitor-application-gateway-reference.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Monitoring data reference for Azure Application Gateway
33
description: This article contains important reference material you need when you monitor Azure Application Gateway.
4-
ms.date: 10/15/2024
4+
ms.date: 03/28/2025
55
ms.custom: horz-monitor
66
ms.topic: reference
77
author: greg-lindsay
@@ -330,12 +330,14 @@ If the application gateway can't complete the request, it stores one of the foll
330330
| ERRORINFO_HTTP_NO_HOST_HEADER | Client sent a request without Host header. |
331331
| ERRORINFO_HTTP_TO_HTTPS_PORT | The client sent a plain HTTP request to an HTTPS port. |
332332
| ERRORINFO_HTTPS_NO_CERT | Indicates client isn't sending a valid and properly configured TLS certificate during Mutual TLS authentication. |
333+
| ERRORINFO_INVALID_HEADER | Application Gateway detected a partial invalid header and forwarded the remaining header to the backend, which responded with 200 OK. Ensure the client's request header does not contain CR, LF, NULL, or similar characters. Replace such characters with SP (whitespace). |
333334

334335
| 5XX Errors | Description |
335336
|:-----------|:------------|
336337
| ERRORINFO_UPSTREAM_NO_LIVE | The application gateway is unable to find any active or reachable backend servers to handle incoming requests. |
337338
| ERRORINFO_UPSTREAM_CLOSED_CONNECTION | The backend server closed the connection unexpectedly or before the request was fully processed. This condition could happen due to backend server reaching its limits, crashing etc. |
338339
| ERRORINFO_UPSTREAM_TIMED_OUT | The established TCP connection with the server was closed as the connection took longer than the configured timeout value. |
340+
| ERRORINFO_INVALID_HEADER | Application Gateway detected a partial invalid header and forwarded the remaining header to the backend, which responded with 200 OK. Ensure the client's request header does not contain CR, LF, NULL, or similar characters. Replace such characters with SP (whitespace). |
339341

340342
### Firewall log category
341343

0 commit comments

Comments
 (0)