Unable to exclude stacktrace from DataFormExceptions in OperationOutcomes when using JAX-RS providers #768
Comments
InfiniteLoop90
added a commit
to InfiniteLoop90/hapi-fhir
that referenced
this issue
Oct 22, 2017
… when using AbstractJaxRsProviders, the stacktrace will be included in the OperationOutcome details only if AbstractJaxRsProvider#withStrackTrace() is configured to return true
InfiniteLoop90
added a commit
to InfiniteLoop90/hapi-fhir
that referenced
this issue
Oct 23, 2017
…tException as an InvalidRequestException so that it still gets sent as a 400 response but now DataFormatException stacktraces can now be conditionally sent based on the ExceptionHandlingInterceptor#setReturnStackTracesForExceptionTypes(Class<?>...) configuration
InfiniteLoop90
changed the title
jamesagnew
added a commit
that referenced
this issue
Nov 23, 2017
…ace-jax-rs Fixes issue #768 to conditionally include stacktraces for DataFormatExceptions in OperationOutcomes when using AbstractJaxRsProviders
|
Closing since this was fixed in HAPI FHIR 3.1.0. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In issue #111, stacktraces were supposed to not be included by default. In doing some digging, it looks like
AbstractJaxRsProvider#createOutcome(DataFormatException)always includes the stacktrace in the details of the OperationOutcome. So if an invalid date format is sent for aDateParam, the whole stracktrace will be included in the response. It seems like it'd be idea ifDataFormatExceptions would be handled like other exceptions by having the stacktrace be included if the Exception type is included as such inExceptionHandlingInterceptor.(Note, this issue still exists in the latest 3.1.0-SNAPSHOT build).
See screenshot from Postman for an example:
The text was updated successfully, but these errors were encountered: