Since you are getting 403 due to default GET servlet, this means that the URL is not mapping to a resource. It is possible the "provided navigation option" was generated wrong. It is possible the trailing / is to blame and could be checked first. Additionally see if the servlet (as a component) and ...

Found the answer, but it took a while dealing with environments with restrictive permissions.1) The dispatcher filter rules were correct. 2) No need to remove the vanity URLs section3) Found that the DNS routed the traffic to a different vhost in this multi-vhost environment4) And this routed the tr...

@sashi_mulugu does dispatcher treat xml extensions as vanity URLs? All other URLs are not treated like this and are getting rendered fine.

We have sitemap configured as /en/sitemap.xmlThis is working as expected in the publisher. However while accessing from dispatcher, see the following the dispatcher logUnable to fetch vanity URLs from [ip-address]:4503/libs/granite/dispatcher/content/vanityUrls.html: remote server returned: HTTP/1.1...

You might want to uncheck isDeep property. This is explained here - https://helpx.adobe.com/experience-manager/6-3/sites/administering/using/tc-rules.html

You would want to verify what @Jaideep_Brar suggests.  Assuming you are talking about page load time in your "site", there might be other factors at play as well Cache ratioSpecific component logicVolume of trafficClientlibs load time in browserbreaking JSIf in author, also look at the "developer mo...

When you say homepage, this is AEM Admin page? Or is the homepage part of the site you built on AEM? In any case, for such errors, you need to troubleshoot, starting with the logs.

If I have to think through the need for this, I can assume that 1) You have (to manage) static and editable templates2) (at least some of the )New components need to be supported in both static and editable templates3) Since one is developing components with style system, might want to leverage the ...

It is possible Chrome would be expecting some headers that is missing in 6.5 vs 6.4. You might want to scan the response headers in 6.4 vs 6.5 and find if something might be missing. 

Try "Move" Page option