Approximately 29 years ago, I was in the MSN multiplayer client for Jedi Knight: Dark Forces II (stop judging me, I know almost every word of that sentence fragment indicates that I’m old) and someone linked something that would log the IP of anyone who accessed it. When I, a naive 9-year old, opened it, they copied my IP and posted it in the public chat.
I was so freaked out that I disconnected from the internet and unplugged my computer.
Oh, I see now. Actually a config issue. It should return text/plain. But it’s odd, I recall it working, I literally just copy pasted it from local NGINX config where I recall it working in the past.
I added default_type text/plain; into the location block which now loads normally, and still returns the same 418 code.
Welp, seems like browsers don’t like 418. Edit: Nevermind, I am idiot.
location = /teapot { return 418 "I'm a teapot\n"; }https://167.160.186.15/teapot
Approximately 29 years ago, I was in the MSN multiplayer client for Jedi Knight: Dark Forces II (stop judging me, I know almost every word of that sentence fragment indicates that I’m old) and someone linked something that would log the IP of anyone who accessed it. When I, a naive 9-year old, opened it, they copied my IP and posted it in the public chat.
I was so freaked out that I disconnected from the internet and unplugged my computer.
Oh, I see now. Actually a config issue. It should return text/plain. But it’s odd, I recall it working, I literally just copy pasted it from local NGINX config where I recall it working in the past.
I added
default_type text/plain;into the location block which now loads normally, and still returns the same 418 code.Both servo and firefox now report the text correctly. I haven’t checked the response code on those, but lynx correctly reports 418:
I get this on Firefox Android:
It basically says “Cannot complete the request. No additional information available” :/