axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject RE: SOAPAction HTTP header required.
Date Tue, 26 Nov 2002 22:40:05 GMT
It can be argued, I guess, but according to SOAP1.1 spec, for an RPC style
web service, the SOAP Action header is required:

6.1.1 The SOAPAction HTTP Header Field
The SOAPAction HTTP request header field can be used to indicate the intent
of the SOAP HTTP request. The value is a URI identifying the intent. SOAP
places no restrictions on the format or specificity of the URI or that it is
resolvable. An HTTP client MUST use this header field when issuing a SOAP
HTTP Request.


-----Original Message-----
From: Chris Forbis [] 
Sent: Tuesday, November 26, 2002 5:19 PM
To: ''
Subject: RE: SOAPAction HTTP header required.

I have seen this before, I have wondered why an action is needed.  I have
MANY client tools that will not allow a action to be set, and for those I
had to make a proxy to get the message, then convert it and resend with the
action = "" set.

Am I missing a simple way to turn off this need?

-----Original Message-----
From: Ken Pelletier [] 
Sent: Tuesday, November 26, 2002 5:15 PM
Subject: SOAPAction HTTP header required.

I have a service which I've moved from Apache SOAP to Axis and am now 

Apart from a couple of things, it's working quite well.

I have one instance where a particular client application can no longer 
make calls to the service now that it's been placed under Axis, but 
could when it was under Apache SOAP.

The client app, which is not under my control, does not send a 
SOAPAction HTTP header, so Axis always returns a 'no SOAPAction 
header!' fault to the client.

How can I get my service to consumer messages w/o SOAPAction HTTP 
headers under Axis?

- Ken

View raw message