[
https://issues.apache.org/jira/browse/SOLR-14886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17722099#comment-17722099
]
Christine Poerschke commented on SOLR-14886:
--------------------------------------------
Thanks [~igiguere] for working on this!
I like the idea of excluding stack traces from the response i.e. if it's logged
in the Solr logs already then the info is there and it's kinda extra noise from
the client's perspective to have the track trace in the error response too.
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? (Did only a quick read through of the pull
request i.e. might have missed things there which answer this already.)
> 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: 20m
> 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: [email protected]
For additional commands, e-mail: [email protected]
