ews-javascript-api icon indicating copy to clipboard operation
ews-javascript-api copied to clipboard

When an Exchange instance returns a http 500 error with an error that isn’t EXACTLY a soap error, an orphaned uncaught exception is thrown and the method never returns

Open perbergland opened this issue 7 months ago • 4 comments
trafficstars

Verified in 0.15.3 and 0.13.2.

The root cause is that the error handler for status 500 creates an instance of EwsServiceXmlReader which will crash if xmlDoc is undefined or later if the exactly correct SOAP error properties aren’t included.

Since the default behaviour for nodejs is to perform a process.exit on uncaught exceptions like this, this leads to serious crashes and the method will hang since it crashes in the code that is supposed to invoke the errorDelegate

perbergland avatar Apr 06 '25 13:04 perbergland