-
Notifications
You must be signed in to change notification settings - Fork 43
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
provide a definition for partial PUT #653
Conversation
Co-authored-by: Julian Reschke <julian.reschke@gmx.de>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe I'm misreading this, but the details do not seem to allow what would be the natural seconf request in a sequence of partial PUTs for a resumable upload: appending to an existing representation.
Good point, though I didn't think appending was an option. I have reduced the description to just the basics. |
This is now effectively the same as what @mnot suggested but as a separate section referred to by both PUT and Content-Range. |
Co-authored-by: Julian Reschke <julian.reschke@gmx.de>
fix cache response directive subsection ordering caching editorial httpwg/http-core#679 Rework representations httpwg/http-core#673 Invalid Date handling httpwg/http-core#671 Specify IMS and IUS like INM and If-Match httpwg/http-core#670 Modify must-understand to be backwards-compatible httpwg/http-core#668 Even HTTP/1.0 caches now support Age and CC httpwg/http-core#667 Clarify how multiple validators are handled httpwg/http-core#666 Mention INM/IMS precedence httpwg/http-core#664 Clarify how caches handle missing Date httpwg/http-core#663 parse defensively instead of requiring an untestable reasonableness httpwg/http-core#662 mention request target forms in considerations for new methods httpwg/http-core#656 Use the term content instead of payload httpwg/http-core#655 provide a definition for partial PUT semantics httpwg/http-core#653
Fixes #618 the other way