No description
Find a file
2025-07-15 11:20:49 +01:00
400.html Initial Commit 2025-07-15 11:20:49 +01:00
401.html Initial Commit 2025-07-15 11:20:49 +01:00
402.html Initial Commit 2025-07-15 11:20:49 +01:00
403.html Initial Commit 2025-07-15 11:20:49 +01:00
404.html Initial Commit 2025-07-15 11:20:49 +01:00
410.html Initial Commit 2025-07-15 11:20:49 +01:00
418.html Initial Commit 2025-07-15 11:20:49 +01:00
429.html Initial Commit 2025-07-15 11:20:49 +01:00
451.html Initial Commit 2025-07-15 11:20:49 +01:00
500.html Initial Commit 2025-07-15 11:20:49 +01:00
501.html Initial Commit 2025-07-15 11:20:49 +01:00
502.html Initial Commit 2025-07-15 11:20:49 +01:00
503.html Initial Commit 2025-07-15 11:20:49 +01:00
504.html Initial Commit 2025-07-15 11:20:49 +01:00
license.md Initial Commit 2025-07-15 11:20:49 +01:00
readme.md Initial Commit 2025-07-15 11:20:49 +01:00
under_construction.html Initial Commit 2025-07-15 11:20:49 +01:00

Blobfox Error Pages

A collection of HTTP error messages featuring blobfoxes.

Pages exist for the following pages:

  • 400 Bad Request
  • 401 Unauthorized
  • 402 Payment Required
  • 403 Forbidden
  • 404 Not Found
  • 410 Gone
  • 418 I'm a Teapot
  • 429 Too Many Requests
  • 451 Unavailable for Legal Reasons
  • 500 Internal Server Error
  • 501 Not Implemented
  • 502 Bad Gateway
  • 503 Service Unavailable
  • 504 Gateway Timeout

Pull Requests to introduce more error pages are welcome, however a few general requirements apply:

  • The chosen blobfox should correspond to the error, and be as if the blobfox were the server.
  • Avoid repeated emojis, technically you could use :blobfoxoutage: for everything, but where's the fun in that?
  • Multiple emojis are okay when there aren't good alternatives (see 451 Unavailable for Legal Reasons), try to keep to one where practical.