Design the Error Body

A RideNotFoundException is now caught centrally. Beyond the status code, what should the response body actually contain so a client can act on it — not just know that something failed?

See a reasonable shape

json

{
  "timestamp": "2026-09-15T10:30:45",
  "status": 404,
  "error": "Ride Not Found",
  "message": "Ride not found with id: 100",
  "path": "/rides/100"
}

Enough to log, enough to display, and enough to correlate against a server-side trace by timestamp and path — not just a bare message string.

Spring Boot
Exception Handling