-
Notifications
You must be signed in to change notification settings - Fork 123
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
If-None-Match header is ignored on POST requests #62
Comments
Rack-cache follows RFC 2616 which describes E-Tag and Last-Modifed headers to be used with GET exclusively, so it called ConditionalGet, http://tools.ietf.org/html/rfc2616#section-9.3 |
👍 |
If-None-Match can also be used in both PUT's and POST's. There is nothing in the spec that says it can't: https://tools.ietf.org/html/rfc2616#section-14.26 |
I also only know it as conditional get ... and always saw it implemented with a |
hmm I guess it can make sense if updating to the same state as before ... would love to see any other library that supports that though so rack-cache is not a 1-off with strange logic ... |
Conditional PUT's and conditional POST's can be used to create idempotent operations, meaning that ie. the same stuff is not created twice or updates are not processed in wrong order. See for instance https://www.hl7.org/fhir/http.html#cond-update |
Yeah, sounds good! |
The title says everything. When I send a GET request to the server, containing an
If-None-Match
header that matches theETag
, I get a304 Not Modified
response as expected. When I do the same for POST-Requests, I get a full response, even though it has the givenETag
.The text was updated successfully, but these errors were encountered: