You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/r2/buckets/public-buckets.mdx
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ import { Render } from "~/components";
12
12
13
13
Public Bucket is a feature that allows users to expose the contents of their R2 buckets directly to the Internet. By default, buckets are never publicly accessible and will always require explicit user permission to enable.
14
14
15
-
Public buckets can be set up in either one of two ways:
15
+
Public buckets can be set up in either of two ways:
16
16
17
17
- Expose your bucket as a custom domain under your control.
18
18
- Expose your bucket using a Cloudflare-managed `https://r2.dev` subdomain for non-production use cases.
@@ -33,7 +33,7 @@ Currently, public buckets do not let you list the bucket contents at the root of
33
33
34
34
Domain access through a custom domain allows you to use [Cloudflare Cache](/cache/) to accelerate access to your R2 bucket.
35
35
36
-
Configure your cache to use [Smart Tiered Cache](/cache/how-to/tiered-cache/#smart-tiered-cache) to have a single uppertier data center next to your R2 bucket.
36
+
Configure your cache to use [Smart Tiered Cache](/cache/how-to/tiered-cache/#smart-tiered-cache) to have a single upper-tier data center next to your R2 bucket.
37
37
38
38
:::note
39
39
@@ -112,14 +112,14 @@ Expose the contents of this R2 bucket to the internet through a Cloudflare-manag
112
112
113
113
:::note
114
114
115
-
Public access through `r2.dev` subdomains are ratelimited and should only be used for development purposes.
115
+
Public access through `r2.dev` subdomains is rate-limited and should only be used for development purposes.
116
116
117
-
To enable access management, Cache and bot management features, you must set up a custom domain when enabling public access to your bucket.
117
+
To enable access management, cache, and bot management features, you must set up a custom domain when enabling public access to your bucket.
118
118
119
119
Avoid creating a CNAME record pointing to the `r2.dev` subdomain. This is an **unsupported access path**, and we cannot guarantee consistent reliability or performance. For production use, [add your domain to Cloudflare](#add-your-domain-to-cloudflare) instead.
120
120
:::
121
121
122
-
### Enable public development url
122
+
### Enable public development URL
123
123
124
124
When you enable public development URL access for your bucket, its contents become available on the internet through a Cloudflare-managed `r2.dev` subdomain.
125
125
@@ -133,7 +133,7 @@ To enable access through `r2.dev` for your buckets:
133
133
134
134
To verify that your bucket is publicly accessible, check that **Public URL Access** shows **Allowed** in you bucket settings.
135
135
136
-
### Disable public development url
136
+
### Disable public development URL
137
137
138
138
Disabling public development URL access removes your bucket's exposure through the `r2.dev` subdomain. The bucket and its objects will no longer be accessible via the Public Bucket URL.
0 commit comments