[SWS-981] SOAPAction header with SOAP ver 1.2 messages Created: 07/Mar/17  Updated: 27/Oct/17  Resolved: 27/Oct/17

Status: Closed
Project: Spring Web Services
Component/s: Core
Affects Version/s: 2.1.4, 2.2.0.RELEASE, 2.3.0, 3.0.0.RC1, 2.4.0
Fix Version/s: 3.0.0.RELEASE

Type: Bug Priority: Minor
Reporter: jaminh Assignee: Greg Turnquist
Resolution: Complete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Pull Request URL: https://github.com/spring-projects/spring-ws/pull/102

 Description   

When sending SOAP version 1.2 messages using the SaajSoapMessageFactory if no SOAP action is specified (using SoapActionCallback) then the message will still be sent with a "SOAPAction" header. The response will also have a "SOAPAction" http header. The "SOAPAction" header was replaced with the "action" parameter of the application/soap+xml MIME type in SOAP version 1.2. If a SoapActionCallback is used then the SOAP action is added in the appropriate place and the "SOAPAction" http header is removed, but that SOAPAction header should never be present for SOAP 1.2 messages. It appears the header is being added in the SaajSoapMessage constructor (around line 118 in master at the time the issue was created).



 Comments   
Comment by jaminh [ 27/Oct/17 ]

I figured I would make a note here that for SOAP version 1.1 the SOAPAction header appears to be required whether a value is specified or not per section 6.1 of the SOAP version 1.1 spec https://www.w3.org/TR/2000/NOTE-SOAP-20000508/#_Toc478383527.

Generated at Mon Dec 11 07:52:19 UTC 2017 using JIRA 6.4.14#64029-sha1:ae256fe0fbb912241490ff1cecfb323ea0905ca5.