Hi Mahedi,   PageManager expects a fully qualified path.   Since you already have ResourceResolver and Request as well as absolute path, add an extra invocation to retrieve the actual absolute path by calling: @Mahedi_Sabuj wrote: Let's assume we have a servlet (resource type binding) that retrieves...

Hi Pamela,   Attachement as attachement rules are dictated by the headers that you supply with your files from your server stack.   mod_headers.so file in Apache directory has the right capabilities to set headers.   Following rule added to appropriate vhost and applied to expected filepath's or ext...

Hi Jay,   Most importantly if Content Authors/other users are using the environment, warn them of possible down time. So, that no user of author instance is disappointment with the downtime. Possibly prepare a downtime message on Dispatcher to warn users.   You need to examine any comms that happen ...

Hi Jazyac,   You can configure your webserver to write CSP header to the browser with all the allowed domains.   Regards, Peter

Hi Goyal,   Ideally, ask upstream system to encode the url before passing it into AEM. We ended up actually excluding plus from our token's to accept only letters, numbers and dashes.   Given it's not possible, you can configure Apache to URL Rewrite any + into %20 before sending into Publishers.   ...

Why do it on Publisher, would it not be better to do it in Webserver layer?   Regards, Peter 

Hi Ian,   Content Fragments implement Versionable API.   You can call listVersions[1] on your ContentFragment to list available version. Then you can use standard Versionable API to get content from the version you need.   Regards, Peter   [1] https://developer.adobe.com/experience-manager/reference...

Hi Aruna,   You can write an OSGi service to monitor native folders.  On Activate method mount callback's Apache Commons IO Library provides a neat FileAlterationListener interface.   on event such as onFileCreate(File file) {   }   You can create syntheticRequuest and use RequestDispatcher to call ...

Kindly attach screenshot with the error message. Peter

Hi Fionas,   You're welcome to use anything for your own build. As long as you can pack it into a clientlib you should be fine.   The problem comes that most OOTB codebase, Core Components, Archetype and the rest of AEM systems do not rely on Yarn, instead it's all npm based. Regards, Peter