Skip to content

Conversation

@raghavexe
Copy link
Contributor

Description

A new article for HTTP explaining various HTTP status codes

Validation

article is located on the learn page under the http header. Article name: "Understanding HTTP Status Codes"

Related Issues

Check List

  • [X ] I have read the Contributing Guidelines and made commit messages that follow the guideline.
  • [X ] I have run pnpm format to ensure the code follows the style guide.
  • [X ] I have run pnpm test to check if all tests are passing.
  • [ X] I have run pnpm build to check if the website builds without errors.
  • [ X] I've covered new added functionality with unit tests if necessary.

@raghavexe raghavexe requested a review from a team as a code owner November 10, 2025 15:47
@vercel
Copy link

vercel bot commented Nov 10, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Updated (UTC)
nodejs-org Ready Ready Preview Nov 10, 2025 3:49pm

Copy link
Member

@avivkeller avivkeller left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My concern here is that we are re-inventing the wheel.

If the user wants to see the different codes they can use, they should visit https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status.


The purpose of this guide is to provide a clear understanding of HTTP status
codes and how to use them effectively when building servers in Node.js.
If you’ve followed along with [`Anatomy of an HTTP Transaction`](https://nodejs.org/en/learn/http/anatomy-of-an-http-transaction), you’ve already seen how to send responses to clients. This article builds on that foundation by exploring how to communicate meaningful outcomes through proper HTTP status codes.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead, this should be bold, not code.

Also, the link should be /learn/...

@raghavexe
Copy link
Contributor Author

My concern here is that we are re-inventing the wheel.

If the user wants to see the different codes they can use, they should visit https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status.

I do agree with that, but i saw it in a way that if the user is utilizing the learn path on the website, it would be convenient for them to have that concept cleared without having to deviating from the page

@efekrskl
Copy link
Contributor

Nice write-up, but I also don't think this should belong nodejs.org. HTTP concepts are general web fundamentals, not Node specific behaviour. We already explain how to send the status code, which covers the only Node related part of this article.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants