So I use a Backblaze B2 bucket to serve JSON files that don’t change very often. I serve this on an
api subdomain on my domain.
Here’s an example URL: api.brawlapi.com/v1/maps
This URL loads and serves content just fine if I request it via Postman, but fails (404 file not found) when requested from Brave/Chrome.
To provide more insight on what I use and how, I followed these two tutorials below:
Here’s a page rule for the subdomain:
The transform rule (exception for two paths as I use workers on those)
Here’s a DNS record for this subdomain
The bucket on Backblaze B2
Here’s the file in this bucket I’m requesting
The issue is this! Whenever I request this file via a browser, in my case Brave / Chrome, it fails this way
However if I request the same URL from Postman, it serves the contents of the file as it should
I’m very lost in how I should approach this issue or how I should go around fixing this. I have no idea why this fails, maybe this is obvious to you. I would welcome some tips and I’m happy to provide anything else that might reveal this issue I missed. It’s not just me, but multiple people using my service who experience this same issue. In the past I used a Wasabi as an S3 bucket for the same purpose and it worked well and never had these issues, but a Transform Rule wasn’t necessary. That’s why I expect this is probably related to the Transform Rule? Looking for people who could help debug this.