You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "stephen mallette (JIRA)" <ji...@apache.org> on 2015/12/11 13:56:10 UTC
[jira] [Updated] (TINKERPOP-1030) Map common exceptions to HTTP
status codes where possible
[ https://issues.apache.org/jira/browse/TINKERPOP-1030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stephen mallette updated TINKERPOP-1030:
----------------------------------------
Priority: Trivial (was: Minor)
Fix Version/s: (was: 3.1.1-incubating)
Description: If a script throws an exception in the REST API, it would be nice if there was a way to map that exception to an HTTP status code. The gremlin server configuration could have a specific set of exception to error code mappings. (was: If a script throws an exception in the REST API, it would be nice if there was a way to map that exception to an HTTP status code. Or at least convert certain common exceptions to sensible codes.)
> Map common exceptions to HTTP status codes where possible
> ---------------------------------------------------------
>
> Key: TINKERPOP-1030
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1030
> Project: TinkerPop
> Issue Type: Improvement
> Components: server
> Affects Versions: 3.1.0-incubating
> Reporter: stephen mallette
> Assignee: stephen mallette
> Priority: Trivial
>
> If a script throws an exception in the REST API, it would be nice if there was a way to map that exception to an HTTP status code. The gremlin server configuration could have a specific set of exception to error code mappings.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)