Skip to content

Stop returning stack traces for failed requests #156

@justinkambic

Description

@justinkambic

It's been noted that there are security implications of returning stack traces and detailed exception messages as a part of request failures. We can throw these errors so the server's log has a record of them, but we should return general messages with appropriate error codes as a result of some failure on our REST requests.

The implementation of this issue should audit the REST endpoints we support and sanitize their exception handling; that issue should have a detailed list of all the endpoints we need to touch in the patch.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions