If you could add to the list of HTTP status codes, what would you add?

🙋 Questions
, , ,
1

The list of HTTP status codes is here to stay yet what if we had magic powers to add to them? :magician:

Wiki version, cat version and dog edition.

How about these?

1000 - Test Pack Too Large
999 - Bug Backlog Too Big
104 - Minutes Since The Build Broke
002 - NOT OK
309 - Redirect Confusion. Are We Back At The Start

What else would you like to see? Be mindful of those already on the official list (or maybe break the rules and repurpose them? :wink: )

1 Like
2

Thought of a few
666 - Beast of a problem
42 - Lack of correct question
53 - Sentient VW present
1.618 - Golden ratio present
3.14159 - Circular reference
007 - Spyware present
1984 - Big brother is watching
2001 - Extra space present
10 - Two binary exceptions present

4 Likes
3

This can be too,

  • 429 Too Many Requests (with rate limit details): Clearly specify rate limits exceeded.
  • 506 Bandwidth Limit Exceeded: Indicate server bandwidth limitations.
  • 521 Web Server is Down: Clearly identify server outage.
  • 522 Connection Timed Out: Indicate connection issues.
  • 523 Origin is Unavailable: Specify origin server problems.
  • 524 A Timeout Occurred: Clearly indicate timeout errors.
  • 525 SSL Handshake Failed: Indicate SSL/TLS issues.
  • 526 Invalid SSL Certificate: Specify SSL certificate problems.
4

419 – I'm a coffee pot
403.5 – Not Quite Forbidden Yet Nearly Not Found
410.5 – Back Again
410.8 – Nope Lost It, Damn

2 Likes
5

Loving the decimal places in error codes :joy:

1 Like
6

Just testing @simon_tomes’s scope :slight_smile:

1 Like
7

776 -Almost perfect connection
555 - Function executed by luck
999 - It works on my system
901 - Broken link
701 - The Bug is Back
2024 - I have seen enough bugs for the millennium

1 Like
8

1066 - Invading code snippets

2 Likes