HTTP 102 Processing vs 201 Created
HTTP 102 (Processing) is a 1xx Informational response, while 201 (Created) is a 2xx Success response. 102 indicates that the server has received and is processing the request, but no response is available yet. Prevents the client from timing out. In contrast, 201 means that the request succeeded and a new resource was created. Typically returned after POST or PUT requests that create a new entity.
Beschreibung
The server has received and is processing the request, but no response is available yet. Prevents the client from timing out.
Wann Sie es sehen
During long-running WebDAV operations.
Wie man es behebt
Wait for the final response. This is an interim status to prevent timeouts.
Beschreibung
The request succeeded and a new resource was created. Typically returned after POST or PUT requests that create a new entity.
Wann Sie es sehen
After successfully creating a new user, post, order, or other resource via a REST API.
Wie man es behebt
No fix needed. Check the Location header for the URL of the new resource.
Wesentliche Unterschiede
102 is a 1xx Informational response, while 201 is a 2xx Success response.
HTTP 102: The server has received and is processing the request, but no response is available yet. Prevents the client from timing out.
HTTP 201: The request succeeded and a new resource was created. Typically returned after POST or PUT requests that create a new entity.
You encounter 102 when during long-running WebDAV operations.
You encounter 201 when after successfully creating a new user, post, order, or other resource via a REST API.
Wann welchen verwenden
For 102 (Processing): Wait for the final response. This is an interim status to prevent timeouts. For 201 (Created): No fix needed. Check the Location header for the URL of the new resource.