You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/08/24 08:33:20 UTC

[jira] [Commented] (CAMEL-8072) Netty Http Server should close the channel once it return an error message

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

ASF GitHub Bot commented on CAMEL-8072:
---------------------------------------

GitHub user YoshikiHigo opened a pull request:

    https://github.com/apache/camel/pull/1136

    Followup to CAMEL-8072

    This is a small followup to CAMEL-8072, which was fixed in e9dded769bff8e060c64e62c962cd552d24d4c70.
    
    Yoshiki, Shinpei, Hideaki, and Mei

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/YoshikiHigo/camel fix04

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/camel/pull/1136.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1136
    
----
commit f2011248028f6b2250686a6123b1f7f5f31d8d40
Author: Yoshiki Higo <yo...@gmail.com>
Date:   2016-08-24T08:15:59Z

    Followup to CAMEL-8072

----


> Netty Http Server should close the channel once it return an error message
> --------------------------------------------------------------------------
>
>                 Key: CAMEL-8072
>                 URL: https://issues.apache.org/jira/browse/CAMEL-8072
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-netty-http, camel-netty4-http
>    Affects Versions: 2.13.3, 2.14.0
>            Reporter: Willem Jiang
>            Assignee: Willem Jiang
>             Fix For: 2.13.4, 2.14.1, 2.15.0
>
>
> It's a common practice that http server close the connection once it send the error message to the client.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)