HTTP 102 — Processing
HTTP 102 (WebDAV) is a keep-alive signal for slow operations: the server has received the full request and is still working, so it pings the client to prevent timeouts while a long collection move or copy runs.
When 102 shows up
- WebDAV operations that move large collections on the server side.
- Long-running requests where an idle connection would otherwise be dropped by an intermediary.
Mocking a 102 response
A response with this status can be faked end to end with a local mock rule — no backend changes needed. The configuration below mirrors the rule fields the ApiSimul editor uses (method, path, status, delay in milliseconds, response body):
{
"method": "GET",
"path": "/dav/copy-collection",
"status": 102,
"delay": 800,
"enabled": true,
"body": null
}Dynamic placeholders such as {{random.name}}, {{string.uuid}} or {{number.int 1 100}} can appear inside the body to vary each response, which keeps client-side list rendering and retry logic honest during development.
Frequently asked questions
What does HTTP 102 mean?
The server has accepted the request and is still processing; nothing is final yet. Clients should keep the connection open and wait for the real response.
How can I test a 102 response without a real backend?
Define a mock rule with the method and path your client requests and set the status to 102. The example configuration above returns this response after the listed delay, so the client exercises its 102 handling exactly as it would against a live server.
Related status codes
Need the response in your own project? Spin up rules for any status with the ApiSimul mock server, or browse every status code page.