⏳
102
Processing
Example HTTP Response
HTTP Response
HTTP/1.1 102 ProcessingCommon Causes
- WebDAV request taking a long time
- Complex server-side processing
- Preventing client timeout during long operations
Technical Details
What does this mean?
Hold tight! The server is cooking something up in the kitchen. Your order will be ready soon!
Technical Definition
The server has received and is processing the request, but no response is available yet.
RFC Says
"The 102 (Processing) status code is an interim response used to inform the client that the server has accepted the complete request, but has not yet completed it."
Plain English:
The server is working on your request but it's taking a while. This prevents your client from timing out while waiting. Used primarily in WebDAV for long-running operations.
Code Snippets
Ready-to-use code for returning this HTTP status in your application:
Node.js
// Express.js
app.get('/example', (req, res) => {
res.status(102).json({
error: 'Processing',
message: 'Your error message here'
});
});
// Native HTTP
const http = require('http');
http.createServer((req, res) => {
res.writeHead(102, { 'Content-Type': 'application/json' });
res.end(JSON.stringify({
error: 'Processing',
message: 'Your error message here'
}));
}).listen(3000);