You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Bob Paulin (Jira)" <ji...@apache.org> on 2019/11/20 04:33:00 UTC

[jira] [Created] (CAMEL-14195) [camel-netty-http] - Add additional logging around DecoderResult Failures

Bob Paulin created CAMEL-14195:
----------------------------------

             Summary: [camel-netty-http] - Add additional logging around DecoderResult Failures
                 Key: CAMEL-14195
                 URL: https://issues.apache.org/jira/browse/CAMEL-14195
             Project: Camel
          Issue Type: New Feature
          Components: camel-netty-http
    Affects Versions: 3.0.0.RC3, 2.23.2
            Reporter: Bob Paulin


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:
{code:java}
 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){code}
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



--
This message was sent by Atlassian Jira
(v8.3.4#803005)