Spyke

Syndicated from the fediverse. Read and engage on the original instance.

View original on programming.dev

28 replies

That's actually a very bad gateway if it's still running an nginx from 2010.

87
programming.dev

Mine gave 418 so I shoved a teabag in and poured water on it

It still doesn't work

71

Yeah fine but it's a bad teapot too... The tea was way too weak and barely warm nevermind hot

15

Of cause it's a bad gateway, look at it. Doesn't even look like a real Cisco router.

36
lemmy.world

Now I’m tempted to finally replace that default page with this one 🤣

26
Toriborreply
corndog.social

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!

15

I need to change my default bad gateway html to this at one point.

Idk if it's possible using NPM

16
lemmy.zip

Should have used a Gateway computer from like 2003.

10

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.

4
lemmy.world

Yeah. Revealing the name and version of the software that is interacting with the network is indeed bad.

3

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

2

You reached the end