| Previous | Next |
| HTTP_STATUS_CREATED | HTTP_STATUS_NON_AUTH_INFORMATION |
HTTP_STATUS_ACCEPTED
The server accepted the request, but processing has not completed and might later be rejected or fail. HTTP does not provide a second response on the original connection when asynchronous work finishes.
A useful 202 response provides a status document, job identifier, or monitor URL. Clients should poll or subscribe to that separate status mechanism rather than treat 202 as completion.
Operational meaning of HTTP 202 for HTTP_STATUS_ACCEPTED
HTTP 202 (this result) is a successful response. AllStat records its meaning as “202 Accepted”. 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
- Verify what work the response representation says was completed; this result can still describe asynchronous or partial handling.
- use validators, location/status links, and application identifiers supplied by the server.
- do not retry a non-idempotent request merely because the client did not understand the response body.
For telemetry, record HTTP 202, 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.