HTTP

HTTP 401 Unauthorized vs 424 Failed Dependency

Both HTTP 401 (Unauthorized) and 424 (Failed Dependency) belong to the 4xx Client Error category. 401 indicates that the request requires user authentication. The response includes a WWW-Authenticate header indicating the authentication scheme. Meanwhile, 424 means that the request failed because it depended on another request that failed (WebDAV).

Description

The request requires user authentication. The response includes a WWW-Authenticate header indicating the authentication scheme.

When You See It

When accessing a protected resource without credentials or with expired tokens.

How to Fix

Include valid authentication credentials (API key, Bearer token, Basic auth) in the Authorization header.

Description

The request failed because it depended on another request that failed (WebDAV).

When You See It

In batch WebDAV operations when a prerequisite action fails.

How to Fix

Fix the failed dependency first, then retry the operation.

Key Differences

1.

HTTP 401: The request requires user authentication. The response includes a WWW-Authenticate header indicating the authentication scheme.

2.

HTTP 424: The request failed because it depended on another request that failed (WebDAV).

3.

You encounter 401 when when accessing a protected resource without credentials or with expired tokens.

4.

You encounter 424 when in batch WebDAV operations when a prerequisite action fails.

When to Use Which

For 401 (Unauthorized): Include valid authentication credentials (API key, Bearer token, Basic auth) in the Authorization header. For 424 (Failed Dependency): Fix the failed dependency first, then retry the operation.

Learn More