Learn HTTP Status Codes In 10 Minutes

Building a web application or API is not an easy task, especially to do it correctly. One of the things that makes this process difficult is HTTP status codes. In this video I will be breaking down and explaining every single HTTP status code that you need to know in order to get started building the perfect web application or API. We will be covering everything from the most basic 200 status codes to the more complex 403 and 304 status codes.

📚 Materials/References:

HTTP Status Code Web Site Reference: https://www.restapitutorial.com/httpstatuscodes.html

🧠 Concepts Covered:

– What HTTP status codes are
– Why they are important
– All important 200 level status codes
– All important 300 level status codes
– All important 400 level status codes
– All important 500 level status codes

🌎 Find Me Here:

My Website: https://webdevsimplified.com
Patreon: https://www.patreon.com/WebDevSimplified
Twitter: https://twitter.com/DevSimplified
Discord: https://discord.gg/7StTjnR
GitHub: https://github.com/WebDevSimplified
CodePen: https://codepen.io/WebDevSimplified

#WebDevelopment #WDS #HTTPStatusCodes

source by Web Dev Simplified

linux http server

Léa LOPEZ

Léa LOPEZ, Telecom System Administrator, Ambala College of Engineering and Applied Research, Ambala (INDIA)

37 thoughts on “Learn HTTP Status Codes In 10 Minutes

  • August 5, 2021 at 9:44 am
    Permalink

    Thank you very much for this video 🙂 It was very helpful and clear for me! 🙂

    Reply
  • August 5, 2021 at 9:44 am
    Permalink

    What is http/200 188 mean? I know the 200 is OK, but what is the trailing 188?

    Reply
  • August 5, 2021 at 9:44 am
    Permalink

    403: I know who you are but you cannot access this information. So go away!

    Reply
  • August 5, 2021 at 9:44 am
    Permalink

    If I try to get some resource by id (ex. Product) and it isn't in the database. Do I have to return code 200 with a message 'Product not found' ? Or there is another code to respond properly to this case?

    Reply
  • August 5, 2021 at 9:44 am
    Permalink

    we can given custom http status codes like
    7,1000,15000,15010,519,1287,366,1442,1232,1233,17000 ?

    Reply
  • August 5, 2021 at 9:44 am
    Permalink

    But you forgot to explain about the 409 Conflit , Remaining explanation is awesome.

    Reply
  • August 5, 2021 at 9:44 am
    Permalink

    By this time, I have seen your about ten videos on web development. They contain explanation simple to follow. Can you make a video on functional programming in JavaScript showing the basics and a few practicle examples? That will be of immense help to beginners. Thanks. 😃

    Reply
  • August 5, 2021 at 9:44 am
    Permalink

    You're such an interesting youtuber… I think you don't have that muck skill of talking to the camera… but damn man! you explain everything so easy…. Keep on!

    Reply
  • August 5, 2021 at 9:44 am
    Permalink

    is it better to use a 4xx status instead of 3xx status for invalid username/passwords? seems i should. what about 200 ok? why not that one? the request doesn't fail, it's not a server error, and nor is it a client error (the data sent may not succeed in a login, but the data isn't necessarily invalid), so for the moment, when users enter the wrong password, the site returns:
    status: 200 ok
    set-cookie: e=Access%20Denied; [….the rest here]
    location: /

    Reply
  • August 5, 2021 at 9:44 am
    Permalink

    Is it ok for developers (especially junior ones) to copy both the code and design and template of a portfolio website tutorial as long as they understand all the code and tutorial? I’ve had people tell me that I can’t do that and you should 100% code and design your own site from scratch fully on your own.

    Reply
  • August 5, 2021 at 9:44 am
    Permalink

    Really interesting, thank you for explaining it. You said on making rest APIs. I notice some kf those status codes are handled by express and nodejs already (500 when the database was down, but at least now I know what it means).
    So I don't have to make functions to send status codes and handle status codes when users navigate my site then? Is the simple check authentication enough to keep out those users, or should I send also a 403 forbidden instead of just redirecting them to the home page?

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *