[
https://issues.apache.org/jira/browse/CXF-5391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13828822#comment-13828822
]
Sergey Beryozkin commented on CXF-5391:
---------------------------------------
Hi Aki,
you are right, 204 would be returned on a non-SOAP path when the response body
is empty. I guess it might also happen on a SOAP Get Binding path too but I'm
not sure if any of CXF users depends on SOAP GET Binding at all. We can
probably add some property later on to help the HTTP transport to decide that
may be 204 is needed in a given case.
Thanks, Sergey
> Response code is not logged for SOAP responses
> ----------------------------------------------
>
> Key: CXF-5391
> URL: https://issues.apache.org/jira/browse/CXF-5391
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime
> Affects Versions: 2.7.7
> Reporter: Mandy Warren
> Assignee: Aki Yoshida
> Priority: Minor
> Fix For: 3.0.0-milestone1, 2.7.8, 2.6.11
>
>
> If you enable logging through the LoggingIn/OutInterceptors and then send a
> SOAP request through, the response code is not logged.
> ---------------------------
> ID: 2
> Encoding: UTF-8
> Content-Type: text/xml
> The response code is logged fine for rest requests:
> ---------------------------
> ID: 19
> Response-Code: 200
> Content-Type: application/xml
--
This message was sent by Atlassian JIRA
(v6.1#6144)
