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

Send Last-Modified in response to PUT #173

Open
sonnyp opened this issue Feb 25, 2019 · 0 comments
Open

Send Last-Modified in response to PUT #173

sonnyp opened this issue Feb 25, 2019 · 0 comments

Comments

@sonnyp
Copy link

sonnyp commented Feb 25, 2019

Could we add Last-Modified as a response header in the PUTexamples https://tools.ietf.org/html/draft-dejong-remotestorage-12#section-12.5

See https://tools.ietf.org/html/rfc7231#section-7.2
Also RFC 7231 says it's fine in our case:

An origin server MUST NOT send a validator header field
   (Section 7.2), such as an ETag or Last-Modified field, in a
   successful response to PUT unless the request's representation data
   was saved without any transformation applied to the body (i.e., the
   resource's new representation data is identical to the representation
   data received in the PUT request) and the validator field value
   reflects the new representation.

It helps with consistency and prevents having to send a subsequent HEAD request to have the precise/server date.

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

No branches or pull requests

1 participant