4 ms·
Kinda awkward, as I was curious to learn more about this plant I searched their website (light.bio) and it wouldn't load for me after multiple attempts. Just a
by mholt 3y ago
Kinda awkward, as I was curious to learn more about this plant I searched their website (light.bio) and it wouldn't load for me after multiple attempts. Just a blank page.
So I opened the dev tools and found the HTTP response of 504. Oh! Their site is down, it's not just me.
Then I looked at the response headers.
Server: Caddy
*skull emoji*
(Of course, after my initial heart-sink, I realized that this means their backend is down, and Caddy is serving up the response just fine. Phew.)
- Karrot_Kream 3y agoI see you're the author of Caddy, cool! Sometimes in Big Tech, this is a way to realize that some backend service is having issues because a proxy in front of the service is still returning a response. It's a rare failure case at most companies though.
- jhardy54 3y agoIsn’t that what the previous comment said? I don’t think HTTP 504 is specific to Big Tech.
- deleted 3y ago[deleted]
- tyre 3y agoExplaining 504s to the author of Caddy is a move, to be sure.
- mholt 3y agoI don't mind; my initial gut reaction forgot what the 504 was about. It's also helpful to other readers not as familiar with the topic! :)
- Karrot_Kream 3y agoWhat's the point of being so snappy and not assume good faith? I was just saying that sometimes it's fun to probe big tech during an outage, see a 504 and see `awselb` as the user agent returned, and get some outside visibility into what's going on inside. I recommend everyone do it, it's fun! It's like using eclipse glasses to look at an eclipse or binoculars to see jets in the sky.