You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Göran Erkstam (Jira)" <ji...@apache.org> on 2019/10/15 11:43:00 UTC

[jira] [Updated] (CAMEL-14069) netty4-http - Add logic to handle http 100-Continue

     [ https://issues.apache.org/jira/browse/CAMEL-14069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Göran Erkstam updated CAMEL-14069:
----------------------------------
    Description: 
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.

I the project I working in 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

 

> 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
>            Reporter: Göran Erkstam
>            Priority: Major
>         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.
> I the project I working in 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)