Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What error code should we use when historical versions are missing? #108

Open
josephg opened this issue Mar 25, 2021 · 1 comment
Open

Comments

@josephg
Copy link
Contributor

josephg commented Mar 25, 2021

This issue is a follow-up to #90 . The spec is now intentionally ambiguous about which error code to send when historical versions are missing or unavailable on the server.

I proposed 416 Range Not Available, but it was raised that 416 might not make sense given the request wasn't a range request.

Alternate suggestions:

  • Add a new status code - but that might be difficult to get by HTTPBIS
  • Use 425 Too Early ? 412 Precondition Failed?
  • Have the server respond with the current version of the document instead

It would be great to get some use cases for requesting historical versions from the server in general, to figure out what the client should do in cases like this.

@mitar
Copy link
Member

mitar commented Apr 11, 2022

I think 410 Gone is almost perfect for this: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/410

Or maybe simply 404?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants