Continue
The server is ready for the client to send the request body.
Loading DEV/STATION…
Look up a code, understand the response and find the next step.
64 of 64 registered entries
The server is ready for the client to send the request body.
The connection is switching to a protocol agreed with the client.
An interim WebDAV response indicates that processing is continuing.
The server sends preliminary hints while preparing the final response.
Temporary registration for resumable uploads. IANA currently lists an expiry of 13 November 2026; check the registry for changes.
The request succeeded. The response normally contains the requested result.
The request created one or more resources.
Processing has been accepted, but completion is not yet guaranteed.
An intermediary transformed the successful response from the origin server.
The request succeeded and there is no response body to display.
The request succeeded and the client should reset the document view. The response has no content.
The response contains the requested part of a resource, such as a video byte range.
A WebDAV response reports separate outcomes for multiple resources.
A WebDAV response avoids repeating members already reported in a multi-status result.
The response contains a representation produced by applying instance manipulations.
More than one representation or destination is available.
The resource has a permanent new location. Some clients can change a POST to GET.
The resource is temporarily at another location. Some clients can change a POST to GET.
Retrieve the result at another address using GET, or HEAD when appropriate.
The cached representation is still valid. This response has no content body.
An older proxy-selection status that is deprecated and should not be used for new implementations.
This code is reserved and is no longer used.
Use a temporary destination while preserving the original request method.
Use the permanent new destination while preserving the original request method.
The server cannot process the request because its syntax, framing or routing is invalid.
The request needs valid authentication credentials. This commonly means signing in.
Reserved for future use; applications sometimes apply their own payment-related meaning.
The server understood the request but refuses access. Signing in again may not grant permission.
The requested resource could not be found, or the server is not disclosing its existence.
The resource does not support this request method. The Allow header identifies supported methods.
The server cannot provide a representation matching the requested negotiation preferences.
The client must authenticate with the proxy.
The server did not receive a complete request within its waiting period.
The request conflicts with the current resource state, such as a newer saved revision.
The resource is no longer available and that condition is likely permanent.
The server requires a valid Content-Length for this request.
A condition supplied in the request headers did not match the resource state.
The request body exceeds the size the server is willing or able to process.
The request address is longer than the server will accept.
The request body uses a format or encoding this resource does not support.
The requested range cannot be served from this resource.
The server cannot meet an expectation supplied in the Expect request header.
Reserved in HTTP semantics. Historically known as “I’m a teapot”; it is not a normal production error.
The request reached a server that cannot provide an authoritative response for this address.
The body format is understood, but its instructions cannot be processed.
The WebDAV resource is locked against the requested operation.
The operation failed because another operation it depended on failed.
The server refuses early data because the request could be replayed.
The client needs to use a supported upgraded protocol.
The request must include a condition to prevent conflicting updates.
The client has reached a request limit. Respect Retry-After when it is provided.
One or more request headers exceed the server’s limits.
Access is unavailable because of a legal demand or restriction.
An unexpected server condition prevented the request from completing.
The server does not support functionality required to complete this request.
A gateway or proxy received an invalid response from an upstream server.
The service is temporarily unable to handle the request. It may provide Retry-After.
A gateway or proxy did not receive an upstream response in time.
The server does not support the HTTP version used by the request.
A server configuration causes a negotiated variant to negotiate again.
The server cannot store the representation needed to complete this operation.
A WebDAV operation encountered an infinite loop.
An obsolete extension-negotiation status. It should not be used for new implementations.
Network access requires authentication, such as a captive Wi-Fi portal.