-
Notifications
You must be signed in to change notification settings - Fork 616
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
SOAPAction matching errors after upgrade to v2.15.x #1016
Comments
Here's a version of Savon that works fine. Gemfile:
Gemfile.lock:
|
Thanks for the perfect repro. i ran this with savon 2.14.0
later versions:
note that These changes don't appear to be in savon, but rather in wasabi 3.x to 5.x - here is the diff: savonrb/wasabi@v3.8.0...v5.0.3 |
mind checking if this fixes the issue?
|
Yep - happy to confirm that adding that to the Gemfile makes everything work properly again. |
going to get a few more data points to check regressions / confirm fixes and then ill cut a release in next few days |
I can confirm that after an upgrade to v2.15.0 I also get login errors to a SOAP endpoint, and that the above 'wasabi' fix fixes the login errors. |
Bug report
Upon upgrade from Savon v2.14.0 to Savon v2.15.0, I start getting error messages. Nothing else has changed on my end (the client). The issue is also present in Savon v2.15.1 as well.
Current behavior:
I get this error where previously there was none:
(soap:Client) SOAPAction shall match 'uri#method' if present (got 'urn:sympasoap#login', expected 'urn:sympasoap#loginRequest' (Savon::SOAPFault)
Steps to reproduce current behavior:
Gemfile:
Gemfile.lock:
Script (run inside
bundle exec irb
):The actual email/password credentials are unimportant. The error can be reproduced with any values in the message. If you do want to test in totality then you go to https://lists.cam.ac.uk/sympa/firstpasswd and create an account.
Expected behavior:
No error thrown (unless you've used nonexistent credentials, in which case an authentication error is expected).
System information:
The text was updated successfully, but these errors were encountered: