From 43e2fcaef12af5bb47bc0842948351a395d049e0 Mon Sep 17 00:00:00 2001 From: Angela Costa Date: Thu, 28 Aug 2025 12:06:12 +0100 Subject: [PATCH 1/2] Adds info about HTTP methods --- .../docs/fundamentals/concepts/traffic-flow-cloudflare.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/content/docs/fundamentals/concepts/traffic-flow-cloudflare.mdx b/src/content/docs/fundamentals/concepts/traffic-flow-cloudflare.mdx index 7698514304ab539..4e0a7eec489dca4 100644 --- a/src/content/docs/fundamentals/concepts/traffic-flow-cloudflare.mdx +++ b/src/content/docs/fundamentals/concepts/traffic-flow-cloudflare.mdx @@ -17,6 +17,10 @@ For example, you may not always want the direct traffic because it can come from If you want to protect your traffic and ensure it travels efficiently, you need to configure Cloudflare to be in front of whatever you are trying to protect, such as your application, service, or server. How you put your resources behind Cloudflare's network will depend on the type of traffic and how you want to control it. +:::note +Cloudflare supports all standard HTTP methods, with the exception of `CONNECT`, `TRACE`, and `PURGE`, which are restricted. Requests using unsupported methods will not be proxied through Cloudflare's network. +::: + ## On-ramp and off-ramp traffic Traffic that enters Cloudflare's network is referred to as "on-ramping," and traffic that exits Cloudflare's network is referred to as "off-ramping." You may also know this as ingress and egress or "routing your traffic" through a network. From ad0e48f1a51b03887c55e7ca4f99fa0565f8d0bd Mon Sep 17 00:00:00 2001 From: Angela Costa Date: Thu, 28 Aug 2025 14:21:40 +0100 Subject: [PATCH 2/2] Updates after review --- .../docs/fundamentals/concepts/traffic-flow-cloudflare.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/fundamentals/concepts/traffic-flow-cloudflare.mdx b/src/content/docs/fundamentals/concepts/traffic-flow-cloudflare.mdx index 4e0a7eec489dca4..523b749e6b4742c 100644 --- a/src/content/docs/fundamentals/concepts/traffic-flow-cloudflare.mdx +++ b/src/content/docs/fundamentals/concepts/traffic-flow-cloudflare.mdx @@ -18,7 +18,7 @@ For example, you may not always want the direct traffic because it can come from If you want to protect your traffic and ensure it travels efficiently, you need to configure Cloudflare to be in front of whatever you are trying to protect, such as your application, service, or server. How you put your resources behind Cloudflare's network will depend on the type of traffic and how you want to control it. :::note -Cloudflare supports all standard HTTP methods, with the exception of `CONNECT`, `TRACE`, and `PURGE`, which are restricted. Requests using unsupported methods will not be proxied through Cloudflare's network. +Cloudflare supports all HTTP methods, with the exception of `CONNECT`, `TRACE`, and `PURGE`, which are restricted. Requests that use restricted methods are not proxied through Cloudflare's network. Note that other Cloudflare products may apply different restrictions on HTTP methods, and behavior can vary depending on the service. ::: ## On-ramp and off-ramp traffic