[CAMEL-14195] [camel-netty-http] - Add additional logging around DecoderResult Failures

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.23.2, 3.0.0.RC3
• Fix Version/s: 3.0.0
• Component/s: camel-netty-http
• Estimated Complexity: Unknown
• Assignee: Claus Ibsen
• Reporter: Bob Paulin
• Created: 20/Nov/19 04:32
• Updated: 22/Nov/19 13:15
• Resolved: 22/Nov/19 08:43

Description

When the Camel Netty Http component receives a header that exceeds it's
maxHeaderSize the
org.apache.camel.component.netty.http.handlers.HttpServerChannelHandler
simply logs that a message was received at DEBUG level:

 2019-11-19T19:34:02,418 | DEBUG | Camel (camel-2) thread #189 -
NettyEventExecutorGroup | NettyHttpConsumer | 95 -
org.apache.camel.camel-core - 2.22.3 | Message received:
HttpObjectAggregator$AggregatedFullHttpRequest(decodeResult:
failure(io.netty.handler.codec.TooLongFrameException: HTTP header is
larger than 8192 bytes.), version: HTTP/1.1, content: EmptyByteBufBE)

This the request is allowed to proceed to code upstream which
unfortunately leads the developer to believe that there is nothing wrong
with the request.

Determine to add error level logging in these cases.

See for discussion: https://lists.apache.org/thread.html/1b991732c0e6f0420220a4329adb64438e7e17142d0799b90d15030a@%3Cdev.camel.apache.org%3E

Issue Links

• links to: GitHub Pull Request #3358