Thanks for your input!The problem is that the webmasters wouldn't be able to maintain the map in /etc/map.For now, the solution has been to let them maintain the mappings in "site settings" for the standard global site. All the other sites then use those settings when mapping. Not the prettiest of s...

Which mapping? The "/content/gb.." -> "gb.mysite.com/.." which the Apache server is doing right now?I'm not quite sure why it's set up like that - but it's not something I can change, unfortunately.

Yup - I have access to the slingRequest variable as well as the other scripting variables provided by <cq:defineObjects />.However, if a user tries to access http://gb.mysite.com/nonexistingpage.html, then the request path is "/nonexistingpage" which doesn't exist. The nearest valid parent path is t...

On our site, we'd like to be able to maintain and serve custom/localized  error pages in the end-users' own language rather than just a standard customized page like /apps/sling/servlet/errorhandler/404.jsp.Right now, we're storing these localized pages as /content/<country>/<language>/errors/<error...