4 ms·
502 Bad Gateway Damn this ancient laptop. But my Packard Bell won’t connect either?!
by cluckindan 2y ago
502 Bad Gateway
Damn this ancient laptop. But my Packard Bell won’t connect either?!
- diggan 2y ago2xx - All good 3xx - Somethings could be better 4xx - You did something wrong 5xx - Server did something wrong Judging by this quick cheat-sheet I just created, this was not your fault :)
- rsynnott 2y ago1xx - Rare novelty response code.
- corobo 2y ago1xx - this is the websocket connection if you want to watch what it's doing
- doubled112 2y ago418 I'm a teapot seemed pretty novel the first few times.
- coldcode 2y agoI prefer I'm a coffeepot, but for some reason, there was a 404.
- doubled112 2y agoCoffee not found. Sorry, I already drank it.
- jeroenhd 2y ago1xx is the response code you try to ignore because it's really annoying to deal with properly (like when you receive a 100 response to a file upload, or even worse, a 101 with a protocol that isn't exactly what you expected, or a 103 which means more content comes later). 1xx response codes are crucial for things like WebSockets and HTTP/3 but they make the HTTP state machine more complex and many people writing manual HTTP requests are ill-prepared to deal with them.