Hi @anupam_miglani even if it solves your error, provide anonymous
access to /home/users path may be considered as a security risk for your
publish instance, if you do (which I would not recommend), you may want
to consider blocking any outside access to this resources from your
dispatcher servers as well as any querying process and CRX/DE.
Hello All, Found the root cause and was not related to the AEM
implementation but the VPN used to access to AEM.Since any access to our
network require VPN login, we never noticed that accessing from outside
the VPN actually loads all resources without any delay.Thank you for
your help on this thread, closing with cause "Not AEM related"
Thank you for your response @Sanjay_Bangar , is true that versioning can
add performance and even solve known issues when JS or CSS files cached
are not automatically flushed on web client after a code release,
however this is not the cause of the error since the author was loading
correctly and just start failinf from one day to another and the author
or dispatcher have not been found so far the cause of the incident, even
the performance on them.
Hello All,Early this week we received reports of users that have
challenges to modify Sites pages and CF in Author servers of lower
environments. When people click on edit a page on any author site, keeps
loading and loading up to 10 minutes and then the page is available for
editing.Looking into this error we start by identifying the files
causing this delay and one of these files was metadataeditor.js under