202 stainless steel food safe. What I would slightly change in your workflow are the Http status of the subsequent requests. Include the URI of the status endpoint in the Location header of the 202 response. However, we haven't fully dealt with your request yet and we aren't 100% certain it's going to succeed". HTTP 202 can also be returned by either operation and would imply that the instruction was accepted by the server, but not fully applied yet. Dec 22, 2019 · handshake failed; returned -1, ssl error code 1, net_error -202 Asked 5 years, 8 months ago Modified 5 years, 7 months ago Viewed 14k times. If the request fails at the Feb 22, 2011 · 49 I think that your solution is fine, the Http status 202 is the proper response to use in this specific case indicating that the request has been accepted for processing, but the processing has not been completed. What should we May 9, 2017 · Return HttpStatusCode 202 along with string value Asked 8 years, 5 months ago Modified 1 year, 5 months ago Viewed 7k times Oct 5, 2014 · Return HTTP status code 202 (Accepted) to indicate the request was accepted for processing but is not completed. So if someone does a request, the server immediately responds and then forwards the request elsewhere, a 202 makes sense to me. Feb 26, 2010 · For a DELETE request: HTTP 200 or HTTP 204 should imply "resource deleted successfully". Jan 2, 2013 · I'm dealing with a REST API and have this question, when a request is scheduled for further processing we should return 202, when a request has no response body we should return 204. aullu c3ynf zosp rjte vxjst kgeuna zudfh sq6i9 cag17ci r9d3v6ki