This is probably related to GCP bucket definitions, but maybe you’ll be able to assist.
We’re in the process of testing the Saved Rows implementation on our side. We’ve added the externalContentURLs array to the beefree configuration.
The urls are pointing to a file that is stored in GCP.
The json file url works fine when accessing from the browser.
The problem is that when we open the Rows dropdown and click on the one category we currently have, no rows are being loaded and the browser indicates the following error:
"Access to XMLHttpRequest at [link to file in our GCP storage bucket] from origin ‘https://app.getbee.io‘ has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource."
In terms of GCP definitions, we’ve been following the instructions to allow CORS from the ‘https://app.getbee.io‘ origin.
We’ve been wondering if you have any input on this matter that may assist.
I believe we’ve addressed this via your ticket, but I will post some details here for the community.
When using any service, such as S3 or GCP, you must remove the authorization header in the request.
Otherwise, the service thinks you want to use authorization and there will be a 401 error in the browser.
The easiest way is to apply a CDN, such as AWS Cloudfront, and not pass the header through to S3.