Missing rest-discuss lately. :(
>
> Sure, what I’m trying to say is that this draft is intended to
> be genetic mechanism to upgrade any upload into resumable
> upload regardless of method or URI.
>
Doesn't HTTP already provide a uniform interface capable of solving this problem? Regardless of upload method...
Server knows the upload was interrupted if the received content falls short of Content-Length, or the connection timed out, or whatever.
Reconnected client makes HEAD request...
Server responds 206 with Content-Range: {zero to Content-Length} -- indicating an interrupted upload, if the client didn't make a range request.
I don't see any prohibition against responding 206 to a non-range request?
Client now knows how to PATCH the resource. Lather-rinse-repeat until 200 OK on HEAD.
-Eric
Received on Tuesday, 5 April 2022 01:27:51 UTC