oscerd opened a new issue, #9055:
URL: https://github.com/apache/camel-quarkus/issues/9055
`extensions/servlet/deployment/.../ServletProcessor.java:113`
```java
MultipartConfig multipartConfig = servletConfig.multipart();
if (multipartConfig != null) {
builder.setMultipartConfig(new MultipartConfigElement(...));
}
```
`CamelServletConfig` is a `@ConfigMapping` interface and `multipart()` is a
non-`Optional` nested group, so SmallRye always materialises it with its
`@WithDefault` values. The guard can never be false, and multipart handling is
applied to every Camel servlet whether or not the deployer asked for it.
The defaults it applies are unbounded — `CamelServletConfig.java:167,176`:
```java
@WithDefault("-1")
long maxFileSize();
@WithDefault("-1")
long maxRequestSize();
```
**Suggested fix**
Apply the multipart configuration only when the deployer actually configured
it — e.g. make the group `Optional`, or compare against the defaults before
wiring it in.
Related: #5830 (inconsistent response code when a multipart body exceeds the
limit) touches the same wiring.
--
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]
