Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add more http statuses #201

Merged
merged 1 commit into from
Sep 24, 2021
Merged

Add more http statuses #201

merged 1 commit into from
Sep 24, 2021

Conversation

n00p3
Copy link
Contributor

@n00p3 n00p3 commented Sep 24, 2021

I needed to use status 422 - Unprocessable Entity and notices it's not present in hunchentoot so I've added it and a few others.

@stassats stassats merged commit 460a32c into edicl:master Sep 24, 2021
@metayan
Copy link

metayan commented Nov 14, 2021

Thanks for adding the status codes.
418 caught my eye, and even though I like that it's called +http-im-a-teapot+ here, and agree with keeping it that way, it might be good to be aware of the current status of that status code (pun intended):

15.5.19.  418 (Unused)

   [RFC2324] was an April 1 RFC that lampooned the various ways HTTP was
   abused; one such abuse was the definition of an application-specific
   418 status code.  In the intervening years, this status code has been
   widely implemented as an "Easter Egg", and therefore is effectively
   consumed by this use.
   Therefore, the 418 status code is reserved in the IANA HTTP Status
   Code Registry.  This indicates that the status code cannot be
   assigned to other applications currently.  If future circumstances
   require its use (e.g., exhaustion of 4NN status codes), it can be re-
   assigned to another use.

IETF source
diff from when 418 was added

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants