Skip to content

fix(filter): keep multipart form parsing with body scanning on, add guard.enabled - #39

Merged
rennf93 merged 4 commits into
masterfrom
fix/multipart-body-scan-and-enable-property
Oct 17, 2026
Merged

rennf93 merged 4 commits into
masterfrom
fix/multipart-body-scan-and-enable-property

Conversation

@rennf93

@rennf93 rennf93 commented Oct 17, 2026

Copy link
Copy Markdown
Member

Closes #37
Closes #38

I fixed multipart uploads losing their parts when detection body scanning is on. The container parses parts and urlencoded parameters from its own input, so the guard now scans a body rebuilt from the container-parsed parts (bounded by the inspect cap, file parts stay in the container spool) and merges urlencoded body parameters from its cache. The same cause made @RequestParam on urlencoded forms come back empty.

I also added guard.enabled (default true) so an app can switch the whole auto-configuration off. I added tests for both, README and installation docs, and a CHANGELOG entry under Unreleased.

…body scanning on (#37)

The guard reads the body for detection, but the container parses parts and parameters from its own input and never saw the replay. Multipart is now scanned from the container-parsed parts and urlencoded body parameters are merged from the cache.
…38)

Defaults to true. With false no guard bean, filter or properties binding is created.
@github-actions github-actions Bot added the documentation Docs site, README, CHANGELOG, license files label Oct 17, 2026
@rennf93
rennf93 merged commit 561635d into master Oct 17, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Docs site, README, CHANGELOG, license files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add guard.enabled property to switch the auto-configuration off Multipart upload loses its parts when detection body scanning is on

1 participant