为何JAX-RS未原生支持423错误码？JAX-RS 2.1 Response枚举缺失该码

Great question—this is one of those niche HTTP status code gaps that catches developers off guard when working with REST APIs, especially if you’re dealing with resource-locking scenarios common in WebDAV or similar systems. Let’s break down why this status code is missing from the Response.Status enum and how to work around it:

Core Reasons for the Omission #

• HTTP Standard vs. Extended Codes: The 423 "Locked" status code is defined as a WebDAV-specific extension to core HTTP/1.1. JAX-RS’s Response.Status enum prioritizes status codes from universal core HTTP standards that are widely used across most RESTful APIs. Since 423 is tied primarily to WebDAV workflows rather than general-purpose REST services, it wasn’t included in the JAX-RS 2.1 specification (JSR 370).
• Maintainability and Scope: The JAX-RS spec team aims to keep the Response.Status enum focused and avoid bloating it with every possible HTTP extension. Including less commonly used codes would add unnecessary complexity, especially since most standard REST services don’t require 423 for their core functionality.
• Backward Compatibility: By the time JAX-RS 2.1 was finalized, the Response.Status enum had already been established with a set of widely adopted codes. Adding niche status codes later could introduce confusion or unintended side effects for existing codebases.

How to Use 423 Locked in JAX-RS #

Even though it’s not in the enum, you can still easily return a 423 response using the numeric status code directly:

// Return a 423 Locked response with a custom message
return Response.status(423)
               .entity("The requested resource is currently locked by another process")
               .build();

If you want to avoid magic numbers, define your own reusable constant:

public static final int SC_LOCKED = 423;

// Then use it in your response
return Response.status(SC_LOCKED).build();

Will Future JAX-RS Versions Include It? #

It’s possible but unlikely unless there’s significant community demand. JAX-RS typically only adds status codes once they become widely adopted across general-purpose REST APIs. For now, the manual approach above is the standard way to handle 423 responses in JAX-RS.

内容的提问来源于stack exchange，提问作者Taufik Pirjade