[
https://issues.apache.org/jira/browse/CXF-6198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14368863#comment-14368863
] Akitoshi Yoshida commented on CXF-6198: --------------------------------------- I am not sure if this is a real problem. Why 400 needs to be treated differently from other 4xx? The reason why 500 is treated differently by default is that this is the code that is used when returning a SOAP fault. http://www.ws-i.org/profiles/basicprofile-1.1-2004-08-24.html#R1126 But you can always override this behavior (e.g., making SOAP faults returned with other code processed) by setting the following context property at the client. org.apache.cxf.transport.no_io_exceptions > No SOAPFault for HTTP error code 400 > ------------------------------------ > > Key: CXF-6198 > URL: https://issues.apache.org/jira/browse/CXF-6198 > Project: CXF > Issue Type: Bug > Affects Versions: 3.0.3, 2.7.14 > Reporter: Bartosz Baranowski > > Currently on HTTP.500 is accessible as SOAPFAult, 400 cause exception. > https://git-wip-us.apache.org/repos/asf?p=cxf.git;a=blob;f=rt/transports/http/src/main/java/org/apache/cxf/transport/http/HTTPConduit.java;h=836b530ccf8b13f527169a0a4bd54a864762cb88;hb=refs/heads/master#l1566 > https://git-wip-us.apache.org/repos/asf?p=cxf.git;a=blob;f=rt/transports/http/src/main/java/org/apache/cxf/transport/http/HTTPConduit.java;h=7664129271bd6eb72d97a43c250355d5bd99ceb8;hb=refs/heads/2.7.x-fixes#l1558 > https://git-wip-us.apache.org/repos/asf?p=cxf.git;a=blob;f=rt/transports/http/src/main/java/org/apache/cxf/transport/http/HTTPConduit.java;h=836b530ccf8b13f527169a0a4bd54a864762cb88;hb=refs/heads/3.0.x-fixes -- This message was sent by Atlassian JIRA (v6.3.4#6332)
