getting a very strange response from a sling servlet in our prod env: <div id="root" status="500"backend="bb78d8242935e149ab12d9d14ebbb908--F_Skyline_Origin_Ingress_Publish"

Forum|Forum|4 years ago
November 30, 2021
3 replies
1706 views

randomly, instead of some json, we get the following HTML back from one of our servlets:

We are looking in the logs, but wondered if anyone has seen this type of response before?

<!DOCTYPE html>
      <html lang="en">
        <head>
          <meta charset="utf-8">
          <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">

          <meta name="description" content="AEM Cloud Service">
          <title>AEM Cloud Service</title>
          <link rel="icon" href="https://errors.adobeaemcloud.com/favicon.ico">
          
          <link rel="stylesheet" href="https://errors.adobeaemcloud.com/src.status.css">
        </head>
        <body>
          <noscript>AEM Cloud Service.</noscript>
          <div id="root" status="500"
                           backend="bb78d8242935e149ab12d9d14ebbb908--F_Skyline_Origin_Ingress_Publish"
                           healthy="1"
                           gen="0"
                           rid="d548c3db-dd02-49d3-bfdd-e96f2c1e4dd6"
                           xid="3481717772"
                           age="0.000"
                           ttl="0.000"
                           restarts="0"
                           nobranding=""
                           statusApi=""
          > </div>
          <script src="https://errors.adobeaemcloud.com/src.status.js"> </script>
        </body>
      </html>

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

Best answer by joerghoh

This means that the publish has returned a statuscode 500 to your browser.

joerghoh

Accepted solution

Adobe Employee

This means that the publish has returned a statuscode 500 to your browser.

L

leek86608325

Level 2

I'm seeing this same thing be returned by the cloud servlet whenever a 500 error is sent, regardless of what I send in the response.getWriter().write(...). Is this unique to 500 error responses, or would a different error code actually let you access the response text?