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

Response code for stale published value or empty response, "no content" #4

Open
mjkoster opened this issue Mar 30, 2017 · 2 comments
Open

Comments

@mjkoster
Copy link
Contributor

Currently we define a "no content" response, such as when a GET is done on a value which has expired its lifetime, with 2.04. We should probably define a new response code like 2.06 for this instead of trying to overload the 2.04 when used as a "changed" response to POST or PUT.

@mjkoster
Copy link
Contributor Author

The semantic of this code is not the same as the HTTP 204 "No Response". 204 indicates that the data have not changes and the client may continue to use the last transmitted value. We need a response code that indicates data are not transmitted because of staleness and the client should not use the last transmitted value.

@mjkoster
Copy link
Contributor Author

Suggest we create an equivalent response code to HTTP 202 Accepted

202 Accepted
The request has been accepted for processing, but the processing has not been completed. The request might or might not be eventually acted upon, and may be disallowed when processing occurs.

Suggest using 2.07

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

1 participant