202 Response to GET request
Unmesh Joshi <[email protected]> Sat, 5 Oct 2013 22:08:12 +0530
| Newsgroups | gmane.comp.web.services.rest |
|---|---|
| Message-ID | <CAOk+zfe3du4_ea-exz4PYGHtM5o8K9nOOigyOWpDeQC3b6u4KA@mail.gmail.com> |
Hi, I recently came across an API which was returning '202 Accepted' response to GET request. It seemed a bit odd. Most asynchronous operations on HTTP implemented with POST request and 202 response. While HTTP does not mandate 202 response to be returned only to POST requests, following lines in RFC do indicate, its almost always going to POST. "The 202 response is intentionally non-committal. Its purpose is to allow a server to accept a request for some other process. (perhaps a batch-oriented process that is only run once per day) without requiring that the user agent's connection to the server persist until the process is completed. " Have anyone come across implementations using 202 response for GET? Thanks, Unmesh