Hi,if i understand correctly for current loaded page by author you need to provide the size.  it should be easy.  Get the Content-Length from header and covert to kilobytes ( by dividing with 1024).    Please note author & publish will have different size because in author has to inject other edit t...

Hi Narendra,Article [A] will help at what leve stat file is created. Send the log with debug enabled.[A]  https://cqdump.wordpress.com/2008/12/26/dispatcher-cache-content-delivery-and-invalidation/Thanks,

Hi Manish,Create a new config with all three trasnsformer & highest order.transformerTypes="[linkchecker,versioned-clientlibs,akamai-static,domainsharding]"Thanks,

Hi Naresh,It is doable. https://helpx.adobe.com/aem-forms/6-1/help-tutorials.html Please post at http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/aem-forms.html

Few users reported this issue. Using private window resolved the issue, We concluded it was browser caching issue. May be you can give that a try.

if aem6 with crx2 then make sure slingid is configured correctly. If crx3 then looks strange please engage with official support teamThanks,

Hi,For assets link sharing is oob [1] & you might need to implement same logic for pages.  We internal solve this requirement by having an seperate dispatcher with hardcoding preview user details along with wcm mode.[1]  https://docs.adobe.com/docs/en/aem/6-2/administer/content/assets/link-sharing.h...

General we follow guidelines of [1].  Most of connector and implementation have seen made use of alias you are reffering.  I am also waiting on community feedback on this.[1]   http://www.seerinteractive.com/blog/international-seo-strategy-guide/[2]     https://claytablet.zendesk.com/hc/en-us/articl...

Does not sound like a webserver issue.  Are you using the latest ACS?  Also is request protocoll changed http vs https.Can you send requesttracker file by accessing both aem directly & dispather?

The repo.adobe.com is not intended for browsable  thus not seeing the artifact  means it hasn't been requested via maven yet and thus not proxy-stored on repo.adobe.com yet.  If maven cannot retrieve the dependency, then engage with support team by providing the complete mvn -X output. So that they ...