-
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
Escape special characters (e.g. &) for XML requests #41
Comments
the problem here is, that the ampersand inside the password string is not escaped. will get this fixed with the next release. |
fix added to the dev branch: http://github.com/rubiii/savon/commit/86ac84ba99813d5822d3883ac3d695b6827a8607 |
released version 0.7.6 containg a fix for this problem. please update. |
Is there an option to turn off escaping of special characters? Can we add one if not? There are wsdls whose elements have processContents="lax". This is typically used when the desired message content is raw xml which is not escaped and in read directly into the system/api. |
Is there any chance to turn off that escaping? I have XML in string, which breaks when escaped. I also put other data into the request as a hash, so manually typing all this into soap.xml would not be preferable. If you use first soap.body and then soap.xml the whole body is overwritten.. See below a shortened example. soap.body = {
"Example" => {
"Foo" => "bar",
"Bar" => "foo"
},
"XMLString" => xml_string
} |
@vkoivula there's a way to prevent escaping of specific hash values by appending an apostroph to the key. |
@rubiii Thanks. |
Does this method of escape preventing actually work in Version 2? It seems here https://github.com/savonrb/savon/blob/version2/lib/savon/qualified_message.rb#L22 (rdb:1) Gyoku.xml_tag("requestXml!", :key_converter => @key_converter).to_s
"requestXml" and thus escaping always happens. |
this does not work
this does
(reported by luqman)
The text was updated successfully, but these errors were encountered: