[ 
https://issues.apache.org/jira/browse/CAMEL-14069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16957667#comment-16957667
 ] 

Zheng Feng commented on CAMEL-14069:
------------------------------------

I came across the CAMEL-7462 and it seems this similar issue had been fixed in 
the camel-netty-http. I just kept investigating and the 
[NettyHttpClientExpectContinueTest|https://github.com/apache/camel/blob/camel-2.x/components/camel-netty4-http/src/test/java/org/apache/camel/component/netty4/http/NettyHttpClientExpectContinueTest.java#L25]
 is just ignored and marked with "TODO Fix". So I assume this could be a bug 
rather than an improvement.

> netty4-http - Add logic to handle http 100-Continue
> ---------------------------------------------------
>
>                 Key: CAMEL-14069
>                 URL: https://issues.apache.org/jira/browse/CAMEL-14069
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-netty4, camel-netty4-http
>    Affects Versions: 2.24.0
>            Reporter: Göran Erkstam
>            Assignee: Zheng Feng
>            Priority: Major
>             Fix For: 3.0.0, 2.25.0
>
>         Attachments: ClientChannelHandler.java, HttpClientChannelHandler.java
>
>
> 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
>  



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

Reply via email to