Skip to content

Commit 9a1dfc7

Browse files
angelampcostanevikashah
authored andcommitted
[Fundamentals] Adds info about HTTP methods (#24758)
* Adds info about HTTP methods * Updates after review
1 parent 184c3a4 commit 9a1dfc7

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

src/content/docs/fundamentals/concepts/traffic-flow-cloudflare.mdx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,10 @@ For example, you may not always want the direct traffic because it can come from
1717

1818
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.
1919

20+
:::note
21+
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.
22+
:::
23+
2024
## On-ramp and off-ramp traffic
2125

2226
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.

0 commit comments

Comments
 (0)