microsoft / microsoft/api-guidelines
[Question] Long running operations on 200 with a Retry-After VS other standards (e.g. w3.org)
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 23.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
Hi there,
I started following the guidelines for Long running operations 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
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No project file or test is named. Start with the long-running-operations guidance referenced in the issue, then read the linked Mozilla and W3C material and check jQuery's stated behavior. Done would require resolving the standards question and making the guideline's recommendation unambiguous.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jquery
- Domain
- api
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100