When using netty4-http as a client we have a problem when the server side answers with a http 100-Continue. We expected the client to handle that internally and continue the call but it's actually returning http 100.
This is handled by Nettys own channel handlers but since the Camel HttpClientChannelHandler/ClientChannelHandler stop waiting when a http 100-Continue arrives it doesn't help.
In the project I'm working with we made a custom ClientInitilizer and made some small changes in the HttpClientChannelHandler and ClientChannelHandler that just "ignores" the http 100-Continue when it arrives to solve this issue.
See the attached files to see our solution