[
https://issues.apache.org/jira/browse/FINERACT-1168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17212031#comment-17212031
]
Aleksandar Vidakovic commented on FINERACT-1168:
------------------------------------------------
We could customize the amount of information that is returned with something
like this:
{code:java}
@Component
public class MyCustomErrorAttributes extends DefaultErrorAttributes {
@Override
public Map<String, Object> getErrorAttributes(
WebRequest webRequest, boolean includeStackTrace) {
Map<String, Object> errorAttributes =
super.getErrorAttributes(webRequest, includeStackTrace);
errorAttributes.put("locale", webRequest.getLocale()
.toString());
errorAttributes.remove("error");
//...
return errorAttributes;
}
}
{code}
> Integration Tests failure due to internal server errors should show server
> side failure stack trace
> ---------------------------------------------------------------------------------------------------
>
> Key: FINERACT-1168
> URL: https://issues.apache.org/jira/browse/FINERACT-1168
> Project: Apache Fineract
> Issue Type: Improvement
> Reporter: Michael Vorburger
> Priority: Blocker
>
> IT failures like FINERACT-1167, already raised in FINERACT-927, are a PITA
> (impossible) to debug.
> This is an IT failure due to a #500 means "something internal went wrong on
> the server" - but we don't know what...
> To know what the problem was, the server should return the exception in the
> HTTP body of the 500 response. The IT should then capture that, and include
> it in the JUnit test failure.
> But in production, 500 errors should NOT show the stack trace - that is
> typically considered a security problem. So we need some env var / sys prop
> to enable it, just for debugging. Spring Boot probably actually already has
> some... knob, for this?
> [~ptuomola] thought this may interest you.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
