202 ACCEPTED

202 ACCEPTED

The request has been acknowledged for preparing, yet the handling has not been finished.

The request may or may not in the end be followed up on, as it may be refused when handling really happens. There is no office in HTTP for re-sending a status code from a nonconcurrent activity.

The 202 reaction is deliberately reserved. Its motivation is to enable a server to acknowledge a request for some different procedure (maybe a cluster situated procedure that is just run once every day) without necessitating that the client specialist’s association with the server continue until the procedure is finished. The representation sent with this reaction should depict the request’s present status and point to (or install) a status screen that can furnish the client with a gauge of when the request will be satisfied

Leave a Reply