savon is stripping ?SOAP off the end of WSDL locations #21
Comments
|
FYI I fixed this in my fork and sent a pull request. When making the soap call, if the URI had a query portion, it was being ignored |
|
fixed this problem in the current dev branch so it will be included in the next release: i'll leave the issue open until the fix is released. |
|
released version 0.7.2 including a fix for this issue. |
rubiii
pushed a commit
that referenced
this issue
Jun 3, 2013
When the resolver gets an erroneous response (such as a 404), raise an HTTPError with: - `message` set to "Error: 404" (or whatever the code is) - `response` set to the original response object
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
given a wsdl that has a location as follows (scrubbed)
<soap:address location="https://somthing.something.com/incident.do?SOAP"/>
a client instance wsdl.soap_endpoint will return the correct value however when you make a soap call, savon is trimming off the ?SOAP. I was getting odd 302 errors and when I ran it through Charles it showed the trimmed URI
The text was updated successfully, but these errors were encountered: