That’s actually a very bad gateway if it’s still running an nginx from 2010.
Mine gave 418 so I shoved a teabag in and poured water on it
It still doesn’t work
deleted by creator
Yeah fine but it’s a bad teapot too… The tea was way too weak and barely warm nevermind hot
Of cause it’s a bad gateway, look at it. Doesn’t even look like a real Cisco router.
Now I’m tempted to finally replace that default page with this one 🤣
This one is at least as informative as the default. Sometimes I’ll be troubleshooting an application where the developers got a little too creative with error messages and I’ll get an “Error: Oopsie woopsie you broke the website!” And I’m like JUST GIVE ME AN ERROR CODE I’M THE ADMINISTRATOR AND I NEED TO ACTUALLY FIX THIS!
They don’t even send the right status code in the header?
haha 67
fam bruh
hang ten mate
Gen Alpha detected
Gen X, sorry mate
Damn, staying with the times tho
Doot doot.
That’s some skibbidie toilet ahh aura rizz head ass type shit
looooooool
I need to change my default bad gateway html to this at one point.
Idk if it’s possible using NPM
Should have used a Gateway computer from like 2003.
would have been more accurate. I don’t know many devs that could tell the difference between an actual network gateway and a desktop computer.
This tab made me think my instance was down again.
I always thought it’s a German spa town
418
Yeah. Revealing the name and version of the software that is interacting with the network is indeed bad.
I’d never thought of this but i think i know where i want to start with hacking now. If only it hadn’t been years since i’d hit one of these
More like bad proxy/load balancer, imo, but sure.
No u
