You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "Stefano Pettini (JIRA)" <ji...@apache.org> on 2007/07/11 11:56:05 UTC
[jira] Created: (AXIS2C-639) Incorrect content-type and soapaction
HTTP client headers
Incorrect content-type and soapaction HTTP client headers
---------------------------------------------------------
Key: AXIS2C-639
URL: https://issues.apache.org/jira/browse/AXIS2C-639
Project: Axis2-C
Issue Type: Bug
Components: transport/http
Affects Versions: 1.0.0
Environment: Windows Server 2003 running the official binary distribution of Axis2c 1.0.0
Reporter: Stefano Pettini
HTTP headers content-type and soapaction seems not to be set correctly, according to how and if axis2_options_set_soap_version is called.
With:
No axis2_options_set_soap_version call or
axis2_options_set_soap_version(axOptions, axEnv, AXIOM_SOAP_11)
I get:
content-type: application/soap+xml;charset=UTF-8;action="helloAction";
With:
axis2_options_set_soap_version(axOptions, axEnv, AXIOM_SOAP_12)
I get:
content-type: text/xml;charset=UTF-8
soapaction: "helloAction"
No special option is written in axis2.xml.
MTOM and REST default options have been commented out from axis2.xml.
Behaviour looks like not compliant with SOAP 1.1 and 1.2 requirements about HTTP headers.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Resolved: (AXIS2C-639) Incorrect content-type and soapaction
HTTP client headers
Posted by "Samisa Abeysinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2C-639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Samisa Abeysinghe resolved AXIS2C-639.
--------------------------------------
Resolution: Fixed
Fix Version/s: 1.1.0
Assignee: Samisa Abeysinghe
There was a bug in that AXIOM_SOAP_11 and AXIOM_SOAP11 had different values. Now this is solved. Also note that AXIOM_SOAP_11 and AXIOM_SOAP_12 are deprecated, you should use AXIOM_SOAP11 and AXIOM_SOAP12 instead.
> Incorrect content-type and soapaction HTTP client headers
> ---------------------------------------------------------
>
> Key: AXIS2C-639
> URL: https://issues.apache.org/jira/browse/AXIS2C-639
> Project: Axis2-C
> Issue Type: Bug
> Components: transport/http
> Affects Versions: 1.0.0
> Environment: Windows Server 2003 running the official binary distribution of Axis2c 1.0.0
> Reporter: Stefano Pettini
> Assignee: Samisa Abeysinghe
> Fix For: 1.1.0
>
>
> HTTP headers content-type and soapaction seems not to be set correctly, according to how and if axis2_options_set_soap_version is called.
> With:
> No axis2_options_set_soap_version call or
> axis2_options_set_soap_version(axOptions, axEnv, AXIOM_SOAP_11)
> I get:
> content-type: application/soap+xml;charset=UTF-8;action="helloAction";
> With:
> axis2_options_set_soap_version(axOptions, axEnv, AXIOM_SOAP_12)
> I get:
> content-type: text/xml;charset=UTF-8
> soapaction: "helloAction"
> No special option is written in axis2.xml.
> MTOM and REST default options have been commented out from axis2.xml.
> Behaviour looks like not compliant with SOAP 1.1 and 1.2 requirements about HTTP headers.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org