accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3094) Pass back stack traces when server side exception occurs
Date Fri, 29 Aug 2014 18:23:53 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-3094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14115616#comment-14115616
] 

Josh Elser commented on ACCUMULO-3094:
--------------------------------------

Configuration would be nice, and defaulting to not doing it would be good. I think to a bunch
of web frameworks in which a development mode will allow the underlying stack to be printed
along with some 5XX HTTP response. You would not want to give any clients information about
the database, regardless of whether or not we think there is an obvious risk. Personally,
I would not want to pass this information back to every client, but could see the merit in
development use cases.

> Pass back stack traces when server side exception occurs 
> ---------------------------------------------------------
>
>                 Key: ACCUMULO-3094
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3094
>             Project: Accumulo
>          Issue Type: Bug
>            Reporter: Keith Turner
>             Fix For: 1.7.0
>
>
> Was discussing ACCUMULO-3092 w/ [~dlmarion] and the issue of why more info about server
side exceptions was not transmitted back to client came up.  This was a concious design decision
made in Accumulo to avoid unintentionally leaking information to the client.   The main concern
is the exception message on the server side, that message could have been constructed w/ data
from Accumulo.
> We discussed the possibility of dropping the exception message[s] and sending the stack
trace[s] back to the client side.  



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message