Other 4xx codes
All HTTP status codes in ASP.NET Core
4xx Client error
423 Locked
The resource is locked (WebDAV, RFC 4918).
In ASP.NET Core: Occasionally used for resources locked by another user.
423 in .NET
The StatusCodes constant, HttpStatusCode enum name, reason phrase, class, and how EnsureSuccessStatusCode() and the standard resilience handler treat 423.
| Constant | StatusCodes.Status423Locked |
|---|---|
| HttpStatusCode | HttpStatusCode.Locked |
| Reason phrase | Kestrel sends Locked |
| Class | 4xx, client error |
| IsSuccessStatusCode | false |
| EnsureSuccessStatusCode() | throws HttpRequestException: Response status code does not indicate success: 423 (Locked). |
| Standard resilience handler | does not retry it |
Returning 423
Minimal APIs
Results.StatusCode(StatusCodes.Status423Locked)
Results.Problem(statusCode: StatusCodes.Status423Locked, detail: "...")Controllers
StatusCode(StatusCodes.Status423Locked)
Problem(statusCode: StatusCodes.Status423Locked, detail: "...")The ProblemDetails body
What Results.Problem(statusCode: 423) sends (with AddProblemDetails()), as application/problem+json:
{
"title": "Locked",
"status": 423,
"traceId": "0HNA1B2C3D4E5:00000001"
}A controller's Problem(statusCode: 423) sends a different body, because MVC only fills type and title for codes in ApiBehaviorOptions.ClientErrorMapping:
{
"status": 423,
"traceId": "0HNA1B2C3D4E5:00000001"
}A bare StatusCode(423) in an [ApiController] also gets a ProblemDetails body automatically; Results.StatusCode(423) in a minimal API sends an empty body unless you add UseStatusCodePages().
Every response on this page was recorded from ASP.NET Core 10.0.12 on Kestrel in the Production environment; the HttpClient rows come from .NET 10.0.12 and Microsoft.Extensions.Http.Resilience 10.10.0.