diff --git a/src/content/docs/fundamentals/reference/connection-limits.mdx b/src/content/docs/fundamentals/reference/connection-limits.mdx
index e1f7861050a9e14..6aeb0b78bc4dba4 100644
--- a/src/content/docs/fundamentals/reference/connection-limits.mdx
+++ b/src/content/docs/fundamentals/reference/connection-limits.mdx
@@ -42,3 +42,15 @@ Some TCP connections can be customized for Enterprise customers. Reach out to yo
 Cloudflare maintains keep-alive connections to improve performance and reduce cost of recurring TCP connects in the request transaction as Cloudflare proxies customer traffic from its global network to the site's origin server.
 
 Ensure HTTP keep-alive connections are enabled on your origin. Cloudflare reuses open TCP connections up to the `Proxy Idle Timeout` limit after the last HTTP request. Origin web servers close TCP connections if too many are open. HTTP keep-alive helps avoid connection resets for requests proxied by Cloudflare.
+
+## Request limits
+
+URLs have a limit of 16 KB. Request headers have a total limit of 32 KB, but each header is limited to 16 KB.
+
+## Response limits
+
+Response headers observe a total limit of 32 KB, but each header is limited to 16 KB.
+
+## Cache limits 
+
+Refer to the [Cache documentation](/cache/concepts/default-cache-behavior/#customization-options-and-limits) for more details about the max upload size and the cacheable file size limits.