[jboss-jira] [JBoss JIRA] (WFLY-11565) WildFly Server Adds Transfer Encoding Chunk Header to the HttpResponse with status code 204

[jaikiran pai (Jira)]

    [ https://issues.jboss.org/browse/WFLY-11565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13709405#comment-13709405 ] 

jaikiran pai commented on WFLY-11565:
-------------------------------------

FWIW - Like I noted way back in this JIRA, there's no development happening on WildFly community 9.x edition. Even if it was a bug in that version, I don't see a release happening with a fix for the issue. You will have to really test your application against WildFly recently released version and see if it's reproducible there. Whatever other issues that you run into while porting the application to that newer version will have to be addressed separately.

If you do need timely and more ETA based responses, JBoss EAP https://developers.redhat.com/products/eap/overview/ is what you will have to buy a subscription for. WildFly community versions are volunteer driven and although you will receive help on issues you run into, it's mostly volunteer driven and depends on the time and efforts that the community can spare.

> WildFly Server Adds Transfer Encoding Chunk Header to the HttpResponse with status code 204
> -------------------------------------------------------------------------------------------
>
>                 Key: WFLY-11565
>                 URL: https://issues.jboss.org/browse/WFLY-11565
>             Project: WildFly
>          Issue Type: Bug
>    Affects Versions: 9.0.0.Final
>            Reporter: Deepak Sahu
>            Assignee: Bartosz Baranowski
>            Priority: Major
>         Attachments: API.war
>
>
> I am using WildFly Server 9.0.0 Final, Javax ws, Jersey for developing Rest APIs. For all the responses whose httpStatus code is 204, the wildfly server adds Transfer encoding Chunked in the response header, which is not correct as per the Rest Standards. Because of this behavior some of the RestAPI clients hang, as they keep waiting for the response (which is not at all there).
> To verify the issue, I tried the same with Springboot instead of deploying the war in WildFly and the Response Header was not added with Transfer Encoding Chuncked.
> Let me know if some other information is required to fix this issue, if this is already fixed is there any patch for this issue. 



--
This message was sent by Atlassian Jira
(v7.12.1#712002)