AEM always returns 200 status code. | Community
Skip to main content
janellic4
janellic4
New Participant
August 29, 2019
Solved

AEM always returns 200 status code.

  • August 29, 2019
  • 34 replies
  • 25894 views

Upon requesting non-existent pages, both aem author and publish instances return blank page with 200 status code. The default 404 error page is not showing.

    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 leoberliant

    Do you have any custom filters that can possibly massage the response? You might want to stop your custom bundles in OSGi and use /system/console/requests to track recent requests.

    34 replies

    Show previous replies
    janellic4
    janellic4Author
    New Participant
    August 29, 2019

    Sorry, a typo. The response is blank page.

    janellic4
    janellic4Author
    New Participant
    August 29, 2019

    I never got the default 404 not found page working in my local author and publish instances. If the request url is invalid, the response would be a black page with 0 content length, while the HTTP status code is 200. Anyone met with the same problem?

    janellic4
    janellic4Author
    New Participant
    August 29, 2019

    Thank you for your response. I tried the custom error handler, but the results are the same. The aem just returns blank page with 200 status code even if the request url is invalid. Not sure what is wrong?

    H
    Hamid1350
    Employee
    August 29, 2019

    See the following document:

    Customizing Pages shown by the Error Handler

    Terms & ConditionsAccessibility statement

    Loading footer...