-
Notifications
You must be signed in to change notification settings - Fork 7
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
Publish document version as ETag header #5
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
As a consumer of an API, I would like the service to publish appropriate cache headers, so that I can leverage caches & minimize resources.
Notes
MongoDB's automatic document versioning seems like a perfect fit for the
ETag
header. Sophisticated API clients could leverage that by including appropriateIf-None-Match
headers in their requests.This should also allow for more effective caching at the server level. Should be able to drop in caching proxies between the API and its clients to reduce load.
Acceptance Criteria
If-None-Match
header should include an ETag in the response. This is simply MongoDB's version number.If-None-Match
header should respond "304: Not Modified" if the value of the header matches the current MongoDB version for the requested entity.If-None-Match
header should respond "304: Not Modified" if the value of the header matches the current MongoDB version for the requested entity.References
The text was updated successfully, but these errors were encountered: