[
https://issues.jboss.org/browse/WFLY-11565?page=com.atlassian.jira.plugin...
]
Bartosz Baranowski commented on WFLY-11565:
-------------------------------------------
[~soumya.khedagi] & [~dsahu030686] - sorry, I was occupied with other tasks. Right now
it does deploy in latest WFLY.
{quote}
baranowb@drone-1-1:~$ curl
http://localhost:7354/restApis/test?id=10
curl: (7) Failed to connect to localhost port 7354: Connection refused
baranowb@drone-1-1:~$ netstat -lon | grep 7354
baranowb@drone-1-1:~$
{quote}
or
{quote}
localhost refused to connect.
Search Google for localhost 7354 rest Apis test
ERR_CONNECTION_REFUSED
{quote}
Also, as Jaikiran said - there is no guarantee for older versions.
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)