mirror of
https://github.com/rmaake1/httpstatuses.git
synced 2024-11-02 00:32:36 +01:00
28 lines
1.3 KiB
Markdown
28 lines
1.3 KiB
Markdown
---
|
|
set: 2
|
|
code: 202
|
|
title: Accepted
|
|
references:
|
|
"Rails HTTP Status Symbol": ":accepted"
|
|
"Go HTTP Status Constant": "http.StatusAccepted"
|
|
"Symfony HTTP Status Constant": "Response::HTTP_ACCEPTED"
|
|
"Python2 HTTP Status Constant": "httplib.ACCEPTED"
|
|
"Python3+ HTTP Status Constant": "http.client.ACCEPTED"
|
|
"Python3.5+ HTTP Status Constant": "http.HTTPStatus.ACCEPTED"
|
|
---
|
|
|
|
The request has been accepted for processing, but the processing has not been
|
|
completed. The request might or might not eventually be acted upon, as it might
|
|
be disallowed when processing actually takes place.
|
|
|
|
There is no facility in HTTP for re-sending a status code from an asynchronous
|
|
operation.
|
|
|
|
The 202 response is intentionally noncommittal. Its purpose is to allow a server to accept a request for some other process (perhaps a batch-oriented process that is only run once per day) without requiring that the user agent's connection to the server persist until the process is completed. The representation sent with this response ought to describe the request's current status and point to (or embed) a status monitor that can provide the user with an estimate of when the request will be fulfilled.
|
|
|
|
---
|
|
|
|
* Source: [RFC7231 Section 6.3.3][1]
|
|
|
|
[1]: <http://tools.ietf.org/html/rfc7231#section-6.3.3>
|