[ http://issues.apache.org/jira/browse/AXIS2C-437?page=all ]
Samisa Abeysinghe resolved AXIS2C-437.
--------------------------------------
Resolution: Fixed
I have fixed this issue using the attached patch as well as some additional
logic. Thank you for the patch first of all.
Now, if you want to set the SOPA action, you should set that on options using
AXIS2_OPTIONS_SET_SOAP_ACTION. This is because, in case of using SOAP 1.2, if
we use the WSA action as SOAP action, Microsoft WCF returns an error in some
cases.
Please have a look at samples/user_guide/clients/echo_blocking_soap11.c on how
to use AXIS2_OPTIONS_SET_SOAP_ACTION.
> HTTP header missing soap action on client call
> -----------------------------------------------
>
> Key: AXIS2C-437
> URL: http://issues.apache.org/jira/browse/AXIS2C-437
> Project: Axis2-C
> Issue Type: Bug
> Components: transport/http
> Affects Versions: Current (Nightly), 0.95
> Reporter: Andrew Borley
> Assigned To: Samisa Abeysinghe
> Fix For: 0.96
>
> Attachments: Axis2c_HTTPSOAPAction.patch
>
>
> From Axis2C 0.95 onwards using AXIS2_OPTIONS_SET_ACTION in client code does
> not set the SOAPAction HTTP header.
> On invocation, the following HTTP header is sent.
> POST /stockquote.asmx HTTP/1.1
> User-Agent: Axis2/C
> SOAPAction: ""
> This causes SOAP 1.1 services that depend on this header to fail, such as the
> services from www.webservicex.net
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
