13.2.7.1 Long Running Operations.

[microsoft]

13.2.7.1 Long Running Operations.

[garethj-msft]

My understanding is that 102 is a code that should be sent as an interim for a single response, whereas the polling response has completed successfully, so 200 is more correct. Our position in general is that the HTTP status code refers to the specific HTTP call rather than the overarching operation.

[darrelmiller]

@edent The 200 response refers to the client making a GET request on a status resource. That status/progress resource is retrieved successfully and so the 200 is appropriate. How the progress resource reports the state of the operation is not defined by HTTP, but in the pattern doc I linked to I make some suggestions.

[garethj-msft]

I think we're comfortable with the current use of the codes here, so 'm going to close this one.

[whozDougie]

Hi there,

I started following the guidelines on 200 with a Retry-After, however, I quickly found that other frameworks such as jQuery does not support 200 with a Retry-After. An Article from Mozilla indicates that Retry-After is used with "413 Payload Too Large" and "503 Service Unavailable".
https://developer.mozilla.org/en-US/docs/Web/HTTP/Status

Also another article states the header can be used with 503 or 3XX: https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html

The problem is I then have to manually write code on these frameworks which have followed "standards" for the implementation. For example, if I try and get a Retry-After from a $.ajax call and I try to get headers, by default it jQuery will ignore the Retry-After header!

I'm not sure which standard / guideline is correct here, but I don't feel very confident with using 200 - unless I am missing something here.

Many thanks,
WhozDougie