ORY

HTTP Status Codes

Quick reference for common HTTP status codes.

35 of 35

1xx Informational
  • 100

    Continue

    The server has received the request headers and the client should proceed to send the request body.

  • 101

    Switching Protocols

    The requester has asked the server to switch protocols (e.g., to WebSocket).

  • 103

    Early Hints

    Used to return some response headers before final HTTP message.

2xx Success
  • 200

    OK

    Standard response for successful HTTP requests.

  • 201

    Created

    The request has been fulfilled, resulting in a new resource.

  • 202

    Accepted

    The request has been accepted for processing, but the processing has not been completed.

  • 204

    No Content

    The server successfully processed the request and is not returning any content.

  • 206

    Partial Content

    The server is delivering only part of the resource due to a range header.

3xx Redirection
  • 301

    Moved Permanently

    This and all future requests should be directed to the given URI.

  • 302

    Found

    Tells the client to look at another URL (temporary redirect).

  • 303

    See Other

    The response can be found under another URI using GET.

  • 304

    Not Modified

    The resource has not been modified since the last request.

  • 307

    Temporary Redirect

    Repeat the request to another URI without changing the method.

  • 308

    Permanent Redirect

    Repeat the request to another URI permanently without changing the method.

4xx Client Error
  • 400

    Bad Request

    The server cannot or will not process the request due to a client error.

  • 401

    Unauthorized

    Authentication is required and has failed or has not yet been provided.

  • 403

    Forbidden

    The request was valid, but the server is refusing action.

  • 404

    Not Found

    The requested resource could not be found.

  • 405

    Method Not Allowed

    The request method is not supported for the target resource.

  • 408

    Request Timeout

    The server timed out waiting for the request.

  • 409

    Conflict

    Indicates a request conflict with the current state of the target resource.

  • 410

    Gone

    Indicates that the resource is no longer available and will not be available again.

  • 413

    Payload Too Large

    The request entity is larger than limits defined by server.

  • 415

    Unsupported Media Type

    The request entity has a media type which the server does not support.

  • 418

    I'm a teapot

    The server refuses the attempt to brew coffee with a teapot.

  • 422

    Unprocessable Content

    The request was well-formed but could not be processed semantically.

  • 425

    Too Early

    Server is unwilling to process a request that might be replayed.

  • 429

    Too Many Requests

    The user has sent too many requests in a given time window (rate limiting).

5xx Server Error
  • 500

    Internal Server Error

    A generic error message when an unexpected condition was encountered.

  • 501

    Not Implemented

    The server either does not recognize the request method, or it lacks the ability to fulfill the request.

  • 502

    Bad Gateway

    The server was acting as a gateway and received an invalid response from the upstream server.

  • 503

    Service Unavailable

    The server is currently unavailable (overloaded or down for maintenance).

  • 504

    Gateway Timeout

    The server was acting as a gateway and did not receive a timely response from the upstream server.

  • 505

    HTTP Version Not Supported

    The server does not support the HTTP protocol version used in the request.

  • 511

    Network Authentication Required

    The client needs to authenticate to gain network access.