-
Bug
-
Resolution: Unresolved
-
Major
-
3.15.0.GA
-
None
-
False
-
-
False
-
-
-
-
0
A customer has noticed that when posting pdf files on a Quarkus Camel route using netty-http that small files work, but larger ones result in "HTTP/1.1 413 Request Entity Too Large".
This happens when they set chunkedMaxContentLength with a query parameter. The query parameter is ignored and the default 1048576 applied.
When they set chunkedMaxContentLength in configuration they following code works:
@Singleton @Named(HttpDestinationNettyHttpComponent.HTTP_DESTINATION_NETTY_HTTP_CONSUMER) public class HttpDestinationNettyHttpComponent extends NettyHttpComponent { public static final String HTTP_DESTINATION_NETTY_HTTP_CONSUMER = "httpDestinationNettyHttpConsumer"; @Inject public HttpDestinationNettyHttpComponent(Config config) { super(); NettyHttpConfiguration nettyHttpConfiguration = new NettyHttpConfiguration(); nettyHttpConfiguration.setChunkedMaxContentLength(config.getValue("chunkedMaxContentLength", Integer.class)); this.setConfiguration(nettyHttpConfiguration); } }
Is this a bug, or it's working as expected?
I see mention of chunkedMaxContentLength as being a query parameter here:
https://docs.redhat.com/en/documentation/red_hat_fuse/7.5/html/apache_camel_component_reference/netty4-http-component
But maybe within quarkus, it can only be set through configuration?