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.