-
Notifications
You must be signed in to change notification settings - Fork 615
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
SOAP request with XML broken in 0.7.6 #50
Comments
thinking about a solution for this. what about something like this?
appending an exclamation mark to a key would force the value to be escaped. |
That looks like a pretty solid suggestion. This is personal preference but I would switch it. Make the exclamation make not escape anything. ! means "I really really mean it" in terms of what is entered into the field while no ! means "Ok, you can modify it" That is just my personal preference. Either way that fix works for me! |
I returned to version 0.7.5 for the same reason. |
added a fix for this issue to the dev branch (http://github.com/rubiii/savon/commit/76a82c484d1d2fa86e931d340ffa9add96d435b0). going to release the next version soon. ps. implemented the suggestion by rurounijones. everything is escaped by default, but you can mark hash keys with an exclamation mark to have them not escaped. |
released version 0.7.8 which should fix this issue. feedback appreciated :) |
Excellent, I cannot test this until tomorrow but will let you know! |
Looks like I was wrong, I could test it today. As fast as I am concerned it is fixed.I am a happy bunny; thank you, I am not going to close the issue because I didn't test anything to do with Laucode's request (Automatically skip encoding inside CDATA) |
currently savon does not automatically skip encoding inside CDATA tags. that would mean "parsing" every input value, so i postponed it until it's really really needed. thanks for the feedback! |
savon still defaults to escape special characters in a given request hash, but does not escape values for keys that end with an exclamation mark.
My requests have been broken by 0.7.6, rolling back to 0.7.5 fixes the issue. I think it is probably caused by the fix for issue #41. I have to send XML inside a soap field and it is getting escaped which the system at the other end (Which I have no control over) cannot read it.
Here an excerpt from a soap request as sent by 0.7.6 (Captured by wireshark) - BROKEN
And here is the same XML as sent by 0.7.5 - WORKING
Maybe we need to be able to set a setting to tell Savon to escape or not?
The text was updated successfully, but these errors were encountered: