|
- Use http status 202 for asynchronous operations - Stack Overflow
As you said, the 202 response should return a Location header specifying the URL that client should use to monitor the status of its previous request Calling this Check-the-status-of-my-process URL, instead of returning a 202 in case of process pending, I would return: 200 OK when the requested process is still pending The Response should
- HTTP Status code 202 vs 200 for a POST request - Stack Overflow
I have confusion that, Im using 202 status code, when I receive a POST request from a client (A) and B is processing it , passing the output to another endpoint(C) In this case I use 202 status code when B receives the request from A ( I have added the sample message flow ) B is not sending any other response back to A
- Is it wrong to return 202 Accepted in response to HTTP GET?
Otherwise, a 202 "Accepted" status code is returned, and the client must poll the resource until the final representation is available The reason for this behavior is the following: If a result is available within a few seconds, it needs to be retrieved as soon as possible; otherwise, when it becomes available is not important
- return value - REST API 202 versus 204 - Stack Overflow
That would be a 202 There is no response body after the processing is complete (and successful) If there is no way for it to fail, or the client doesn't care about failure, and the client doesn't care when the action is complete, then 204 would be appropriate as there's no point in delaying it
- Phone Number Lookup
800notes is a FREE REVERSE PHONE NUMBER LOOKUP database built by YOU, its users Our strength is in our numbers - by sharing pieces of information each of us has we are putting together a free and public phone number directory with information no other service can provide
- HTTP status code 202 or 303. When I need use it? - Stack Overflow
Maybe reding rfc2616-sec10 will help you out, they say the following about the status code 202: 10 2 3 202 Accepted The request has been accepted for processing, but the processing has not been completed The request might or might not eventually be acted upon, as it might be disallowed when processing actually takes place
- How long will a Logic App continue to check a HTTP 202 Accepted . . .
Following is the request I made it returned a status of 202 When I did a GET on the url received in above call after 1 minute I received a 500 Status code Following is the Logic app run history, which shows that the Logic App stopped waiting after 1 Minutes of polling Now I have removed the Timeout defined previously and made a request as
- Is the use of Location header in HTTP 202 response RFC-compliant?
202 is a success status The pointer mentioned is just hypertext in the body of the response A 303 should be sent if you want to use Location to redirect the client to another resource The result of the redirected request can be a 202 Roy So, the Location header should not be used in 202 Accepted response The PHP guys did the right
|
|
|