Uploaded image for project: 'Axis2-C'
  1. Axis2-C
  2. AXIS2C-639

Incorrect content-type and soapaction HTTP client headers

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 1.0.0
    • 1.1.0
    • transport/http
    • None
    • Windows Server 2003 running the official binary distribution of Axis2c 1.0.0

    Description

      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.

      Attachments

        Activity

          People

            samisa Don Samisa Abeysinghe
            spettini Stefano Pettini
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: