Release 2026.00

Release Note:

Beginning with Release 2026.00, SymXchange enforces standard HTTP and SOAP messaging behavior for SOAP-based service requests. This change aligns SymXchange with established HTTP protocol standards by requiring SOAP requests that contain a message payload to use the HTTP POST method. Prior to this release, certain SOAP requests submitted using HTTP GET may have been processed due to legacy behavior within the SymXchange web server implementation. Release 2026.00 removes this non-standard behavior and enforces protocol-compliant processing.

Background:

SOAP is an application-layer messaging protocol that operates over HTTP and defines its own structured message format using a SOAP envelope and payload. Because SOAP requests contain a message body, industry standards require these requests to be transmitted using HTTP POST.

What Changed in Release 2026.00

Release 2026.00 corrects a gap in prior SymXchange request handling by enforcing standard HTTP method usage for SOAP operations. The update ensures that:

• SOAP requests containing a SOAP payload must be submitted using HTTP POST.
• HTTP GET is no longer accepted for SOAP request execution.
• Request processing now behaves consistently with standard HTTP and SOAP protocol expectations

Impact to Existing Integrations

Credit unions and vendors with integrations that improperly use HTTP GET to invoke SymXchange SOAP operations may experience failures after upgrading to Release 2026.00. Such integrations must be updated to submit SOAP messages using HTTP POST.

It is important to distinguish between:

• SOAP service requests, which include a SOAP payload and must use HTTP POST.
• Standard HTTP GET requests, which retrieve resources without a payload and continue to be supported where applicable. Examples include retrieving service information or WSDL resources through a browser URL request.

Clarification Regarding HTTP GET Release 2026.00 change does not eliminate support for all HTTP GET requests. HTTP GET remains appropriate for retrieving resources that do not require a request payload, such as service metadata or WSDL documents. The restriction applies specifically to SOAP operation execution, where a SOAP payload is present.