2015-11-06 22:55:41 +01:00
|
|
|
---
|
|
|
|
set: 1
|
|
|
|
code: 102
|
|
|
|
title: Processing
|
2015-11-07 01:41:41 +01:00
|
|
|
references:
|
|
|
|
"Rails HTTP Status Symbol": ":processing"
|
2015-11-06 22:55:41 +01:00
|
|
|
---
|
|
|
|
|
2015-11-07 06:24:24 +01:00
|
|
|
The 102 Processing status code is an interim response used to inform the
|
2015-11-07 01:28:15 +01:00
|
|
|
client that the server has accepted the complete request, but has not yet
|
2015-11-07 06:24:24 +01:00
|
|
|
completed it.
|
|
|
|
|
|
|
|
This status code SHOULD only be sent when the server has a
|
2015-11-07 01:28:15 +01:00
|
|
|
reasonable expectation that the request will take significant time to complete.
|
|
|
|
As guidance, if a method is taking longer than 20 seconds (a reasonable, but
|
|
|
|
arbitrary value) to process the server SHOULD return a 102 (Processing)
|
|
|
|
response. The server MUST send a final response after the request has been
|
|
|
|
completed.
|
|
|
|
|
|
|
|
Methods can potentially take a long period of time to process, especially
|
|
|
|
methods that support the Depth header. In such cases the client may time-out the
|
|
|
|
connection while waiting for a response. To prevent this the server may return a
|
|
|
|
102 (Processing) status code to indicate to the client that the server is still
|
|
|
|
processing the method.
|
|
|
|
|
|
|
|
Source: [RFC2518 Section 10.1][1]
|
|
|
|
|
|
|
|
[1]: <http://tools.ietf.org/html/rfc2518#section-10.1>
|