-
-
Notifications
You must be signed in to change notification settings - Fork 591
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Variable not written correctly in SOAP body #894
Comments
So, duration objects must be of the type
Fair enough. But this could be in the documentation .. or maybe it is there already and its just me? |
I did not know this as well or see it in the documentation. Thanks for your help @elsampsa. I spent quite some time wondering why the format would work fine in other platforms but not with zeep. |
Hi! I'm trying to get events using PullMessages method. Here is a code: zeep 3.4.0 And I've got output with error 500 the parameter value is illegal. I googled this problem and used timestamp with isodate lib (timestamp is ok), but still have this problem. What else can be a reason of this error?
Thanks in advance, |
Hi,
I'm getting an erroneous value into the SOAP message body. The "Timeout" attribute should have value "PT1S", but instead, a mysterious string "P%P" appears.
I've confirmed this with zeep in verbose mode and with wireshark.
Zeep version: 3.2.0
Here is the script as per your debugging template:
.. so it seems that your debugging template does not work if the the WSDL file does not have a default service.
Please do confirm this .. !
Here is also a more complex version. However for this one you need an IP camera:
A related SO question : https://stackoverflow.com/questions/53989525/using-onvif-pullpoint-services-with-zeep
The text was updated successfully, but these errors were encountered: