21–30 of 44 posts
Anyone know what's in that debug information the 500 error page spits out?
Looks base64 encoded to me, but running it through a decoder isn't giving me anything intelligible. Here's a OCR of the text in the image, maybe you can figure it out: Edit: Full text is in sibling comment.
Well, you can get a 500 error from facebook via this URL. http://facebook.com/logout
Users are more comfortable with this way: they simply copy/paste the text to us and we have all the info we need.
My kid got soooooo upset: "Daddy, fix it. I wanna see the Beetle monster truck". Imagine me trying to explain that 'monkeys will fix the problem for him' :-P. He was eager to wait... hoping to see the monkeys... but none came while refreshing the page. As soon as the Beetle baja buggie video loaded, all about he monkeys was forgotten.
Thanks for reminding
Spotify is down too. Didn’t they move to Google Cloud recently?
Hm... wonder if there's a library that could do something similar. It's an interesting idea encrypting your error that I haven't seen in many places.
What could the purpose of an encrypted error be? If it's a server side error it's already in their logs.
If it's symmetric-encrypted, then it's unforgeable, and it's safe to include private information, like IP address or recent video-viewing history, just in case someone posts a screenshot of it on HN.
Hm... wonder if there's a library that could do something similar. It's an interesting idea encrypting your error that I haven't seen in many places.
What could the purpose of an encrypted error be? If it's a server side error it's already in their logs.
It would be useful when things break so hard you don't even get a log.