Skip to content

Provide richer GraphQL errors when IncludeExceptionDetails is enabled #9826

Description

@tobias-tengler

Currently we have to limit the details we include in error messages, since attackers could fingerprint / infer details about the implementation otherwise.
It would be helpful to provide more details in certain cases though.

Metadata

Metadata

Assignees

No one assigned

    Fields

    No fields configured for Feature.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions