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 2018/02/06 20:58:00 UTC
[jira] [Commented] (TINKERPOP-1737) Validate and throw an exception
when maxContentLength overflows
[ https://issues.apache.org/jira/browse/TINKERPOP-1737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16354524#comment-16354524 ]
stephen mallette commented on TINKERPOP-1737:
---------------------------------------------
[~jeromatron] is this still an issue to be concerned about? Looking back to my last comment, it doesn't appear as though I was able to recreate this.
> Validate and throw an exception when maxContentLength overflows
> ---------------------------------------------------------------
>
> Key: TINKERPOP-1737
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1737
> Project: TinkerPop
> Issue Type: Improvement
> Components: server
> Affects Versions: 3.2.5
> Reporter: Jeremy Hanna
> Priority: Trivial
>
> If you set the {{maxContentLength}} to higher than {{Integer.MAX_VALUE}} it won't error out but the gremlin console is broken. We should probably do some sort of validation on startup and then fail fast with an appropriate error message instead.
> This can happen if people don't want to worry about the value and set it arbitrarily high and don't know that it's an integer.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)