[
https://issues.apache.org/jira/browse/SOLR-14886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17722181#comment-17722181
]
Isabelle Giguere commented on SOLR-14886:
-----------------------------------------
[~cpoerschke]
{quote}Would be curious w.r.t. extent of stack trace hiding e.g. query vs.
update vs. admin/other requests and http vs. solrj requests – would it be
useful in all the cases to hide or only in some?{quote}
I'm not sure. Any exception that ends up in ResponseUtils will have the stack
trace hidden from the response (if configured), but, Solr is not a small code
base, as you know. I make no guarantees about any other response paths that I
would not be aware of.
> Suppress stack trace in Query response.
> ---------------------------------------
>
> Key: SOLR-14886
> URL: https://issues.apache.org/jira/browse/SOLR-14886
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 8.6.2
> Reporter: Vrinda Davda
> Priority: Minor
> Attachments: SOLR-14886.patch, SOLR-14886.patch
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently there is no way to suppress the stack trace in solr response when
> it throws an exception, like when a client sends a badly formed query string,
> or exception with status 500 It sends full stack trace in the response.
> I would propose a configuration for error messages so that the stack trace is
> not visible to avoid any sensitive information in the stack trace.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
