EDS - Setup 404 and 500 error pages for Shared Repository (Repoless) | Community
Skip to main content
Asutosh_Jena_
Community Advisor
Asutosh_Jena_Community Advisor
Community Advisor
April 17, 2025
Solved

EDS - Setup 404 and 500 error pages for Shared Repository (Repoless)

  • April 17, 2025
  • 3 replies
  • 1072 views

I'm working on configuring 404 and 500 error pages on EDS, where we're using the repoless setup—meaning multiple websites are sharing a single content repository. I haven’t been able to find any reference materials on how to set up error pages in this scenario. Any guidance would be greatly appreciated.

PS: Please note, I'm not looking for copy-paste responses from AI tools that don’t add any real value.

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 Asutosh_Jena_

Solution:

For the 404 page, I’m currently utilizing a fragment-based approach, where a predefined content path is set. This path can also be maintained in platforms like SharePoint or Google Drive to ensure consistent content delivery across all websites.

As for the 500 error page, it appears that there is no similar feature available at the moment. However, Adobe is actively working on it, and we hope to see updates on this in the near future.


Thanks,

Asutosh

3 replies

arunpatidar
Community Advisor
arunpatidarCommunity Advisor
Community Advisor
April 17, 2025

Hi @asutosh_jena_ 

I am not sure if this is possible or not but you can have a look to the approach mentioned here

https://adapt.to/2024/presentations/adaptto-2024-scaling-up-implement-large-scale-projects-on-aem-edge-delivery-services.pdf 

Arun Patidar
    Asutosh_Jena_
    Community Advisor
    Asutosh_Jena_Community AdvisorAuthor
    Community Advisor
    April 18, 2025

    Hi @arunpatidar 

    Thank you for sharing this document. I’ve reviewed it previously, but unfortunately, it doesn’t fully meet the requirements for our current scenario.

      Shashi_Mulugu
      Community Advisor
      Shashi_MuluguCommunity Advisor
      Community Advisor
      April 18, 2025

      @asutosh_jena_ we do have 404.html file in github code repo created from archetype right? Will it not work?

      Asutosh_Jena_
      Community Advisor
      Asutosh_Jena_Community AdvisorAuthor
      Community Advisor
      April 18, 2025

      Hi @shashi_mulugu 

      Yes, we do have the 404.html file in the repository. However, since it's a shared repository supporting multiple websites, each site may have its own unique design and content requirements. One potential approach I considered is using a fragment path and maintaining the respective content via SharePoint, ensuring consistency through a common fragment reference. This solution is working for now, but I was hoping to explore if there’s a more standardized or best-practice approach we could follow.

      Regarding the 500 error, I’m currently looking into ways to simulate or trigger this error to validate the behavior. Unlike AEM or AEMaaCS, we don’t have direct control over the 500 scenarios in this environment, which makes it a bit more challenging to test.

        Asutosh_Jena_
        Community Advisor
        Asutosh_Jena_Community AdvisorAuthorAccepted solution
        Community Advisor
        April 24, 2025

        Solution:

        For the 404 page, I’m currently utilizing a fragment-based approach, where a predefined content path is set. This path can also be maintained in platforms like SharePoint or Google Drive to ensure consistent content delivery across all websites.

        As for the 500 error page, it appears that there is no similar feature available at the moment. However, Adobe is actively working on it, and we hope to see updates on this in the near future.


        Thanks,

        Asutosh

          Terms & ConditionsAccessibility statement

          Loading footer...