You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/application-gateway/application-gateway-diagnostics.md
+11-11Lines changed: 11 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ services: application-gateway
6
6
author: greg-lindsay
7
7
ms.service: application-gateway
8
8
ms.topic: article
9
-
ms.date: 11/18/2023
9
+
ms.date: 01/10/2024
10
10
ms.author: greglin
11
11
---
12
12
@@ -26,7 +26,7 @@ You can use different types of logs in Azure to manage and troubleshoot applicat
26
26
***Firewall log**: You can use this log to view the requests that are logged through either detection or prevention mode of an application gateway that is configured with the web application firewall. Firewall logs are collected every 60 seconds.
27
27
28
28
> [!NOTE]
29
-
> Logs are available only for resources deployed in the Azure Resource Manager deployment model. You cannot use logs for resources in the classic deployment model. For a better understanding of the two models, see the [Understanding Resource Manager deployment and classic deployment](../azure-resource-manager/management/deployment-models.md) article.
29
+
> Logs are available only for resources deployed in the Azure Resource Manager deployment model. You can't use logs for resources in the classic deployment model. For a better understanding of the two models, see the [Understanding Resource Manager deployment and classic deployment](../azure-resource-manager/management/deployment-models.md) article.
30
30
31
31
## Storage locations
32
32
@@ -187,8 +187,8 @@ The access log is generated only if you've enabled it on each Application Gatewa
187
187
|sentBytes| Size of packet sent, in bytes.|
188
188
|timeTaken| Length of time (in milliseconds) that it takes for a request to be processed and its response to be sent. This is calculated as the interval from the time when Application Gateway receives the first byte of an HTTP request to the time when the response send operation finishes. It's important to note that the Time-Taken field usually includes the time that the request and response packets are traveling over the network. |
189
189
|sslEnabled| Whether communication to the backend pools used TLS/SSL. Valid values are on and off.|
190
-
|host| The hostname with which the request has been sent to the backend server. If backend hostname is being overridden, this name reflects that.|
191
-
|originalHost| The hostname with which the request was received by the Application Gateway from the client.|
190
+
|host| The hostname for which the request has been sent to the backend server. If backend hostname is being overridden, this name reflects that.|
191
+
|originalHost| The hostname for which the request was received by the Application Gateway from the client.|
192
192
193
193
```json
194
194
{
@@ -216,17 +216,17 @@ The access log is generated only if you've enabled it on each Application Gatewa
216
216
}
217
217
```
218
218
### Error code Information
219
-
If the application gateway cannot complete the request, it stores one of the following reason codes in the error_info field of the access log.
219
+
If the application gateway can't complete the request, it stores one of the following reason codes in the error_info field of the access log.
220
220
221
221
222
-
|4XX Errors |The 4xx error codes indicate that there was an issue with the client's request, and the server cannot fulfil it |
222
+
|4XX Errors |The 4xx error codes indicate that there was an issue with the client's request, and the server can't fulfill it |
223
223
|---------|---------|
224
-
| ERRORINFO_INVALID_METHOD| The client has sent a request which is non-RFC compliant. Possible reasons: client using HTTP method not supported by server, misspelled method, incompatible HTTP protocol version etc.|
225
-
| ERRORINFO_INVALID_REQUEST | The server cannot fulfill the request because of incorrect syntax.|
224
+
| ERRORINFO_INVALID_METHOD| The client has sent a request which is non-RFC compliant. Possible reasons: client using HTTP method not supported by server, misspelled method, incompatible HTTP protocol version etc.|
225
+
| ERRORINFO_INVALID_REQUEST | The server can't fulfill the request because of incorrect syntax.|
226
226
| ERRORINFO_INVALID_VERSION| The application gateway received a request with an invalid or unsupported HTTP version.|
227
227
| ERRORINFO_INVALID_09_METHOD| The client sent request with HTTP Protocol version 0.9.|
228
-
| ERRORINFO_INVALID_HOST |The value provided in the "Host" header is either missing, improperly formatted, or does not match the expected host value (when there is no Basic listener, and none of the hostnames of Multisite listeners match with the host).|
229
-
| ERRORINFO_INVALID_CONTENT_LENGTH | The length of the content specified by the client in the content-Length header does not match the actual length of the content in the request.|
228
+
| ERRORINFO_INVALID_HOST |The value provided in the "Host" header is either missing, improperly formatted, or doesn't match the expected host value (when there is no Basic listener, and none of the hostnames of Multisite listeners match with the host).|
229
+
| ERRORINFO_INVALID_CONTENT_LENGTH | The length of the content specified by the client in the content-Length header doesn't match the actual length of the content in the request.|
230
230
| ERRORINFO_INVALID_METHOD_TRACE | The client sent HTTP TRACE method which is not supported by the application gateway.|
231
231
| ERRORINFO_CLIENT_CLOSED_REQUEST | The client closed the connection with the application gateway before the idle timeout period elapsed.Check whether the client timeout period is greater than the [idle timeout period](./application-gateway-faq.yml#what-are-the-settings-for-keep-alive-timeout-and-tcp-idle-timeout) for the application gateway.|
232
232
| ERRORINFO_REQUEST_URI_INVALID |Indicates issue with the Uniform Resource Identifier (URI) provided in the client's request. |
@@ -238,7 +238,7 @@ If the application gateway cannot complete the request, it stores one of the fol
238
238
|5XX Errors |Description |
239
239
|---------|---------|
240
240
| ERRORINFO_UPSTREAM_NO_LIVE | The application gateway is unable to find any active or reachable backend servers to handle incoming requests |
241
-
| ERRORINFO_UPSTREAM_CLOSED_CONNECTION | The backend server closed the connection unexpectedly or before the request was fully processed .This could happen due to backend server reaching its limits ,crashing etc.|
241
+
| ERRORINFO_UPSTREAM_CLOSED_CONNECTION | The backend server closed the connection unexpectedly or before the request was fully processed. This could happen due to backend server reaching its limits, crashing etc.|
242
242
| ERRORINFO_UPSTREAM_TIMED_OUT | The established TCP connection with the server was closed as the connection took longer than the configured timeout value. |
0 commit comments