On Wed, 12 Dec 2012, John MacAuley wrote:
Ah yes, but "Basic Profile Version 1.1" clause "R1127 A RECEIVER MUST NOT rely on the value of the SOAPAction HTTP header to correctly process the message." was put in because in SOAP 1.2 the SOAP action dependency was removed.
The nice thing about standards is that there are so many to choose between :-). Is there a decisions on what version of SOAP the NSI protocol should use?
The additional statement from the profile document states "SOAPAction is purely a hint to processors. All vital information regarding the intent of a message is carried in soap:Envelope."
Most new SOAP specifications no longer use the SOAP action field. I had just went through the pain of doing Microsoft integration and put it in for better NSI compatibility with MS.
Interesting. OpenNSA will break without it, but it should not be difficult to change (just annoying). Best regards, Henrik Henrik Thostrup Jensen <htj at nordu.net> Software Developer, NORDUnet