Recording of HTTP messages is blocked in case of wrong HTTP Frame

When recording HTTP message (in sub-pipeline), netty aggregator and codec are used to parse HTTP messages. In case of frame error (such as Content-Length too big), even if the aggregator detects it, netty will block the message when parsing it, waiting for the end of the frame.

Ultimately, the channel will be closed (sub-pipeline time-out and/or client timeout that closes the connection), then Netty will raise the exception (closing channel while still aggregating). In that situation, the information is print in Proxy logs and not recorded. That is lost to the user and that is not helpful to debug/understand what happen.