Skip to content

Conversation

@dpolaske-cloudflare
Copy link
Contributor

https://jira.cfdata.org/browse/CUSTESC-52250

Summary

Screenshots (optional)

Documentation checklist

  • The documentation style guide has been adhered to.
  • If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.
  • Files which have changed name or location have been allocated redirects.

Copy link
Contributor

@windsurf-bot windsurf-bot bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 To request another review, post a new comment with "/windsurf-review".

## How it works

By default, Cloudflare **streams** traffic data, meaning that each packet is sent as it becomes available. This can improve the delivery of large files. However, this streaming behavior only applies to dynamic traffic; cacheable traffic is buffered and this behavior cannot be changed.
By default, Cloudflare **streams** traffic data, meaning that each packet is sent as it becomes available. This can improve the delivery of large files. However, this streaming behavior only applies to dynamic traffic; cacheable traffic (that is, *any* status noted in [Cloudflare cache responses](https://developers.cloudflare.com/cache/concepts/cache-responses/) with the exception of **DYNAMIC**) is buffered and this behavior cannot be changed.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The added clarification is helpful, but consider using consistent formatting for emphasis. Currently you're using both italics and bold in the same parenthetical. Consider using bold formatting consistently:

Suggested change
By default, Cloudflare **streams** traffic data, meaning that each packet is sent as it becomes available. This can improve the delivery of large files. However, this streaming behavior only applies to dynamic traffic; cacheable traffic (that is, *any* status noted in [Cloudflare cache responses](https://developers.cloudflare.com/cache/concepts/cache-responses/) with the exception of **DYNAMIC**) is buffered and this behavior cannot be changed.
By default, Cloudflare **streams** traffic data, meaning that each packet is sent as it becomes available. This can improve the delivery of large files. However, this streaming behavior only applies to dynamic traffic; cacheable traffic (that is, **any** status noted in [Cloudflare cache responses](https://developers.cloudflare.com/cache/concepts/cache-responses/) with the exception of **DYNAMIC**) is buffered and this behavior cannot be changed.

@hyperlint-ai
Copy link
Contributor

hyperlint-ai bot commented Jun 9, 2025

Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment.

We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally.


PR Change Summary

Clarified the behavior of cacheable traffic in the response buffering documentation.

  • Updated the explanation of streaming behavior for cacheable traffic.
  • Specified that only non-DYNAMIC cache responses are buffered.

Modified Files

  • src/content/docs/network/response-buffering.mdx

How can I customize these reviews?

Check out the Hyperlint AI Reviewer docs for more information on how to customize the review.

If you just want to ignore it on this PR, you can add the hyperlint-ignore label to the PR. Future changes won't trigger a Hyperlint review.

Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add hyperlint-ignore to the PR to ignore the link check for this PR.

@dcpena dcpena enabled auto-merge (squash) June 11, 2025 17:07
@dcpena dcpena merged commit badf70d into cloudflare:production Jun 11, 2025
5 checks passed
@workers-devprod workers-devprod added the contribution [Holopin] Recognizes a docs contribution, big or small label Jun 11, 2025
@holopin-bot
Copy link

holopin-bot bot commented Jun 11, 2025

Congratulations @dpolaske-cloudflare, the maintainer of this repository has issued you a holobyte! Here it is: https://holopin.io/holobyte/cmbs7saz1392907kzh3hxrich

This badge can only be claimed by you, so make sure that your GitHub account is linked to your Holopin account. You can manage those preferences here: https://holopin.io/account.
Or if you're new to Holopin, you can simply sign up with GitHub, which will do the trick!

sdnts pushed a commit to sdnts/cloudflare-docs that referenced this pull request Jul 24, 2025
* Update response-buffering.mdx

https://jira.cfdata.org/browse/CUSTESC-52250

* Tiny formatting fix

---------

Co-authored-by: Denise Peña <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

contribution [Holopin] Recognizes a docs contribution, big or small product:network size/xs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants