DEV Community

Cover image for Understanding HTTP Status Codes
Alok Patel
Alok Patel

Posted on

1

Understanding HTTP Status Codes

  1. 200 OK: Your request worked just fine, and you're getting what you asked for.

  2. 201 Created: What you asked to be made was created successfully.

  3. 202 Accepted: Your request is okay, but it's still being worked on.

  4. 204 No Content: The request was okay, but there's nothing to show for it.

  5. 301 Moved Permanently: The thing you're looking for is at a new address, and it's not coming back here.

  6. 302 Found: The thing you want is somewhere else, but just for now.

  7. 304 Not Modified: You already have the latest version of this, so there's nothing new to give you.

  8. 400 Bad Request: Something was wrong with your request, but it's not saying what.

  9. 401 Unauthorized: You need to prove who you are to get what you asked for.

  10. 403 Forbidden: You're not allowed to get what you asked for, no matter who you are.

  11. 404 Not Found: Whatever you're looking for isn't here.

  12. 500 Internal Server Error: Something's broken, but it's not your fault; it's the website's problem.

Sentry image

Hands-on debugging session: instrument, monitor, and fix

Join Lazar for a hands-on session where you’ll build it, break it, debug it, and fix it. You’ll set up Sentry, track errors, use Session Replay and Tracing, and leverage some good ol’ AI to find and fix issues fast.

RSVP here →

Top comments (0)

Cloudinary image

Video API: manage, encode, and optimize for any device, channel or network condition. Deliver branded video experiences in minutes and get deep engagement insights.

Learn more

👋 Kindness is contagious

Please leave a ❤️ or a friendly comment on this post if you found it helpful!

Okay