@sravs  - That really helped. Thanks for the swift response. We will completely remove requestResponseFactory usage as well once the complete logic is sorted out since that is the main priority as of now.  FYI @rahulh56481972 

@sravs Above solutions are the recommendations to create a HttpServletRequest object which is still valid via com.day.cq.contentsync.handler.util.RequestResponseFactory object. Our problem is regarding getMD5 method since it is deprecated we are looking for an alternative for the same to hash the re...

@sravs I am trying to use MD5 method in thecom.day.cq.contentsync.handler.util.RequestResponseFactoryto get the MD5 hash of the response body, modify the content and store it into the node. Is there any equivalent method from another API class which can be used for the same purpose? This is a blocke...

@Jörg_Hoh  - I am facing the same issue where the post servlet is accessed via AWS domain is giving out 204 no content response. The same is working via Postman where the servlet is redirecting to the success page.  Could you please help us why dispatcher is returning the 204 no content when accesse...

@Kishore_Kumar_  The above dispatcher header rule is not working if we add it in the project file /conf.d/enabled_vhosts/<project_publish>.vhost for the AEM as a Cloud Service project. Could you please confirm where this needs to be added.

@SeanMc5 It seems that existing URL based format allow is not working. i.e. /0112 { /type "allow" /url "* *.webp *" } # enable webpThe above code is not working. The below code is working in AEM as a Cloud Service /0138 { /type "allow" /method "GET" /extension '(css|eot|gif|ico|jpeg|jpg|js|gif|png...

@Sean-McK  - Just to confirm the dispatcher filters are the only fix provided as part of the issue. I am facing the same issue for WEBP images in the AEM as a Cloud Service dispatcher. 

@arunpatidar We have a code which uses CQ Asset API to create assets in the DAM programmatically. Is the asset upload the only programmatic solution available now or Granite Assets API can be used. I don't want to go via AEM developer console to upload the assets due to time constraints.  FYI @ritik...

@arunpatidar - The CQ Asset API is now deprecated in Cloud. So have to use Granite Asset API. In that case the  above issue will occur again. Is there a way to create an asset using Granite Asset API with the right metadata. As per the Adobe API DOC, there is not method of Asset as well to do this. ...

This needs to be via the error handler based solution proposed by AEM ACS commons (https://adobe-consulting-services.github.io/acs-aem-commons/features/vanity-path-rewrite-mapper/index.html) and use the custom VanityURLServiceImpl in your code to handle the vanity solution. Please let me know if you...