From 003617a1dede1b0fdecb15e4c0bc1227b0ee24d8 Mon Sep 17 00:00:00 2001 From: Matt Silverlock Date: Tue, 26 Nov 2024 10:32:14 -0500 Subject: [PATCH 1/3] r2: clarify r2.dev limits --- src/content/docs/r2/platform/limits.mdx | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/src/content/docs/r2/platform/limits.mdx b/src/content/docs/r2/platform/limits.mdx index 5f815db06f8a35..5d58bc17d3bab2 100644 --- a/src/content/docs/r2/platform/limits.mdx +++ b/src/content/docs/r2/platform/limits.mdx @@ -35,4 +35,9 @@ Limits specified in MiB (mebibyte), GiB (gibibyte), or TiB (tebibyte) are storag ## Rate limiting on managed public buckets through `r2.dev` -Managed public bucket access through an `r2.dev` subdomain is not intended for production usage and has a rate limit applied to it. If you exceed the rate limit, requests through your `r2.dev` subdomain will be temporarily throttled and you will receive a `429 Too Many Requests` response. For production use cases, consider linking a [custom domain](/r2/buckets/public-buckets/#custom-domains) to your bucket. +Managed public bucket access through an `r2.dev` subdomain is not intended for production usage and has a variable rate limit applied to it. The `r2.dev` endpoint for your bucket is designed to enable testing: + +* If you exceed the rate limit (hundreds of requests/second), requests to your `r2.dev` endpoint will be temporarily throttled and you will receive a `429 Too Many Requests` response. +* Bandwidth (throughput) may also be throttled when using the `r2.dev` endpoint. + +For production use cases, connect a [custom domain](/r2/buckets/public-buckets/#custom-domains) to your bucket. Custom domains allow you to serve content from a domain you control (e.g. `assets.example.com`), configure fine-grained caching, set up redirect and rewrite rules, mutate content via [Cloudflare Workers](/workers/), and get detailed URL-level analytics for content served from your R2 bucket. From 79471b68cfb43b2a34b9685eec8d94fcdd810924 Mon Sep 17 00:00:00 2001 From: Matt Silverlock Date: Tue, 26 Nov 2024 11:01:42 -0500 Subject: [PATCH 2/3] Update src/content/docs/r2/platform/limits.mdx Co-authored-by: hyperlint-ai[bot] <154288675+hyperlint-ai[bot]@users.noreply.github.com> --- src/content/docs/r2/platform/limits.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/r2/platform/limits.mdx b/src/content/docs/r2/platform/limits.mdx index 5d58bc17d3bab2..a583c3408d065a 100644 --- a/src/content/docs/r2/platform/limits.mdx +++ b/src/content/docs/r2/platform/limits.mdx @@ -40,4 +40,4 @@ Managed public bucket access through an `r2.dev` subdomain is not intended for p * If you exceed the rate limit (hundreds of requests/second), requests to your `r2.dev` endpoint will be temporarily throttled and you will receive a `429 Too Many Requests` response. * Bandwidth (throughput) may also be throttled when using the `r2.dev` endpoint. -For production use cases, connect a [custom domain](/r2/buckets/public-buckets/#custom-domains) to your bucket. Custom domains allow you to serve content from a domain you control (e.g. `assets.example.com`), configure fine-grained caching, set up redirect and rewrite rules, mutate content via [Cloudflare Workers](/workers/), and get detailed URL-level analytics for content served from your R2 bucket. +For production use cases, connect a [custom domain](/r2/buckets/public-buckets/#custom-domains) to your bucket. Custom domains allow you to serve content from a domain you control (for example, `assets.example.com`), configure fine-grained caching, set up redirect and rewrite rules, mutate content via [Cloudflare Workers](/workers/), and get detailed URL-level analytics for content served from your R2 bucket. From e2830144795b190aa8ed57ab6b50431c6fc3b46d Mon Sep 17 00:00:00 2001 From: Matt Silverlock Date: Tue, 26 Nov 2024 11:34:55 -0500 Subject: [PATCH 3/3] Update src/content/docs/r2/platform/limits.mdx MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Denise Peña <75506267+dcpena@users.noreply.github.com> --- src/content/docs/r2/platform/limits.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/r2/platform/limits.mdx b/src/content/docs/r2/platform/limits.mdx index a583c3408d065a..866f49a3d860b7 100644 --- a/src/content/docs/r2/platform/limits.mdx +++ b/src/content/docs/r2/platform/limits.mdx @@ -35,7 +35,7 @@ Limits specified in MiB (mebibyte), GiB (gibibyte), or TiB (tebibyte) are storag ## Rate limiting on managed public buckets through `r2.dev` -Managed public bucket access through an `r2.dev` subdomain is not intended for production usage and has a variable rate limit applied to it. The `r2.dev` endpoint for your bucket is designed to enable testing: +Managed public bucket access through an `r2.dev` subdomain is not intended for production usage and has a variable rate limit applied to it. The `r2.dev` endpoint for your bucket is designed to enable testing. * If you exceed the rate limit (hundreds of requests/second), requests to your `r2.dev` endpoint will be temporarily throttled and you will receive a `429 Too Many Requests` response. * Bandwidth (throughput) may also be throttled when using the `r2.dev` endpoint.