Savon Files

Restore WS-Addressing headers and fix :wsse_signature resolution

Fixed

• WS-Addressing headers are populated from the WSDL again (#1057). With use_wsa_headers: true and no explicit :soap_action or :endpoint, Savon emitted empty <wsa:Action xsi:nil="true"/> and <wsa:To xsi:nil="true"/> elements instead of the operation's SOAPAction and service endpoint. Up to 2.16.0 those values were populated as a side effect of building the HTTP request. The 2.17.0 transport refactor removed that step.
• A global :host override no longer rewrites the WSDL's endpoint. Resolving the request endpoint with :host set replaced host and port of the parsed WSDL address in place, visible as a permanently changed client.wsdl.endpoint after the first call. Endpoint and SOAPAction resolution moved into Savon::EffectiveOptions, which applies the override to a copy and never touches the WSDL document.
• A local :wsse_signature no longer crashes when set to false. Passing wsse_signature: false to a call raised NoMethodError: undefined method 'have_document?' for false while building the WSSE header. The envelope builder and the SOAP header also resolved the option with different rules, so they could disagree on which signature applies. Both now read it through Savon::EffectiveOptions, the one place that resolves options settable in both the global and the local scope. A falsy local :wsse_signature falls back to the global one. Setting a signature object in either scope is unaffected.

Deprecated

• Savon::Builder::WSA_NAMESPACE. WS-Addressing emission moved into Savon::Addressing, which owns the namespace as Savon::Addressing::NAMESPACE. The constant on Savon::Builder stays available as an alias and will be removed in Savon 3.

Changelog: https://github.com/savonrb/savon/blob/main/CHANGELOG.md Commits: https://github.com/savonrb/savon/compare/v2.17.3...v2.17.4