HTTP Status Code Short listed

HTTP Status Code Short listed

Commonly Used HTTP Status Codes for Web Services.

  • 200 => OK, general indication of request success.
  • 201 => Created, typically used for POST and PUT request.
  • 204 => No Content, typically means request is processed successfully but no data is found on server for the request.
  • 301 => Redirect permanently, new URL is returned and the client should send to the new URL directly for the future requests.
  • 302 => Redirect temporarily. Future request from client should send to the same URL.
  • 400 => Bad request, used to tell client the request contains invalid data.
  • 401 => Unauthorized, this actually tells the client they are not authenticated to access the requested data.
  • 403 => Forbidden, this tells the client that they are denied to access the content.
  • 404 => Not found, tells the client the requested resource is not found on the server.
  • 429 => Too Many Requests, tells the client that they have reached the limit of allowed number of requests in a given amount of time.
  • 500 => Internal Server Error, tells the client there is a error happened during the processing of the request. This usually happens when error/exception raised when try to get data from database.
  • 501 => Not Implemented, tells the client the request can not be fulfilled (but may be available in the future).
  • 502 => Bad Gateway, this usually send from gateway server that it got a invalid response from service server.
  • 503 => Service Unavailable, this indicates the server is not able to handle the request due to overload or downtime.
  • 504 => Gateway Timeout, this is given when the gateway server is timed out when waiting for a response from the service server.

To view or add a comment, sign in

More articles by Lixin C.

  • Solution Architect - part 1

    Solution Architects (SA) are responsible for providing solutions to fulfill business requirements by working with…

  • Retrieve Data From Multiple Microservices

    In microservice pattern, microservices are suppose to own their own database to achieve best independent scalability…

  • Chaining HTTP Calls Using Observables With RxJS

    Sometimes we need to make multiple HTTP calls in a specific order to get data. The data from previous call are either…

  • RxJS Concise Demo - Creation Operators

    RxJS operators are functions that can create or process Observables. Creation operators are used to create new…

  • Async Controller Methods For Scalability

    In API action methods, it is very common to call a database or another web resource to get requested data. Getting data…

  • Angular Component Lifecycle Hooks

    Angular lifecycle hooks allows you to implement critical logic at the right time of a component's lifecycle. During the…

  • Network Layers for Software Engineers

    Sending messages to another person using web browser or mobile app is not surprisingly easy nowadays and most people…

  • Implementing a Fixed-Window Median Data Stream With Heaps

    A data stream is like a pipe with moving data inside. Here I only consider integer numbers as data and try to find the…

  • Test Your Testing Strategy with A Dice Game

    1. Project background Sometime in last year I got interested in how does the 3D web rendering engines work.

Explore content categories