problem-spring-web VS error-handling-spring-boot-starter

That's a silly question. Yet, I'd probably answear https://github.com/zalando/problem-spring-web (which is a Spring extension for https://github.com/zalando/problem).

For that https://github.com/zalando/problem-spring-web already exists. Which also follows the Problem standard.

It's been done: https://github.com/zalando/problem-spring-web#:~:text=Problem%20Spring%20Web%20is%20a,responses%20from%20a%20Spring%20application.

If you use my error handling library https://github.com/wimdeblauwe/error-handling-spring-boot-starter , then see https://wimdeblauwe.github.io/error-handling-spring-boot-starter/current/#spring-security-authenticationentrypoint

I am the author of Error Handling Spring Boot Starter which you can just put on your classpath and using the validation annotations will given you a nice response in case there are validation errors. See https://foojay.io/today/better-error-handling-for-your-spring-boot-rest-apis/ for an overview of how it works.

I always try to include information so the caller knows what is wrong exactly. I personally would hate it to get a Bad Request, but having no clue what field is missing or wrong. It is in fact the main driver for my error handling library I have built: https://github.com/wimdeblauwe/error-handling-spring-boot-starter

You can have a look at the unit test https://github.com/wimdeblauwe/error-handling-spring-boot-starter/blob/master/src/test/java/io/github/wimdeblauwe/errorhandlingspringbootstarter/handler/HttpMessageNotReadableApiExceptionHandlerTest.java#L37 It will return a response similar to this: