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
+18-18Lines changed: 18 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -118,7 +118,7 @@ The access log is generated only if you've enabled it on each Application Gatewa
118
118
|requestUri| This field contains the URL after the rewrite operation on Application Gateway |
119
119
|upstreamSourcePort| The source port used by Application Gateway when initiating a connection to the backend target|
120
120
|originalHost| This field contains the original request host name|
121
-
|error_info|The reason for the 4xx and 5xx error. If the request failed, one of the error codes described in [Error Info codes](./application-gateway-diagnostics.md#error-info-codes) is stored in this field of access log|
121
+
|error_info|The reason for the 4xx and 5xx error. Displays an error code for a failed request. More details in [Error code information.](./application-gateway-diagnostics.md#error-info-codes) |
122
122
|contentType|The type of content or data that is being processed or delivered by the application gateway
123
123
124
124
@@ -161,9 +161,9 @@ The access log is generated only if you've enabled it on each Application Gatewa
161
161
"serverResponseLatency": "0.028",
162
162
"upstreamSourcePort": "21564",
163
163
"originalHost": "20.110.30.194",
164
-
"host": "20.110.30.194"
165
-
"error_info":"ERRORINFO_NO_ERROR"
166
-
"contentType":"application/json"
164
+
"host": "20.110.30.194",
165
+
"error_info":"ERRORINFO_NO_ERROR",
166
+
"contentType":"application/json"
167
167
}
168
168
}
169
169
```
@@ -215,30 +215,30 @@ The access log is generated only if you've enabled it on each Application Gatewa
215
215
}
216
216
}
217
217
```
218
-
### Error info codes
218
+
### Error code Information
219
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.
220
220
221
221
222
-
|4XX Errors |Description |
222
+
|4XX Errors |The 4xx error codes indicate that there was an issue with the client's request, and the server cannot fulfil it|
223
223
|---------|---------|
224
-
| ERRORINFO_INVALID_METHOD| The client has sent a request using an HTTP method that is not recognized or supported by the server Possible reasons : client using HTTP method not supported by server, Misspelled Method , incompatible HTTP protocol version etc|
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
225
| ERRORINFO_INVALID_REQUEST | The server cannot fulfill the request because of incorrect syntax.|
226
-
| ERRORINFO_INVALID_VERSION| The application gateway received a request with an invalid or unsupported HTTP version|
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.Possible reasons: There is no Basic listener configured and none of the hostnames of the Multisite listener is matching 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|
230
-
| ERRORINFO_INVALID_METHOD_TRACE | The client sent HTTP TRACE method which is not supported by the application gateway|
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
-
| ERRORINFO_REQUEST_URI_INVALID |Indicates issue with the Uniform Resource Identifier (URI) provided in the client's request |
233
-
| ERRORINFO_HTTP_NO_HOST_HEADER | Client sent a request without Host header |
234
-
| ERRORINFO_HTTP_TO_HTTPS_PORT |The client sent plain HTTP request to HTTPS port |
235
-
| ERRORINFO_HTTPS_NO_CERT | Indicates client is not sending a valid and properly configured SSL certificate during MTLS Authentication|
226
+
| ERRORINFO_INVALID_VERSION| The application gateway received a request with an invalid or unsupported HTTP version.|
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.|
230
+
| ERRORINFO_INVALID_METHOD_TRACE | The client sent HTTP TRACE method which is not supported by the application gateway.|
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
+
| ERRORINFO_REQUEST_URI_INVALID |Indicates issue with the Uniform Resource Identifier (URI) provided in the client's request.|
233
+
| ERRORINFO_HTTP_NO_HOST_HEADER | Client sent a request without Host header.|
234
+
| ERRORINFO_HTTP_TO_HTTPS_PORT |The client sent a plain HTTP request to an HTTPS port.|
235
+
| ERRORINFO_HTTPS_NO_CERT | Indicates client is not sending a valid and properly configured TLS certificate during Mutual TLS authentication. |
236
236
237
237
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 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