The times they are a-changin’.
This post seems to be older than 18 years—a long time on the internet. It might be outdated.
The current message on our door is the RFC definition and handeling of 403 Forbidden error:
10.4.4 403 Forbidden
The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.
It’s been on the board since Tuesday and it was time to change it, so I Googled "funny RFC" and came up with RFC 2795, The Infinite Monkey Protocol Suite (IMPS). Here’s the abstract:
Abstract
This memo describes a protocol suite which supports an infinite number of monkeys that sit at an infinite number of typewriters in order to determine when they have either produced the entire works of William Shakespeare or a good television show. The suite includes communications and control protocols for monkeys and the organizations that interact with them.
Definitely worthy of putting on the board; also worthy enough to post a blog about.
0