You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Yang Xia (Jira)" <ji...@apache.org> on 2024/05/21 18:40:00 UTC
[jira] [Assigned] (TINKERPOP-2866) Hide Stack Trace and Details of Certain Server Errors from Clients
[ https://issues.apache.org/jira/browse/TINKERPOP-2866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yang Xia reassigned TINKERPOP-2866:
-----------------------------------
Assignee: Yang Xia
> Hide Stack Trace and Details of Certain Server Errors from Clients
> ------------------------------------------------------------------
>
> Key: TINKERPOP-2866
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2866
> Project: TinkerPop
> Issue Type: Improvement
> Components: server
> Affects Versions: 3.5.5
> Reporter: Cole Greer
> Assignee: Yang Xia
> Priority: Major
>
> The current behaviour of gremlin server when an error or exception is thrown is to serialize the full throwable and return it to the client.
>
> Based on [this|https://lists.apache.org/thread/qb5o0vxk927n00csht4xdcfmw34qdhmd] discussion in the dev list, it is preferable to only return errors which might be considered useful to a user, and replace other errors with a more generic InternalServerError response.
>
> There remains an open question of exactly which errors and exceptions should be returned in detail. Current intention is continue returning all `Exception`s which are thrown. Any `Error` will be replaced with InternalServerError unless the original error is included in a whitelist which allows it to be sent. If any `Exception` is identified which the community feels should not be returned, a blacklist of exceptions can be added as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)