Skip to content

Update response-buffering.mdx #26054

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: production
Choose a base branch
from
Open

Update response-buffering.mdx #26054

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions src/content/docs/network/response-buffering.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,8 @@ By default, Cloudflare **streams** traffic data, meaning that each packet is sen

If your domain sends many small packets, however, it might be faster to **buffer** the file. This approach waits to send the full file until all packets are ready, preventing a client browser from having to re-assemble packets.

Additionally, buffering is expected behavior when other Cloudflare features are enabled that require inspection of the response. Cloudflare must buffer the response to read and potentially change the response body before delivery. Common features that necessitate response buffering include compression rules, HTML modifications (like Email Obfuscation or Rocket Loader), WAF/Rate Limiting rules that inspect response content, etc.

## Enable Response Buffering

<Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
Expand Down