Re: 202 Response to GET request

Seems very odd for the reasons you cited, 202 says your request has
not been processes. The spec also speaks about the location uri pointing to
a monitor. I would not expect the status code of that monitor to be a 202
either.

On Saturday, October 5, 2013, Unmesh Joshi wrote:

> **
>
>
> 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
>
>  
>