I saw that the usage of gsoap-plugin resets in some way the field error in the SOAP structure.
When authentication is disabled (gsoap-plugin not registered) I observed some different values of SOAP->error:
SOAP_EOF (when connection takes longer than what specified in SOAP->send/recv_timeout)
SOAP_TCP_ERROR (when try to connect to an unknown host, not allowed TCP port, etc.)
SOAP_CLI_FAULT
SOAP_SVR_FAULT
SOAP_FAULT
etc. etc.
When using the gsoap-plugin, all the possible SOAP error codes seem collapsed into "1" (SOAP_CLI_FAULT).
This forces me to discern a connection timeout or a connection refused by matching the fault strings (that is not very nice) in order to take the proper action.
Is this behavior known and wanted ? or is it a bug in the gsoap-plugin ?
If wanted, is there another way to recover that precious error code ?
Original submission by Alvise:
I saw that the usage of gsoap-plugin resets in some way the field error in the SOAP structure. When authentication is disabled (gsoap-plugin not registered) I observed some different values of SOAP->error:
When using the gsoap-plugin, all the possible SOAP error codes seem collapsed into "1" (SOAP_CLI_FAULT).
This forces me to discern a connection timeout or a connection refused by matching the fault strings (that is not very nice) in order to take the proper action.
Is this behavior known and wanted ? or is it a bug in the gsoap-plugin ?
If wanted, is there another way to recover that precious error code ?