ext-soap throws uncatchable errors
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 40.4k
- Forks
- 8.1k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 96
Description
Description
I am writing a SOAP server, but the soap extension throws uncatchable errors.
For example, "Procedure '...' not present" happens when the client asks for a function that is not supported by the server. And when $soapServer->handle(...) is called, the script throws a fatal error and outputs its own response.
I should be able to catch any error and handle it however I want. \SoapServer::handle() should never kill my script.
PHP Version
PHP 8.1.14
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 ext-soap implementation of \SoapServer::handle() and trace how unsupported procedures and other errors are raised. Done means callers can catch these errors, including the unsupported-procedure case, without the script terminating or the SOAP server emitting its own response.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, php
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100