The DevOps Drop
Home / Encyclopedia / HTTP Status Codes / 1xx Informational Responses / 102 Processing

102 Processing

The HTTP 102 Processing status code tells a client that the server has received the request but is still working on processing it. Learn how it is used in long-running operations and WebDAV systems.

Published 16 Jul 2026 · HTTP Status Code

What is HTTP 102 Processing?

The 102 Processing status code is an informational HTTP response indicating that the server has accepted the request but has not completed processing it yet.

It is part of the 1xx Informational response family and was introduced for WebDAV operations that may take significant time to complete.

Why Does 102 Processing Exist?

Some operations require more time than a typical HTTP request.

Without an intermediate response, clients may assume the connection has failed and terminate the request.

The 102 Processing response tells the client:

The request is still being worked on.
Please wait.

Example

HTTP/1.1 102 Processing

The server can continue processing before eventually returning the final response.

Where Is It Used?

  • WebDAV operations
  • Large file processing
  • Long-running backend tasks
  • Complex server operations

Why Does It Matter For DevOps?

Although rarely seen in modern application logs, understanding 102 Processing helps when debugging long-running requests and asynchronous workflows.

  • Timeout troubleshooting
  • Reverse proxy configuration
  • Long-running API requests
  • Background processing systems

Summary

The 102 Processing response keeps clients informed that a request is still being handled.