Michael Hart

@alukach I can see you're using different hosts. If your bucket is in the us-west-2 region, shouldn't your host be `aws4fetch-err-example.s3.us-west-2.amazonaws.com`?

See: https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html#virtual-hosted-style-access

Actually, if you're using Cloudflare, it will always be `accept-encoding: gzip` – regardless of if you specify it or not. https://github.com/cloudflare/miniflare/blob/9265fa4d53262ce66278b91f2001b090e10696e8/packages/http-server/src/index.ts#L117-L123 I'd just remove the header altogether and try again....

@kyranb ah ok, thanks. I guess Backblaze must require that the `range` header is signed.

> > Actually, if you're using Cloudflare, it will always be accept-encoding: gzip – regardless of if you specify it or not. > > So are you saying that Cloudflare...

Changing this to be a Node.js-support specific issue. The ability to use this locally should be supported by [`workerd`](https://github.com/cloudflare/workerd) and I assume Deno as well (though haven't checked). If anyone...

You don't need to necessarily run Docker-in-Docker for this – you could just run it as a sibling couldn't you? ie, with: ``` docker run -v /var/run/docker.sock:/var/run/docker.sock ... ```

Personally I feel that as more and more tools become containerized, it's actually incumbent on Docker itself to make integration easier – otherwise there are going to be more and...

@GeoffreyBooth the docker image you're talking about has such an example: https://github.com/cnadiminti/docker-aws-sam-local#how-to-use-this-image

@GeoffreyBooth that seems like Docker's working – just you don't have your Lambda JS files setup in the correct hierarchy?