User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; Sidewinder 1.0; formsPlayer 2.0; formsPlayer 1.4; SV1; formsPlayer 1.5; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
Reference https://bugzilla.mozilla.org/show_bug.cgi?id=309442. The code to support the SOAPAction header based upon the XForms 1.1 spec. was added to xforms.xpi 0.8.0.1. Using a SOAP monitor and the test case from 309442, the SOAPAction header was not being viewed in the http headers. Discussed the problem with Aaron, who subsequently debugged the problem. He said "we are testing the DOMDocument. We should be checking against the document's documentElement". Please reference the SerializeDataXML method where the nodeNS and nodeName are tested to determine if the node of the instance is in the SOAP Namespace and is the SOAP "Envelope" element.
Steps to Reproduce:
1.See Test case
Created attachment 269735 [details]
Web Service submission from XForms
Created attachment 269738 [details] [diff] [review]
Simple fix as it turns out. We were incorrectly looking for SOAPEnvelope on the the document instead of the documentElement. Doh!
Comment on attachment 269738 [details] [diff] [review]
oops. Regression from Bug 338314 ?
fix committed to trunk and 1.8 branch