api-guidelines icon indicating copy to clipboard operation
api-guidelines copied to clipboard
verified publisher icon microsoft

Alternate long running operation strategy

Open darrelmiller opened this issue 7 years ago • 2 comments

Related to #10

This change removes the need for the custom header Operation-Location and uses the standard Content-Location header to enable the hybrid flow. This approach ensures that all long running operations use the standard 202 status code and Location header pattern. It also removes the need to prevent a body from being returned with a 202 response.

darrelmiller avatar Feb 06 '18 16:02 darrelmiller

Do we have any consensus on this? We are building a new API and were wondering if we should follow this new approach.

AkJo avatar Mar 20 '18 03:03 AkJo

If there's concern on a breaking change, why not introduce a header or some way for clients to opt-in to the alternative behavior? The approach suggested seems like it is in-line with how the HTTP spec defines using the 202 header. On a different note, did anyone consider submitting the new header to the IETF, in order to get some discussion around its introduction?

glennblock avatar Mar 25 '18 19:03 glennblock