blaginin commented on PR #609:
URL: 
https://github.com/apache/arrow-rs-object-store/pull/609#issuecomment-4269178970

   <details>
       <summary>In case it helps, here is how different clouds respond to 
various `Range` headers</summary>
   
   ```
   no `Content-Range`
         s3
                Status code: 200
                Content-Range: None
                Content-Length: 80835272
   
         tigris
                Status code: 200
                Content-Range: None
                Content-Length: 80835272
   
         r2
                Status code: 200
                Content-Range: None
                Content-Length: 80835272
   
         google cloud
                Status code: 200
                Content-Range: None
                Content-Length: 80835272
   
   ===
   bytes=100-200
         s3
                Status code: 206
                Content-Range: bytes 100-200/80835272
                Content-Length: 101
   
         tigris
                Status code: 206
                Content-Range: bytes 100-200/80835272
                Content-Length: 101
   
         r2
                Status code: 206
                Content-Range: bytes 100-200/80835272
                Content-Length: 101
   
         google cloud
                Status code: 206
                Content-Range: bytes 100-200/80835272
                Content-Length: 101
   
   ===
   bytes=0-(max+1)
         s3
                Status code: 206
                Content-Range: bytes 0-80835271/80835272
                Content-Length: 80835272
   
         tigris
                Status code: 206
                Content-Range: bytes 0-80835271/80835272
                Content-Length: 80835272
   
         r2
                Status code: 206
                Content-Range: bytes 0-80835271/80835272
                Content-Length: 80835272
   
         google cloud
                Status code: 206
                Content-Range: bytes 0-80835271/80835272
                Content-Length: 80835272
   
   ===
   bytes=-200
         s3
                Status code: 206
                Content-Range: bytes 80835072-80835271/80835272
                Content-Length: 200
   
         tigris
                Status code: 206
                Content-Range: bytes 80835072-80835271/80835272
                Content-Length: 200
   
         r2
                Status code: 206
                Content-Range: bytes 80835072-80835271/80835272
                Content-Length: 200
   
         google cloud
                Status code: 206
                Content-Range: bytes 80835072-80835271/80835272
                Content-Length: 200
   
   ===
   bytes=100-
         s3
                Status code: 206
                Content-Range: bytes 100-80835271/80835272
                Content-Length: 80835172
   
         tigris
                Status code: 206
                Content-Range: bytes 100-80835271/80835272
                Content-Length: 80835172
   
         r2
                Status code: 206
                Content-Range: bytes 100-80835271/80835272
                Content-Length: 80835172
   
         google cloud
                Status code: 206
                Content-Range: bytes 100-80835271/80835272
                Content-Length: 80835172
   
   ===
   bytes=(max + 100)-
         s3
                Status code: 416
                Content-Range: None
                Content-Length: None
   
         tigris
                Status code: 416
                Content-Range: None
                Content-Length: 255
                Content: `<?xml version="1.0" encoding="UTF-8"?>
   <Error><Code>InvalidRange</Code><Message>Invalid 
range</Message><Resource>/foo-compact.vortex</Resource><RequestId>1776438374761678270</RequestId><Key>foo-compact.vortex</Key><BucketName>dima-dev</BucketName></Error>`
   
         r2
                Status code: 416
                Content-Range: None
                Content-Length: 27150
   
         google cloud
                Status code: 416
                Content-Range: None
                Content-Length: 171
                Content: `<?xml version='1.0' 
encoding='UTF-8'?><Error><Code>InvalidRange</Code><Message>The requested range 
cannot be satisfied.</Message><Details>bytes=80835373-</Details></Error>`
   
   ===
   bytes=5-1
         s3
                Status code: 200
                Content-Range: None
                Content-Length: 80835272
   
         tigris
                Status code: 416
                Content-Range: None
                Content-Length: 255
                Content: `<?xml version="1.0" encoding="UTF-8"?>
   <Error><Code>InvalidRange</Code><Message>Invalid 
range</Message><Resource>/foo-compact.vortex</Resource><RequestId>1776438375764341629</RequestId><Key>foo-compact.vortex</Key><BucketName>dima-dev</BucketName></Error>`
   
         r2
                Status code: 400
                Content-Range: None
                Content-Length: 17949
   
         google cloud
                Status code: 200
                Content-Range: None
                Content-Length: 80835272
   
   ===
   bytes=???
         s3
                Status code: 200
                Content-Range: None
                Content-Length: 80835272
   
         tigris
                Status code: 416
                Content-Range: None
                Content-Length: 255
                Content: `<?xml version="1.0" encoding="UTF-8"?>
   <Error><Code>InvalidRange</Code><Message>Invalid 
range</Message><Resource>/foo-compact.vortex</Resource><RequestId>1776438377339542727</RequestId><Key>foo-compact.vortex</Key><BucketName>dima-dev</BucketName></Error>`
   
         r2
                Status code: 400
                Content-Range: None
                Content-Length: 17949
   
         google cloud
                Status code: 200
                Content-Range: None
                Content-Length: 80835272
   ```
   
   </details>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to