Daniel Rohe

removed handling of HttpMediaTypeNotAcceptableException and HttpMediaNotSupportedException which are subclasses of HttpMediaTypeException because similar responses. HttpMediaTypeNotAcceptableException ``` zalando-problem status: 406 content-type: application/problem+json { "title":"Not Acceptable", "status":406, "detail":"No acceptable representation" } spring-problem...

> Interesting that spring doesn't seem to use the problem specific JSON media subtype That's what the test cases show when running with spring's advice :)

The handling of HttpMessageNotReadableException in MessageNotReadableAdviceTrait with Spring Problem Exception handling is slightly different. This library uses the exception message that unveils possible application internals in details attribute where as...

removed handling of TypeMismatchException because of similar response. ``` zalando-problem status: 400 content-type: application/problem+json { "title":"Bad Request", "status":400, "detail":"Failed to convert value of type 'java.lang.String' to required type 'java.time.OffsetDateTime'; Failed...

Using predicates and filters would make writing routing rules much more complex as people would have to maintain at least two different routes, one for the original request and a...

without this filter developers will always have to define two routes and an additional shunt backend. ``` - pathSubtree: /something filters: - corsOrigin - oauthTokenInfoScopes("uid") - pathSubtree: /something predicates: -...

Hi Brian, in our company we implemented ErrorAttributes and ErrorView in a way that the Map structure resembled the JSON Problem structure for all spring framework exceptions and also added...

Hi Brian, no, we didn't use Spring Framework's ProblemDetails support We implemented this approach of overwriting ErrorAttributes and ErrorView before Spring Framework supported Problem Details. This solution worked out quite...

Hi Brian, I did some more testing and a big difference between the current Error Response and the Error Attributes is that Error Responses does not include the binding results...

Hi Brian, yes similar to the mentioned issue. In case of validation errors I think the API should still respond with a presentation of binding errors (e.g. JSON pointer to...