Bobcares

Cloudflare Access CORS Settings

by | Mar 8, 2024

Learn more about Cloudflare Access CORS Settings. Our Cloudflare Support team is here to help you with your questions and concerns.

Cloudflare Access CORS Settings

Are you wondering how your browser ensures that a website from Domain X doesn’t snatch resources from Domain Y?
Well, the answer lies in Cross-Origin Resource Sharing (CORS).

Cloudflare Access CORS Settings

 

Today, we will take a close look at CORS and how it safeguards our data while managing our bucket resources.

CORS makes sure that only the right domains get access to specific resources. It does this by using special headers in the HTTP responses from the resource domain, letting our browser double-check if the resource domain permits access.

CORS in Action with Your Bucket

When you’re mingling with a bucket through a web browser, CORS steps in. Here are the two options:

  1. Set a Bucket to Public:

    This option makes our bucket accessible on the Internet as read-only. In other words, anyone can request and load objects from our bucket in their browser or anywhere else. This works well if our bucket contains images used in a public blog.

  2. Presigned URLs:

    This grants individuals with a unique URL permission to execute specific actions on our bucket.

Before diving into CORS, we need the following:

  • An R2 bucket with at least one object (create one if needed).
  • A domain to access the object (even localhost will do).
  • Optional: Access keys, are only required for creating presigned URLs.

Using CORS with a Public Bucket

  1. First, make sure the bucket is set to allow public access.
  2. Then, add a CORS policy to the bucket to allow the file to be shared.

Using CORS with a Presigned URL

  1. Here, we need our S3-compatible credentials to generate the predesigned URL.
  2. Use `@aws-sdk/client-s3` in JavaScript to create a presigned PutObject URL.
  3. Then, upload an object using cURL to ensure our presigned URL is in top-notch shape.

Adding CORS Policies from the Cloudflare Dashboard

  1. Head over to the Cloudflare dashboard and select R2.
  2. Locate and select the bucket.
  3. Under CORS Policy, add our CORS policy from the JSON tab.
  4. Finally, click Save.

We can easily configure CORS settings by going to Transform Rules under Rules. Then, click “Modify Response Header,” and create a rule. This rule makes sure the CORS settings are on point.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

In brief, our Support Experts introduced us to Cloudflare Access CORS Settings.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF