[
https://issues.apache.org/jira/browse/CAMEL-14069?focusedWorklogId=333060&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-333060
]
ASF GitHub Bot logged work on CAMEL-14069:
------------------------------------------
Author: ASF GitHub Bot
Created on: 24/Oct/19 04:13
Start Date: 24/Oct/19 04:13
Worklog Time Spent: 10m
Work Description: zhfeng commented on pull request #3279: CAMEL-14069
Update to ignore the 100-Continue response and continue to
URL: https://github.com/apache/camel/pull/3279
wait for the answer
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 333060)
Time Spent: 20m (was: 10m)
> 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: 20m
> 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)
