You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AEM Version, including Service Packs, Cumulative Fix Packs, etc: _______6.3 SP2
ACS AEM Commons Version: _____3.13
Reproducible on Latest? yes
Expected Behavior
In our application, CUG are applied on all page except login page. When a page is accessed with actual url, user gets redirected to the login page and after logging in, page opens. Same should be the behavior with Vanity Url. If a user access the page with vanity url, if user is not logged in, it should be redirected to login page and if user is logged in, page should be open.
Actual Behavior
When a user try to access the page with vanity url, user gets 404 page instead of redirected to login page.
Steps to Reproduce
Created some pages, addd vanity url, and apply CUG on it. Install ACS Commons 3.13 version. Open ACS AEM COMMONS - Error page handler service in ConfigMgr and enable 'Vanity Dispatch Check'. Now access the page using vanity url. It will give 404 page.
We tried to debug it and found that, errorpagehandler's 404.jsp calls a service(vanityURLService) dispatch method. In this service, there is method isVanity which checks for the vanity path. But it uses current user resource resolver to resolve the path. Because, current user is not logged in and page is secured, resource resolver resolve method returns non-existing resource.
There are some logic performed which eventually returns false to jsp.
Now as response is false, jsp sets 404 status code and serve the 404 page to end user.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Required Information
Expected Behavior
In our application, CUG are applied on all page except login page. When a page is accessed with actual url, user gets redirected to the login page and after logging in, page opens. Same should be the behavior with Vanity Url. If a user access the page with vanity url, if user is not logged in, it should be redirected to login page and if user is logged in, page should be open.
Actual Behavior
When a user try to access the page with vanity url, user gets 404 page instead of redirected to login page.
Steps to Reproduce
Created some pages, addd vanity url, and apply CUG on it. Install ACS Commons 3.13 version. Open ACS AEM COMMONS - Error page handler service in ConfigMgr and enable 'Vanity Dispatch Check'. Now access the page using vanity url. It will give 404 page.
We tried to debug it and found that, errorpagehandler's 404.jsp calls a service(vanityURLService) dispatch method. In this service, there is method isVanity which checks for the vanity path. But it uses current user resource resolver to resolve the path. Because, current user is not logged in and page is secured, resource resolver resolve method returns non-existing resource.
There are some logic performed which eventually returns false to jsp.
Now as response is false, jsp sets 404 status code and serve the 404 page to end user.
The text was updated successfully, but these errors were encountered: