Its not safe to remove POST from CSRF filter. I would recommend logging a support ticket to further debug the issue rather than removing the POST

You have the wrong URL. The correct URL for new package share is below: https://experience.adobe.com/#/downloads/content/software-distribution/en/general.html 

This is caused by the session timeout which is configured in OSGI. Check [1] for more details. Increase the timeout to resolve the issue. [1] https://helpx.adobe.com/ca/experience-manager/kb/How-to-set-token-session-expiration-AEM.html 

The best way to do this is to check why minification is failing, Setup a DEBUG logger on "com.adobe.granite.ui.clientlibs" and Follow the steps below: - Go to <host>:<port>/libs/granite/ui/content/dumplibs.rebuild.html- Invalidate Cache- Rebuild Libraries- Check the debug logger for errors.

@gangula2018  - The architecture of the AEM cloud is different than AEM 6.5 and below. When you upload Assets to AEM cloud, they are not uploaded to AEM but to the backend data store and AEM just gets the signed URL to read/update the binary from Datastore. So, it's not comparable with traditional A...

Upgrade needs to be run on each instance separately and make sure you are starting the instance with the correct run mode. EX: Starting author with "author" runmode That said, you need to run repository migration between step 4 and 5. See detailed steps at [1] [1] https://experienceleague.adobe.com/...

Instead of removing POST(Not safe), you can allow specific hosts that can make POST calls to AEM in the "Allowed Hosts" section. EX: If www.example.com is making a POST call to AEM which is failing, you can add "allowed host"= "www.example.com" and it should start working. Share the error.log if thi...

AD0-E103 was retired as of Dec 30, 2020 and can no longer be scheduled. See [1] for more details It is replaced by AD0-E116 which is the newer version of the Sites Developer Exam[2]  [1] https://spark.adobe.com/page/xHrRpsYWplZF0/ [2] https://spark.adobe.com/page/IN3bRhRJDvqCc/ 

This is working as designed. The product team implemented this change to move towards unified login via "/libs/granite/core/content/login.html"

You can use the AEM Modernization tools for this conversion. See [1] for more details [1] https://opensource.adobe.com/aem-modernize-tools/pages/tools.html