I believe this S is the start of STREAMING-AWS4-HMAC-SHA256-PAYLOAD (if you could confirm this by looking in Garage logs or by using Wireshark it would be amazing).
This mode of payload…
- In case one of the parts upload went wrong, you have to abort the multipart upload and start over.
I think this is the most annoying part of this ticket. It's one of the main selling point of…
for a file with 2 part of exactly 6Mio each, the exact header is
Content-Range: bytes 6291456-12582911/12582912, so it's the latter (with added full content lenght which was not in your example)
multiple small diffences with AWS. I wouldn't consider them blocking, if you want to merge this quiclky, just open an issue for them.
minor missmatch with AWS : if not multipart, AWS consider everything is contained in part 1.
AWS does not support this kind of request (InvalidRequest: Cannot specify both Range header and partNumber query parameter).
AWS returns byte range headers and HTTP 206 (Partial Content) as if it was a range request
prefere using clamp, min(max(..)..) is unclear and very much subject to inverting bounds.