Files
system-design-101/data/guides/5-http-status-codes-that-should-never-have-been-created.md
Kamran Ahmed ee4b7305a2 Adds ByteByteGo guides and links (#106)
This PR adds all the guides from [Visual
Guides](https://bytebytego.com/guides/) section on bytebytego to the
repository with proper links.

- [x] Markdown files for guides and categories are placed inside
`data/guides` and `data/categories`
- [x] Guide links in readme are auto-generated using
`scripts/readme.ts`. Everytime you run the script `npm run
update-readme`, it reads the categories and guides from the above
mentioned folders, generate production links for guides and categories
and populate the table of content in the readme. This ensures that any
future guides and categories will automatically get added to the readme.
- [x] Sorting inside the readme matches the actual category and guides
sorting on production
2025-03-31 22:16:44 -07:00

883 B
Raw Blame History

title, description, image, createdAt, draft, categories, tags
title description image createdAt draft categories tags
5 HTTP Status Codes That Should Never Have Been Created Explore 5 HTTP status codes that are quirky, humorous, or problematic. https://assets.bytebytego.com/diagrams/0232-http-status-code-shouldnt-exist.png 2024-01-27 false
api-web-development
HTTP Status Codes
Web Development

  • 451 Unavailable for Legal Reasons: Access denied due to legal issues.
  • 218 This is Fine: Inspired by the meme, bypasses server error overrides.
  • 420 Enhance Your Calm: Twitters old code for exceeding rate limits. Now changed to 429.
  • 530 Site Frozen: Used by Pantheon for locked sites, often unpaid bills.
  • 418 I'm a Teapot: A classic April Fool's joke indicating a server's limitations.