tag: status-codes
articles: 2 · beats: 1
latest: November 14, 2026
---
Status Codes
2 Crashtech articles on Status Codes, filed under Development Best Practices, published in November 2026. Every piece is full-text HTML with sources, structured data and an authored FAQ.
All 2 sit in the Development Best Practices beat. Development Best Practices
The Strange HTTP Status Codes: 451, 418, 420, 218 and 530, and What They Teach
Five odd status codes, which are standard, which are jokes and which are vendor inventions, and why custom codes are a trap for client code.
HTTP Status Codes You Misuse, and What to Return Instead
401 vs 403, 301 vs 308, 404 vs 410, 502 vs 503 vs 504. Picking the right status code tells clients and monitors what to do next.
Questions we answer about Status Codes
- What does HTTP 451 mean?
- Is HTTP 418 I'm a teapot a real status code?
- Why was Twitter's 420 replaced?
- Should I invent my own HTTP status codes?
- What is the difference between 401 and 403?
- When should an API return 400 versus 422?
- What is the difference between 502, 503 and 504?
- Should I use 301 or 308 for a permanent redirect?
Covered alongside
Frequently asked questions
What does Crashtech publish about Status Codes?
2 articles tagged Status Codes, the most recent published November 14, 2026. All 2 sit in the Development Best Practices beat. Each carries numbered sources, an authored FAQ and full structured data.
What questions about Status Codes does Crashtech answer directly?
8 questions have a dedicated answer page under this tag, including “What does HTTP 451 mean?”. Each answer is authored prose from the article it belongs to, not a generated summary.
Can AI assistants read Crashtech's Status Codes coverage?
Yes. Crashtech serves full static HTML to every crawler, allows all major AI user agents in robots.txt, and publishes an llms.txt manifest plus a full-text corpus, so assistants can retrieve and cite these articles directly.