loopbackio / loopbackio/strong-soap
SOAP fault coerces SOAP 1.2 request to SOAP 1.1 response
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 410
- Forks
- 162
- Avg merge
- 4h 36m
- Merged PRs (30d)
- 7
Description
Looks like return a fault according to your documentation (throw { Fault: .... }) causes coercion to SOAP 1.1.
# Description/Steps to reproduce
Use SOAP 1.2 request and return a fault.
# Link to reproduction sandbox
[gentest3.zip](https://github.com/loopbackio/strong-soap/files/7687450/gentest3.zip)
# Expected result
Expected result is SOAP 1.2 Envelope
# Additional information
win32 x64 16.13.0
ltpp0000-paci-app@1.0.0 C:\temp\crap\test3
├── cors@2.8.5
├── debug@4.3.3
├── express@4.17.1
├── helmet@4.6.0
├── morgan@1.10.0
└── strong-soap@3.3.1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the gentest3.zip reproduction and trace how a SOAP fault response is built for a SOAP 1.2 request. Compare the generated response with the expected SOAP 1.2 Envelope; done means returning a fault without coercing the response to SOAP 1.1.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100