| Previous | Next |
| HTTP_STATUS_HTTP_TO_HTTPS_PORT | HTTP_STATUS_TOKEN_REQUIRED |
HTTP_STATUS_INVALID_TOKEN
ArcGIS uses 498 when a token was present but cannot authorize the request. It is distinct from ArcGIS 499, where the token is absent.
Refresh or reacquire the token through the supported authentication flow, then verify its scope, issuer, expiration, and audience. Do not log the token itself while diagnosing the response.
Operational meaning of HTTP 498 for HTTP_STATUS_INVALID_TOKEN
HTTP 498 (HTTP_STATUS_INVALID_TOKEN) is a client-error response. AllStat records its meaning as “498 Invalid Token”. For HTTP_STATUS_INVALID_TOKEN, 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_INVALID_TOKEN
- Treat HTTP_STATUS_INVALID_TOKEN as a condition visible at the request boundary; inspect authentication, syntax, preconditions, routing, and resource state before retrying.
- For HTTP_STATUS_INVALID_TOKEN, preserve the response body and challenge or retry-related headers because they often carry the actionable reason.
- For HTTP_STATUS_INVALID_TOKEN, automatic retry is safe only when the method and status contract allow it and the request has been corrected.
For telemetry, record HTTP 498, 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.