We use this same setup on our 6.2 AEM instance and everything works correctly. When I navigate to stage.site1.com/en_us/home.html the content appears on our 6.2 instances, however, when I switch our CDN (Content Delivery Network) to point to 6.3 instead of 6.2 I receive a 404 error but only have I am redirected to a login page.
AEM Resource Mapping Structure
- /etc/map
- http
- stage.site1.com
- https
- stage.site1.com
Properties for stage.site1.com
- sling:match = en_us
- sling:internalRedirect = /content/site1/en_us
Problem
The resource mapping is not allowing me to view the content on the correct URL. stage.site1.com/content/site1/en_us/home.html works, however, stage.site1.com/en_us/home.html does not work, only redirects me to an AEM login screen before throwing a 404 error.
Questions:
1) Did anything change between 6.2 and 6.3 when it comes to resource mapping?
2) Are there any settings in SLING I should check to validate that Adobe set up our new 6.3 environments correctly?
Solved! Go to Solution.
To fix this, below were the changed that were done:
(1) : http://HOST:PORT/system/console/configMgr/com.day.cq.rewriter.linkchecker.impl.LinkCheckerImpl
(2) : http://HOST:PORT/system/console/configMgr/org.apache.felix.http
To fix this, below were the changed that were done:
(1) : http://HOST:PORT/system/console/configMgr/com.day.cq.rewriter.linkchecker.impl.LinkCheckerImpl
(2) : http://HOST:PORT/system/console/configMgr/org.apache.felix.http