CF-Incidents Rules - Control request and response body buffering in Configuration Rules

[ENF News Bot]

You can now control how Cloudflare buffers HTTP request and response bodies using two new settings in Configuration Rules.

Request body buffering​

https://developers.cloudflare.com/changelog/rss/#request-body-buffering

Controls how Cloudflare buffers HTTP request bodies before forwarding them to your origin server:

Mode	Behavior
Standard (default)	Cloudflare can inspect a prefix of the request body for enabled functionality such as WAF and Bot Management.
Full	Buffers the entire request body before sending to origin.
None	No buffering — the request body streams directly to origin without inspection.

Response body buffering​

https://developers.cloudflare.com/changelog/rss/#response-body-buffering

Controls how Cloudflare buffers HTTP response bodies before forwarding them to the client:

Mode	Behavior
Standard (default)	Cloudflare can inspect a prefix of the response body for enabled functionality.
None	No buffering — the response body streams directly to the client without inspection.

Caution


Setting body buffering to None may break security functionality that requires body inspection, including the Web Application Firewall (WAF) and Bot Management. Ensure that any paths where you disable buffering do not require security inspection.

API example​

https://developers.cloudflare.com/changelog/rss/#api-example

{
  "action": "set_config",
  "action_parameters": {
    "request_body_buffering": "standard",
    "response_body_buffering": "none"
  }
}

For more information, refer to Configuration Rules.

Continue reading...