Closed orette closed 6 years ago
Hi @orette,
Thanks for reporting!
This is a known issue which has been adressed in https://github.com/phpro/soap-client/pull/131. SOAP 1.2 does not require a SOAPAction header and uses the Content-Type header instead. This PR hasn't been completed yet, but you could use the code in there or use SOAP 1.1 instead if it's available for your service.
Currently there is no middleware for WS-ReliableMessaging. Feel free to add one :)
Thanks for the response @veewee.
SOAP 1.1 isn't an option for me sadly. I tested the code from the PR #131 , and the error went away, i'm going to dig a little deeper to see if the resulting request is formatted the way the web service i'm using expects it to be.
I'm trying to use this client on a WCF service that has
WS-Addressing
andWS-ReliableMessaging
enabled. The plan is to use WsaMiddleware and to manually handle WS-ReliableMessaging as i have not seen a middleware or client that handles it.I have however ran into this error
PHP Notice: Undefined offset: 0 in /client/vendor/phpro/soap-client/src/Phpro/SoapClient/Middleware/WsaMiddleware.php on line 31
and would just like to be sure that it's not as a result of misconfigurartion. After going through the code, it seems the middleware is expecting the headerSOAPAction
to be an array with at least one value, but it is actually empty. Line 31:$wsa->addAction($request->getHeader('SOAPAction')[0]);
. Is this a bug or did i miss some part of the configuration?I also have two other questions:
WS-ReliableMessaging
?My Config:
My Client: