HTTP 419 Never Gonna Give You Up
Dev tools
http error response
SHOW HN2021
262points
71comments
#141of 2,533 in 2021
Top 6%of 2021 by points
How HN took it
CuriousMostly questions and neutral comments
4 positive, 20 neutral or asking, 0 mixed, 8 critical, out of 32 comments about the project. Thread score -0.10.
Idea: 4 for, 6 against
The thread, comment by comment
Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.
positive neutral or mixed critical about another commenter or something else the maker
What HN said
Objections
Turns HTTP error codes into a meme
From 1 comment
a part of me is definitely in favor of this, but another part of me wants to avoid turning http error codes into a meme
nunez on HN
Could help bot authors refine bots or reveal detection abilities
From 1 comment
Superficially a fun idea.. Side efffects may include: * Helping bot authors improve their bot so it won't be identified. * Revealing how good you are at detecting bots.
dusted on HN
Redirecting bots is not appropriate for a 4xx code
From 2 comments
If it redirects then it should be in the 3xx class
andrethegiant on HNIf the requirement is that client should follow the redirect, one should not use a 4xx status code. I think “319 never gonna give you up” is more adequate
hoppla on HN
Questions
Is it legal to host zip bombs or similar traps for bots?
From 2 comments
> "And I remembered another nice trick which someone else came up with, zip bomb the bots :-)" Just curious, is it legal to host a zip bomb on your website? I would think it…
gitgud on HNCould there be legal repercussions for doing this?
rascul on HN
Alternatives named
418 I'm a Teapot
From 2 comments
> I’m half joking, but if we can have HTTP 418 I’m a Teapot then there is enough room in the HTTP standard for the more useful HTTP 419 Never Gonna Give You Up error code.…
zinekeller on HNThe thing that really disappoints me is that 418 I'm a Teapot isn’t registered—instead it’s reserved as “(Unused)”:…
chrismorgan on HN
Laravel 419 Page Expired
From 2 comments
https://en.wikipedia.org/wiki/List_of_HTTP_status_codes#Unofficial_codes 419 Page Expired (Laravel Framework) Used by the Laravel Framework when a CSRF Token is missing or expired.
dmitrijbelikov on HNLaravel uses 419 as Page Expired: https://github.com/laravel/framework/blob/a2c557a1b697c462927e10b248c6911ce9415079/src/Illuminate/Foundation/Exceptions/Handler.php#L389
omgitsabird on HN
Gzip and zip bombs for bots
From 2 comments
I definitely agree bots are underserved, I have a few things I do to keep them entertained, ssh bots are tar-pitted to keep them connected but busy, my hope is that I occupy at…
gnyman on HNAlthough I think bots should be free to access the same content as humans do, I have a suggestion for your fuzzer anti-bot-spray: It won't work on the more sturdy samples, but…
SCHiM on HN
SSH tarpits
From 2 comments
I definitely agree bots are underserved, I have a few things I do to keep them entertained, ssh bots are tar-pitted to keep them connected but busy, my hope is that I occupy at…
gnyman on HNThere are some very cool ways of doing these tarpit. This for example: https://nullprogram.com/blog/2019/03/22/
rexfuzzle on HN
nginx 444 silent connection close
From 1 comment
NGINX has a very nice status 444 that silently closes the connection, I think serves as a great way to deal with uninvited connections.
pull_my_finger on HN