Problems serving static deltas from S3

[akiernan]

I don't think this is really a bug, but...

The namespace for static deltas includes the + character, which gets mapped to space by S3, when your client then tries to consume the static delta, the path seemingly doesn't exist.

We've custom tooling to upload to S3 so fixing it as we upload stuff was straightforward, but that's not an easy option if you're using aws s3 sync (we had to bail on using that as it was way too slow).

Not sure if there's really anything than knowing the problem exists that we can do, but writing it down here in case there's ideas we've not thought of and if not at least there's a reference for the next poor unfortunate to trip over it!

[jallwine]

I ran into this as well, unknowingly at first. Thanks for posting this!

A work around is to use the static website end point (http only): http://<bucket name>.s3-website-<region>.amazonaws.com

I believe that could then be mapped to an https endpoint using CloudFront.

The REST API endpoint seems to be the problem: https://<bucket name>.s3.<region>.amazonaws.com