5 ms·

HTTP 202 Accepted [1] does the job. [1] http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.2.3 http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html

• jeremyjh 13y ago
  Actually it doesn't. The "hard" problem here isn't telling the client to come back later, it is providing the client with a way to get the actual results later. So providing a request identifier that gets populated in a database when the task is complete may be one way to do that.
  • icebraining 13y ago
    → POST /resource ← 202 Accepted ← Location: /jobs/XXX
    • jeremyjh 13y ago
      Right but you need /jobs/XXX to return a response that is not 404. How you accomplish this is outside the scope of what 202 provides you.