Skip to main content
replaced https://tools.ietf.org/html/rfc with https://www.rfc-editor.org/rfc/rfc
Source Link

RFC 2518RFC 2518 suggests using HTTP 102 Processing:

RFC 2518 suggests using HTTP 102 Processing:

RFC 2518 suggests using HTTP 102 Processing:

replaced http://programmers.stackexchange.com/ with https://softwareengineering.stackexchange.com/
Source Link

A better approach is to respond with HTTP 202 Accepted and either let the user to get back to you later to determine whether the processing ended (for instance by calling repeatedly a given URI such as /process/result which would respond with HTTP 404 Not Found or HTTP 409 ConflictHTTP 409 Conflict until the process finishes and the result is ready), or notify the user when the processing is done if you're able to call the client back for instance through a message queue service (example) or WebSockets.

A better approach is to respond with HTTP 202 Accepted and either let the user to get back to you later to determine whether the processing ended (for instance by calling repeatedly a given URI such as /process/result which would respond with HTTP 404 Not Found or HTTP 409 Conflict until the process finishes and the result is ready), or notify the user when the processing is done if you're able to call the client back for instance through a message queue service (example) or WebSockets.

A better approach is to respond with HTTP 202 Accepted and either let the user to get back to you later to determine whether the processing ended (for instance by calling repeatedly a given URI such as /process/result which would respond with HTTP 404 Not Found or HTTP 409 Conflict until the process finishes and the result is ready), or notify the user when the processing is done if you're able to call the client back for instance through a message queue service (example) or WebSockets.

added 179 characters in body
Source Link
Arseni Mourzenko
  • 139.1k
  • 32
  • 359
  • 544

A better approach is to respond with HTTP 202 Accepted and either let the user to get back to you later to determine whether the processing ended (for instance by calling repeatedly a given URI such as /process/result which would respond with HTTP 404 Not Found or HTTP 409 Conflict until the process finishes and the result is ready), or notify the user when the processing is done if you're able to call the client back for instance through a message queue service (example) or WebSockets.

A better approach is to respond with HTTP 202 Accepted and either let the user to get back to you later to determine whether the processing ended (for instance by calling repeatedly a given URI such as /process/result which would respond with HTTP 404 until the process finishes and the result is ready), or notify the user when the processing is done if you're able to call the client back for instance through a message queue service (example) or WebSockets.

A better approach is to respond with HTTP 202 Accepted and either let the user to get back to you later to determine whether the processing ended (for instance by calling repeatedly a given URI such as /process/result which would respond with HTTP 404 Not Found or HTTP 409 Conflict until the process finishes and the result is ready), or notify the user when the processing is done if you're able to call the client back for instance through a message queue service (example) or WebSockets.

deleted 1 character in body
Source Link
Arseni Mourzenko
  • 139.1k
  • 32
  • 359
  • 544
Loading
added 1916 characters in body
Source Link
Arseni Mourzenko
  • 139.1k
  • 32
  • 359
  • 544
Loading
added 1916 characters in body
Source Link
Arseni Mourzenko
  • 139.1k
  • 32
  • 359
  • 544
Loading
added 160 characters in body
Source Link
Arseni Mourzenko
  • 139.1k
  • 32
  • 359
  • 544
Loading
added 731 characters in body
Source Link
Arseni Mourzenko
  • 139.1k
  • 32
  • 359
  • 544
Loading
Source Link
Arseni Mourzenko
  • 139.1k
  • 32
  • 359
  • 544
Loading