JiriOndrusek opened a new pull request, #27569: URL: https://github.com/apache/camel/pull/27569
# Description [CAMEL-25463](https://issues.apache.org/jira/browse/CAMEL-25463) A stream or file body was read whole before `maxDocumentSize` was checked. It is now read only one byte (media) or character (text) past the cap, enough to refuse it. - The cap is checked before the blank check, since a capped read sees only the start. A body over the cap now fails even if all blank; it answered `EMPTY` before. - With a cap, a `File` or `Path` body decodes strictly, like a file-consumer body. - Docs: stream caching (on by default) still reads a stream whole before the endpoint, into memory unless it spools, so limit the size at the consumer too. # Target - [x] I checked that the commit is targeting the correct branch (Camel 4 uses the `main` branch) # Tracking - [x] If this is a large change, bug fix, or code improvement, I checked there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL) filed for the change (usually before you start working on it). # Apache Camel coding standards and style - [x] I checked that each commit in the pull request has a meaningful subject line and body. - [x] I have run `mvn clean install -DskipTests` locally from root folder and I have committed all auto-generated changes. # AI-assisted contributions - [x] If this PR includes AI-generated code, commits have proper co-authorship attribution (e.g., `Co-authored-by` trailers) and the PR description identifies the AI tool used. _Claude Code on behalf of @JiriOndrusek_ 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
