.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
.The main purpose of using 202 instead of 200 is for a server to communicate to a client: quot;From what I can tell, the request looks good. However, we havent fully dealt with
.For a DELETE request: HTTP 200 or HTTP 204 should imply quot;resource deleted successfullyquot;. HTTP 202 can also be returned by either operation and would imply that the
Otherwise, a 202 quot;Acceptedquot; 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
.What is the appropriate way of giving an estimate for request completion when the server returns a 202 - Accepted status code for asynchronous requests? From the HTTP
.Return HTTP status code 202 (Accepted) to indicate the request was accepted for processing but is not completed. You should expose an endpoint that returns the status of
.handshake failed; returned -1, ssl error code 1, net_error -202 Asked 5 years, 7 months ago Modified 5 years, 6 months ago Viewed 14k times
.Im 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
.Im trying to get the basic quot;hello worldquot; of sendgrid working, but have so far been unsuccessful. The response returns code 202, suggesting that it will send the email, but the
Ask questions, find answers and collaborate at work with Stack Overflow for Teams. Try Teams for free Explore Teams
.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
.The main purpose of using 202 instead of 200 is for a server to communicate to a client: quot;From what I can tell, the request looks good. However, we havent fully dealt with
.For a DELETE request: HTTP 200 or HTTP 204 should imply quot;resource deleted successfullyquot;. HTTP 202 can also be returned by either operation and would imply that the
Otherwise, a 202 quot;Acceptedquot; 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
.What is the appropriate way of giving an estimate for request completion when the server returns a 202 - Accepted status code for asynchronous requests? From the HTTP
.Return HTTP status code 202 (Accepted) to indicate the request was accepted for processing but is not completed. You should expose an endpoint that returns the status of
.handshake failed; returned -1, ssl error code 1, net_error -202 Asked 5 years, 7 months ago Modified 5 years, 6 months ago Viewed 14k times
.Im 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
.Im trying to get the basic quot;hello worldquot; of sendgrid working, but have so far been unsuccessful. The response returns code 202, suggesting that it will send the email, but the
Ask questions, find answers and collaborate at work with Stack Overflow for Teams. Try Teams for free Explore Teams
.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
.The main purpose of using 202 instead of 200 is for a server to communicate to a client: quot;From what I can tell, the request looks good. However, we havent fully dealt with
.For a DELETE request: HTTP 200 or HTTP 204 should imply quot;resource deleted successfullyquot;. HTTP 202 can also be returned by either operation and would imply that the
Otherwise, a 202 quot;Acceptedquot; 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
.What is the appropriate way of giving an estimate for request completion when the server returns a 202 - Accepted status code for asynchronous requests? From the HTTP
.Return HTTP status code 202 (Accepted) to indicate the request was accepted for processing but is not completed. You should expose an endpoint that returns the status of
.handshake failed; returned -1, ssl error code 1, net_error -202 Asked 5 years, 7 months ago Modified 5 years, 6 months ago Viewed 14k times
.Im 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
.Im trying to get the basic quot;hello worldquot; of sendgrid working, but have so far been unsuccessful. The response returns code 202, suggesting that it will send the email, but the
Ask questions, find answers and collaborate at work with Stack Overflow for Teams. Try Teams for free Explore Teams
.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
.The main purpose of using 202 instead of 200 is for a server to communicate to a client: quot;From what I can tell, the request looks good. However, we havent fully dealt with
.For a DELETE request: HTTP 200 or HTTP 204 should imply quot;resource deleted successfullyquot;. HTTP 202 can also be returned by either operation and would imply that the
Otherwise, a 202 quot;Acceptedquot; 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
.What is the appropriate way of giving an estimate for request completion when the server returns a 202 - Accepted status code for asynchronous requests? From the HTTP
.Return HTTP status code 202 (Accepted) to indicate the request was accepted for processing but is not completed. You should expose an endpoint that returns the status of
.handshake failed; returned -1, ssl error code 1, net_error -202 Asked 5 years, 7 months ago Modified 5 years, 6 months ago Viewed 14k times
.Im 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
.Im trying to get the basic quot;hello worldquot; of sendgrid working, but have so far been unsuccessful. The response returns code 202, suggesting that it will send the email, but the
Ask questions, find answers and collaborate at work with Stack Overflow for Teams. Try Teams for free Explore Teams