RESUMABLE: Redefine Upload-Complete on the server side#3404
Open
guoye-zhang wants to merge 1 commit intohttpwg:mainfrom
Open
RESUMABLE: Redefine Upload-Complete on the server side#3404guoye-zhang wants to merge 1 commit intohttpwg:mainfrom
guoye-zhang wants to merge 1 commit intohttpwg:mainfrom
Conversation
GrantGryczan
suggested changes
Mar 29, 2026
|
|
||
| An upload is marked as completed if a request for creating the upload resource ({{upload-creation}}) or appending to it ({{upload-appending}}) included the `Upload-Complete` header field with a true value and the request content was fully processed. | ||
|
|
||
| The `Upload-Complete` response header field distinguishes the response from the initial targeted resource or the temporary upload resource. The value of true means the response is from the the initial targeted resource, and the value of false means the response is from the temporary upload resource. It is worth noting that `Upload-Complete` can be true even if the upload is not complete if the targeted resource decides to generate an early response. |
Contributor
There was a problem hiding this comment.
It is worth noting that
Upload-Completecan be true even if the upload is not complete
This is confusing, especially since arguably Upload-Complete being true defines the notion that the upload was completed in some sense. How about this (also fixed a typo, "the the"):
Suggested change
| The `Upload-Complete` response header field distinguishes the response from the initial targeted resource or the temporary upload resource. The value of true means the response is from the the initial targeted resource, and the value of false means the response is from the temporary upload resource. It is worth noting that `Upload-Complete` can be true even if the upload is not complete if the targeted resource decides to generate an early response. | |
| The `Upload-Complete` response header field distinguishes the response from the initial targeted resource or the temporary upload resource. The value of true means the response is from the initial targeted resource, and the value of false means the response is from the temporary upload resource. It is worth noting that `Upload-Complete` can be true even when the full representation data was not received if the targeted resource decides to generate an early response. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Discussed during IETF125. Refining the
Upload-Completeresponse header to differentiate the final response from the responses from the upload resource. Also allowing the final response to arrive early.Resolves #3398