Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SOAP action not set in content-type header with ballerina/soap.soap12:0.9.0 #5842

Closed
MaryamZi opened this issue Nov 30, 2023 · 1 comment · Fixed by ballerina-platform/module-ballerina-soap#116
Assignees
Labels
Priority/High Reason/EngineeringMistake The issue occurred due to a mistake made in the past. Type/Bug

Comments

@MaryamZi
Copy link
Member

Description:
$title. Seems to be setting it as the SOAPAction header (as for SOAP 1.1).

0.8.1 - set as expected

POST /services/SimpleStockQuoteService HTTP/1.1
content-type: application/soap+xml; action=getQuote

0.9.0 - set as SOAPAction

POST /services/SimpleStockQuoteService HTTP/1.1
content-type: text/xml
SOAPAction: getQuote
Copy link

github-actions bot commented Dec 6, 2023

This issue is NOT closed with a proper Reason/ label. Make sure to add proper reason label before closing. Please add or leave a comment with the proper reason label now.

      - Reason/EngineeringMistake - The issue occurred due to a mistake made in the past.
      - Reason/Regression - The issue has introduced a regression.
      - Reason/MultipleComponentInteraction - Issue occured due to interactions in multiple components.
      - Reason/Complex - Issue occurred due to complex scenario.
      - Reason/Invalid - Issue is invalid.
      - Reason/Other - None of the above cases.

@ThisaruGuruge ThisaruGuruge added the Reason/EngineeringMistake The issue occurred due to a mistake made in the past. label Dec 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority/High Reason/EngineeringMistake The issue occurred due to a mistake made in the past. Type/Bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants