[
https://issues.apache.org/jira/browse/CAMEL-14069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16958472#comment-16958472
]
Zheng Feng commented on CAMEL-14069:
------------------------------------
[~urken] I doubt that the camel-netty4-http producer could support the expect
100-continue which is sending the request with the header "EXPECT:
100-continue" and waiting for the response "HTTP/1.1 100 Continue" and then
sending the body. Now the client only sends the request with the body at once
even if we set the EXPECT header.
By the way, I raise the PR to ignore the "100 Continue" response in the client
handlers based on your fix.
> 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
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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)
