Skip to content

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 #455

@perbergland

Description

@perbergland

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions