RFC 7807, EK INDUSTRY-STANDARD, ERROR RESPONSE FORMAT DEFINE karta hai — type (ERROR TYPE ka URI), title (SHORT, HUMAN-READABLE SUMMARY), status (HTTP STATUS CODE), detail (SPECIFIC, HUMAN-READABLE EXPLANATION), instance (SPECIFIC OCCURRENCE ka URI).

Spring Boot 3.x mein, ProblemDetail CLASS, ISI STANDARD ko, NATIVELY, SUPPORT karti hai — HAR API mein, CUSTOM ERROR FORMAT, INVENT karne ke BAJAYE, EK ESTABLISHED, WIDELY-RECOGNIZED STANDARD, FOLLOW kiya jaata hai.

@RestControllerAdvice
public class GlobalExceptionHandler {
    @ExceptionHandler(ResourceNotFoundException.class)
    public ProblemDetail handleNotFound(ResourceNotFoundException ex) {
        ProblemDetail problem = ProblemDetail.forStatusAndDetail(
            HttpStatus.NOT_FOUND, ex.getMessage());
        problem.setTitle("Resource Not Found");
        problem.setType(URI.create("https://api.example.com/errors/not-found"));
        return problem;
    }
}

// Response body:
// {
//   "type": "https://api.example.com/errors/not-found",
//   "title": "Resource Not Found",
//   "status": 404,
//   "detail": "Product with id 42 not found",
//   "instance": "/api/products/42"
// }