RESUMABLE: Remove nominative languages addressing the lost final response#3405
Merged
Conversation
smatsson
approved these changes
Apr 17, 2026
Acconut
reviewed
May 12, 2026
| - If the client attempted to append a zero-length document: | ||
| - If the server retains knowledge of the upload resource but it is not available, the `410 (Gone)` status code can be used; the response could also contain a `Location` header field to indicate the location of the completed upload. The server can use the problem type {{PROBLEM}} of "https://iana.org/assignments/http-problem-types#completed-upload" ({{completed-upload}}) in the response. | ||
| - If the server has not retained knowledge of the upload resource, a `404 (Not Found)` status code can be used. | ||
| Even if the upload is complete ({{upload-complete}}) in the server's perspective and the final response from the targeted resource has already been sent, the client might still perform an upload append {#upload-appending} after an offset retrieval {#offset-retrieving} due to the response being lost during transmission. The server can choose to replay the final response to the client if the request to append to the completed upload is valid. |
Member
There was a problem hiding this comment.
Can we move this paragraph down one paragraph after "If the Upload-Complete request header field is set to true [...]"? This other paragraph talks about generating responses, which helpful context to understand what this new sentence is about.
Contributor
Author
There was a problem hiding this comment.
I moved it 2 paragraphs down since they are related
LPardue
reviewed
May 13, 2026
LPardue
reviewed
May 13, 2026
LPardue
approved these changes
May 13, 2026
Contributor
LPardue
left a comment
LPardue
left a comment
There was a problem hiding this comment.
LGTM modulo some minor comments
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
4 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. Removing nominative language recommending that the server should keep the temporary resource alive, 410 Gone, and the
completed-uploadproblem type.Mention the possibility of the client performing offset retrieval and upload append even if the upload is complete in the server's perspective, but do not require a specific way to handle this situation.
Resolves #3270