HTTP 202 Accepted

Success code, RFC 9110, section 15.3.3

What it means

The server accepted the request but has not finished it. It may be done later, or it may fail later: the code does not promise the outcome.

A real response

This is the request and the answer our test server gave when we asked it to return 202.

GET /c/202 HTTP/1.1
Host: example.com

HTTP/1.1 202 Accepted
Date: Sat, 14 Nov 2026 10:00:00 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 11

<p>demo</p>

If you run the site

Use 202 for work done in the background, such as an export or an email send. Give the client a way to check progress, usually a status address in the body or a Location header. There is no way in HTTP to send the final result later on the same request.

If you are a visitor

Wait and check again later, as the page or program says.

A common mistake

Using 202 and never telling the client how to learn the result.

Registered in the IANA HTTP Status Code Registry as Accepted, defined in RFC 9110, section 15.3.3.

This is an independent guide. It is not connected with the IETF, IANA, any browser maker or any company named here. Meanings were checked against the RFC texts on 14 November 2026. Responses shown were recorded on 14 November 2026 from a small test server on the author's own computer.