axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samisa Abeysinghe (JIRA)" <>
Subject [jira] Resolved: (AXIS2C-437) HTTP header missing soap action on client call
Date Wed, 06 Dec 2006 12:57:23 GMT
     [ ]

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:
>             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

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message