Public bug reported: I'm using WSO2 WSF/PHP and I compiled it against this package. I found a bug when using Rampart/C and throwing a WSFault. Another person, François Mireaux, also encountered this bug, he created a patch and send it upstream. Below is his description.
[quote] When axis2_msg_recv_receive_impl detects that response is a SOAP fault, it doesn't send this response but delegates sending to HTTP transport (http_transport_utils.c). But the fault message context created by axis2_engine_create_fault_msg_ctx doesn't copy the base axis2 context contained in input message context, as in axis2_core_utils_create_out_msg_ctx used in normal processing. So Rampart context is not found, Rampart fails to process and SOAP fault is send without security headers. [/quote] For extra information, please see https://issues.apache.org/jira/browse/AXIS2C-1394. I've attached the patch I used. ** Affects: axis2c (Ubuntu) Importance: Undecided Status: New -- Incorrect SOAP fault handling when Rampart is engaged https://bugs.launchpad.net/bugs/431251 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
