How to handle error handler for 404 page of acs commons 4.2 version its working in author not in publish and DNS aswell???? | Community
Skip to main content
K
keshav_goud
Level 3
October 6, 2020
Solved

How to handle error handler for 404 page of acs commons 4.2 version its working in author not in publish and DNS aswell????

  • October 6, 2020
  • 1 reply
  • 3961 views

I was trying to implement error handler of acs commons 4.2 version in my project its working fine in author but not in publish also in dns can you help me why this functionality not working in publish 

 

( Specified the path of error page in project parent page jcr:content )

 

 

 

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 ektaa69139387

Please check below points to resolve the issue:

1. Check if the issue is from publish server or dispatcher. If issue is from dispatcher then ensure that you have done required AEM dispatcher configuration

 In dispatcher_vhost.conf file, set DispatcherPassError to ‘0’. This allows erring requests to be sent back to AEM.

 

 

2. Which AEM version you are using because on AEM 6.2 or above, this service uses a Service User for repository access. This user is configured with the expected permissions required, but additional permissions may be required if your repository design deviates from the expected structure. So please check if this user have proper permission on publish instance as well.

User name: acs-commons-error-page-handler-service

ACLs:

  • jcr:read on /content

1 reply

E
ektaa69139387Accepted solution
Level 2
October 6, 2020

Please check below points to resolve the issue:

1. Check if the issue is from publish server or dispatcher. If issue is from dispatcher then ensure that you have done required AEM dispatcher configuration

 In dispatcher_vhost.conf file, set DispatcherPassError to ‘0’. This allows erring requests to be sent back to AEM.

 

 

2. Which AEM version you are using because on AEM 6.2 or above, this service uses a Service User for repository access. This user is configured with the expected permissions required, but additional permissions may be required if your repository design deviates from the expected structure. So please check if this user have proper permission on publish instance as well.

User name: acs-commons-error-page-handler-service

ACLs:

  • jcr:read on /content
    K
    keshav_goudAuthor
    Level 3
    October 6, 2020
    Hi ektaa, thanks for your reply the problem is on publisher server the node is not handling the error page handler , User name: acs-commons-error-page-handler-service having /content and /libs permission also to read ,i need dynamically 404 page implementation like if /content/we-retail/fsdff.html error handler should wakeup over here.
    Terms & ConditionsAccessibility statement

    Loading footer...