From 73f1f79578f16e21ad38e94c75613a81dfa4da47 Mon Sep 17 00:00:00 2001 From: Wade Pickett Date: Thu, 14 Feb 2019 12:00:55 -0800 Subject: [PATCH] Minor update 2.2 release notes - added RFC link --- aspnetcore/release-notes/aspnetcore-2.2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnetcore/release-notes/aspnetcore-2.2.md b/aspnetcore/release-notes/aspnetcore-2.2.md index 361bdd832c..b6313b0402 100644 --- a/aspnetcore/release-notes/aspnetcore-2.2.md +++ b/aspnetcore/release-notes/aspnetcore-2.2.md @@ -23,7 +23,7 @@ For more information, see the following resources: ## Problem details support -ASP.NET Core 2.1 introduced `ProblemDetails`, based on the RFC 7807 specification for carrying details of an error with an HTTP Response. In 2.2, `ProblemDetails` is the standard response for client error codes in controllers attributed with `ApiControllerAttribute`. An `IActionResult` returning a client error status code (4xx) now returns a `ProblemDetails` body. The result also includes a correlation ID that can be used to correlate the error using request logs. For client errors, `ProducesResponseType` defaults to using `ProblemDetails` as the response type. This is documented in Open API / Swagger output generated using NSwag or Swashbuckle.AspNetCore. +ASP.NET Core 2.1 introduced `ProblemDetails`, based on the [RFC 7807](https://tools.ietf.org/html/rfc7807) specification for carrying details of an error with an HTTP Response. In 2.2, `ProblemDetails` is the standard response for client error codes in controllers attributed with `ApiControllerAttribute`. An `IActionResult` returning a client error status code (4xx) now returns a `ProblemDetails` body. The result also includes a correlation ID that can be used to correlate the error using request logs. For client errors, `ProducesResponseType` defaults to using `ProblemDetails` as the response type. This is documented in Open API / Swagger output generated using NSwag or Swashbuckle.AspNetCore. ## Endpoint Routing