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

[Soumya Khedagi (Jira)]

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

Soumya Khedagi commented on WFLY-11565:
---------------------------------------

Hey [~baranowb], we are really looking forward for your response. We have 3-4 tickets submitted for this issue. Could you please let us know the ETA for this ticket? Looks like nobody is looking into this issue. The status is still Open. 

> 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)