Feature Requests item #2996445, was opened at 2010-05-04 11:08
Message generated for change (Settings changed) made by sjaakvs
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=350976&aid=2996445&group_id=976

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
>Category: libcurl
>Group: download
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Sjaak (sjaakvs)
Assigned to: Nobody/Anonymous (nobody)
Summary: Support for HTTP SOAP Fault

Initial Comment:
SOAP stands for Simple Object Access Protocol.
SOAP over HTTP(S) is send as a POST text/xml with a SOAPAction header field.

libcurl works fine for this, except when setting the option FAILONERROR. Then the SOAP Fault document is passedto the client.

This is because the SOAP Fault is defined to be a HTTP code 500 "Internal server error". The (Soap Fault) text/xml document that MUST follow should explain the error reason in more detail. So for SOAP over HTTP code 500 is NOT an HTTP error but more as 'Error document follows'.

Adjustment of libcurl is needed to pass the SOAP Fault document as a fault document is needed. Regardless of FAILONERROR.
Currently I modified http.c for this so that a HTTP POST resulting in HTTP code 500 just continues. It's better to also test for the SOAPAction request header. Or make a specific/generic switch for SOAP so that the transport layer is prepared, since SOAP can be passed over other protocols as well.

More details in: http://www.w3.org/TR/2000/NOTE-SOAP-20000508/ (section 6.1.1 & 6.2 & 4.4)

----------------------------------------------------------------------

>Comment By: Sjaak (sjaakvs)
Date: 2010-05-04 11:09

Message:
Forgot to set category

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=350976&aid=2996445&group_id=976
Received on 2010-05-04