Clarify the ability of using Custom Rules to act on truncated payloads

[Vortexmind]

As per title

[pedrosousa]

Hi @Vortexmind

As stated in the documentation, the (plan-dependent) maximum body size only applies to the values of Cloudflare body fields — the origin server will always receive the complete request body, without any truncation.

Truncation info is useful to understand why a given Cloudflare rule with a body field in its expression may not be triggering. For example, if a rule matches a body containing a specific string, it may not match a request if that string does not occur in the piece of the request body that is actually evaluated by Cloudflare (i.e., if it appears in the bytes that got truncated).

Since the truncation of body values in Cloudflare fields has no impact on what the origin server receives, what kind of rule would you create based on truncated body values?

[Vortexmind]

Hi @pedrosousa - thanks for your reply. If I am not misunderstanding, in scenarios where security is paramount I could decide to block a request if the flag shows that truncation has occurred, to avoid a scenario where the offending payload was in the part that was not analyzed. Thanks, Paolo

[pedrosousa]

Got it, thanks for clarifying. I will slightly rephrase your proposal because I had a different understanding from what I read.

[pedrosousa]

Added a suggested edit.

[holopin-bot]

Congratulations @Vortexmind, the maintainer of this repository has issued you a holobyte! Here it is: https://holopin.io/holobyte/cm5qnn7kt00660cmhqgxqzub0

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!