4 ms·

Do they encrypt the server side error stack trace? 500 Internal Server Error Sorry, something went wrong. A team of highly trained monkeys has been dispatched

• meowface 8y ago
  Yes, they do. Pretty clever idea, I think.
  • Globz 8y ago
    Yes I agree, encrypting the stack trace enable them to share sensitive server side error codes to the client which in return can be easily reported back without having to explain anything or try to decode cryptic custom error messages. This is fantastic!
    • agumonkey 8y ago
      Also probably a unique hash too
    • jtchang 8y ago
      I actually thought it was a bit jarring. Mostly because I don't know what personal information it might be collecting and having me send them.
      • shawnz 8y ago
        Well, it's information collected at the server side. So if they really wanted they could just store the data and give you a code, but that would require more storage on their end.
        • ReverseCold 8y ago
          (sorry for the sarcasm but...) Oh no! YouTube needs to store a few kb of text! How will they have enough space?
          • pkulak 8y ago
            Well, it obviously only happens when something goes wrong. Seems valuable to keep the complexity and external dependencies of your error handing to a minimum.
            • DelightOne 8y ago
              Maybe its + a placebo since already stored in storage system + ability to see an outage maybe dropped in the filters cause it was assumed its not user-facing and so assumed lesser severity + assurance incase storage failed due to server-storage network unreachable
• joshstrange 8y ago
  I too would like to know more about this such as is it encrypted by any know method (ex: pgp)? It's rather brilliant if it's an encrypted stack trace or similar. I imagine it might even contain info about who the user is as well (if logged in or tracked via cookie) to help them debug it more.
• nickthemagicman 8y ago
  Thats prob base64 and your IP might be in the decoded string.
  • deleted 8y ago
    [deleted]
  • zamadatix 8y ago
    Messing around with it for a minute it seems it's a modified base64 (+ and / are replaced by - and _) with a space every 56 characters. I couldn't get any permutation where a-z, A-Z, 0-9, and -_/_- were consistent so it's either encrypted or one of 1,268,869,321,858,841,641,034,33,389,335,161,480,802,865,516,174,545,192,198,801,894,375,214,704,230,400,000,000,000,000 permutations of the encoding alphabet (or I messed up the decoding).
    • dx87 8y ago
      The modified base64 is probably just URL encoding https://en.wikipedia.org/wiki/Base64#URL_applications https://en.wikipedia.org/wiki/Base64#URL_applications
• devxpy 8y ago
  Why does this look like a problem for https://sentry.io https://sentry.io