Is 102 Processing still a valid status code?
It is still listed in the IANA registry, but the WebDAV specification that defined it dropped it in 2007. Treat it as legacy: understand it if you receive it, but do not send it from new code.
HTTP 102 PROCESSING
WebDAV: the server is still working on a long request. Deprecated in practice. 102 belongs to the 1xx informational class and is defined in RFC 2518.
Loading the workbench.
About HTTP 102
What Does HTTP 102 Processing Mean?
WebDAV: the server is still working on a long request. Deprecated in practice. The code is registered with IANA and defined in RFC 2518.
Informational: the request was received and the process continues. Every code from 100 to 199 shares that general meaning, so a client that does not recognise 102 must treat it like 100.
When Do You See a 102 Response?
102 Processing comes from WebDAV (RFC 2518). A server working on a long request, such as a recursive COPY or MOVE of a large directory tree, could send it to stop the client from timing out while the real answer was still being built. RFC 4918 removed it from the WebDAV specification, and outside a few legacy WebDAV servers you will almost never see it today. It is informational only: a final status always follows.
How Do You Handle a 102?
Clients can ignore a 102 and keep waiting for the final response; well-behaved HTTP libraries discard interim responses they do not understand. New servers should not send it. For slow operations, a better pattern is to answer 202 Accepted at once with a URL the client can poll, or to stream progress over a separate channel, rather than holding a connection open behind interim responses.
What Does a 102 Response Look Like?
HTTP/1.1 102 Processing102 is not cacheable by default: a browser or CDN stores it only when Cache-Control or Expires explicitly allows it.
To inspect a real one without sending it anywhere:
- Copy the response headers from your browser Network tab, or from
curl -i. - Paste them into the Header decoder to see every header explained.
- Check caching in the Cache lane.
Which Status Codes Are Related to 102?
- 202 Accepted: The request was queued but not finished. Common for background jobs.
- 207 Multi-Status: WebDAV: the body holds separate status codes for several resources.
- 103 Early Hints: Preliminary Link headers so the browser can preload assets while the final response is prepared.
Browse every code on the HTTP status codes page.
What Other Lanes Are in the Reference Section?
- HTTP status codes: Every IANA-registered status code, with a page per code.
- MIME types: File extensions to Content-Type, searchable both ways, plus a Content-Type parser.
- HTTP methods: GET, POST, PUT, PATCH, DELETE and the rest: safe, idempotent, cacheable.
Elsewhere in 2http: Header decoder, Cookie decoder, Cache-Control decoder, CORS checker, User-agent parser, and all eleven lanes on the 2http home page. Part of the 2suite.io privacy-first ecosystem.
Frequently Asked Questions
What should I use instead of 102 for slow requests?
Return 202 Accepted with a Location or a body pointing to a status resource, then let the client poll it. That avoids long-held connections that proxies and load balancers may cut.
Is HTTP 102 an error?
No. 102 is a informational response, not an error.
Is a 102 response cacheable by default?
No. Caches store a 102 only when Cache-Control or Expires explicitly allows it.
How Can You Verify That Nothing Leaves This Browser?
You do not have to take our word that your headers stay here. Developer tools show every request a page makes, so you can watch this page work and confirm that nothing is sent. The check takes under a minute.
- Open your browser developer tools with
F12, orCmd+Option+Ion a Mac, and select the Network tab. - Reload the page and let it finish. You will see the page's own files, its web fonts, and one anonymous page-view request. Nothing has been typed yet, so none of them can contain your headers.
- Click the clear icon in the Network tab so that the log is empty.
- Paste real headers into any lane and read the result.
- Look at the Network tab again. It is still empty. For extra proof, turn on offline mode after the page loads and every lane keeps working.
Only two things can add a line to that log, and neither carries your headers. Submitting the feedback form sends the vote and comment you typed. Typing characters in a script the page has not displayed yet, such as Cyrillic or Greek, can make the browser fetch the matching font file, and that request names only the font.
2http never sends a request on your behalf: the request builder writes code for you to run, and the meta inspector reads source you paste instead of fetching a URL. The production site also sends a Content-Security-Policy header that tells your browser to refuse connections to anywhere except this site and the anonymous analytics endpoint.