Re:Show HN: We built an end-to-end encrypted alternative to ...
by bjyule on Monday August 30, 2021 @10:45AM
(#28356175)
When you say incompatible, are you talking about the cache not working or something else? How are you working around this using workers?
[ Parent
| on HN ]
Re:Show HN: We built an end-to-end encrypted alternative to ...
by vishnumohandas on Monday August 30, 2021 @10:52AM
(#28356220)
B2 documentation suggests that after adding a CNAME (eg. cdn.ente.io) for their bucket endpoint (eg. bucket.s3.eu-central-003.backblazeb2.com), you will be able to replace the latter with the former. This breaks with the native B2 APIs with the following error:
```
{
"code": "not_found",
"message": "/api/top_level_url_mapping",
"status": 404
}```
The last I checked was a few months ago, not sure if things have been fixed now.
With Workers, we simply fetch the remote resource from B2 and return it back to the client, acting as a thin proxy.