| Previous | Next |
| HTTP_STATUS_INVALID_TOKEN | HTTP_STATUS_CLIENT_CLOSED_REQUEST |
HTTP_STATUS_TOKEN_REQUIRED
ArcGIS documents 499 separately from NGINX 499: here it means that the request reached an ArcGIS service which requires a token but did not receive one. The same numeric code has different meanings across products.
Obtain a valid token through the supported ArcGIS authentication flow and send it using the method documented for that service. Check token scope, expiration, and whether the operation requires additional privileges.
Operational meaning of HTTP 499 for HTTP_STATUS_TOKEN_REQUIRED
HTTP 499 (HTTP_STATUS_TOKEN_REQUIRED) is a client-error response. AllStat records its meaning as “499 Token Required”. For HTTP_STATUS_TOKEN_REQUIRED, interpret it with the request method, selected representation, response headers, and the specification or product that defines the code; the number alone does not prove that application work completed.
Client and server handling for HTTP_STATUS_TOKEN_REQUIRED
- Treat HTTP_STATUS_TOKEN_REQUIRED as a condition visible at the request boundary; inspect authentication, syntax, preconditions, routing, and resource state before retrying.
- For HTTP_STATUS_TOKEN_REQUIRED, preserve the response body and challenge or retry-related headers because they often carry the actionable reason.
- For HTTP_STATUS_TOKEN_REQUIRED, automatic retry is safe only when the method and status contract allow it and the request has been corrected.
For HTTP_STATUS_TOKEN_REQUIRED, for telemetry, record HTTP 499, method, authority, route template rather than secrets, response headers relevant to caching or retry, latency, upstream identity, and whether the response originated at the application or an intermediary.
Looking for a different code? Search another status or error code.