Skip to content


Subversion checkout URL

You can clone with
Download ZIP


use soapAction from WSDL #100

merged 1 commit into from

3 participants


I think it's better to use soapAction defined in WSDL, rather than client assumption of its value. Especially since we have it in method.soapAction. And double quote it.


Yes please. I am calling a java cxf soap server and in a recent update it requires the soap action to be either "" or the name of the method. The wsdl declares soapAction="" but the node client automatically converts it to the namespace + methodname. I would like it to use the "" as defined by the wsdl, because currently cfx doesn't accept the header.


thanks. i'll merge this in and fallback to the previous code if method.soapAction is undefined.

@milewise milewise merged commit 4a3b5c5 into vpulim:master

If you specify an empty string as the soapAction in the wsdl, which is what you do when you want the soapAction to stay empty, it will be "undefined" as well so I don't know how that would work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Oct 12, 2012
  1. @yuriykashin
This page is out of date. Refresh to see the latest.
Showing with 1 addition and 1 deletion.
  1. +1 −1  lib/client.js
2  lib/client.js
@@ -88,7 +88,7 @@ Client.prototype._invoke = function(method, arguments, location, callback) {
message = '',
xml = null,
headers = {
- SOAPAction: this.SOAPAction ? this.SOAPAction(ns, name) : (((ns.lastIndexOf("/") != ns.length - 1) ? ns + "/" : ns) + name),
+ SOAPAction: '"' + method.soapAction + '"',
'Content-Type': "text/xml; charset=utf-8"
options = {},
Something went wrong with that request. Please try again.