Skip to content

Support for limits on input stream processing in WebFlux codecs  #23884

Closed
@rstoyanchev

Description

@rstoyanchev

While a proxy, or the underlying server, or a WebFilter can be used to enforce general limits on the size of server request input, it would be helpful for Decoder and HttpMessageReader implementations to expose configurable limits too, because codecs in WebFlux can parse asynchronously and pass one object one at a time to the application, as a stream. That means the overall request input stream may be infinite, and it's the input per streamed object that should be limited.

Metadata

Metadata

Assignees

Labels

in: webIssues in web modules (web, webmvc, webflux, websocket)status: backportedAn issue that has been backported to maintenance branchestype: enhancementA general enhancement

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions