It's difficult to provide a problematic scripts as the service uses authentifictation, but the point is easy to explain :
The service needs a different "wsa to" address than the one used to submit the request (ie : the one found in the wsdl). It seems that the wsa_to is used for internal routing of the request.
However, the WS-Adressing plugin is extracting the "to" wsa header from the address element.
I've forked and wrote a workaround in wsa.py that relies on the possibility to instanciate the plugin with a wsa_to parameter. Btw I'm not experienced enough to make a pr.
I hope this post could help people facing the same issue and maybe that you would consider adding this feature in the future
I don't know if this is an issue or a feature request, hope I'm in the right place :)
Version of zeep : 4.1.0 The WSDL I'm using : https://gist.github.com/Lapin-Blanc/0e211650a91959082e819a831f07bc04 Documentation for the service is here
It's difficult to provide a problematic scripts as the service uses authentifictation, but the point is easy to explain : The service needs a different "wsa to" address than the one used to submit the request (ie : the one found in the wsdl). It seems that the wsa_to is used for internal routing of the request.
However, the WS-Adressing plugin is extracting the "to" wsa header from the address element.
I've forked and wrote a workaround in wsa.py that relies on the possibility to instanciate the plugin with a wsa_to parameter. Btw I'm not experienced enough to make a pr.
I hope this post could help people facing the same issue and maybe that you would consider adding this feature in the future