It has been a while since I last wrote my blog entry. Lots of changes have happened in my life over the last few years and this is not the time or place to rant.
Introduction
I have started playing with AEM a.k.a Adobe Experience Manager which is Adobe’s platinum Web content management platform. As a part of learning the product, I have installed the following components on my local windows machine
- AEM Authoring Server
- AEM Publish Server
- AEM Dispatcher = which is a module installed within Apache HTTP Server 2.2
The following image shows the high level flow between the various components
- Using a browser we type in a URL to visit a website hosted using AEM. In our case this is the We.Retail sample page
- The Apache HTTP Server receives the request and sends it for processing using the configured modules
- The AEM Dispatcher module now receives the request and the checks if the page has already been stored in Cache
- If the page is not stored in Cache, the dispatcher makes a request to the AEM Publish server which then serves the page. The dispatcher now stores the received content/page in its cache on the file system
- The content originally comes from the Authoring server – which pushes the content to the Publish server using a set of “Replication” agents.
How are the Cached items stored
The dispatcher literally creates folders within the configured Cache directory and persists the HTML and static content received from the Publish server. In my case, I had configured the cache directory within the htdocs root folder.
My Apache server installation was under
C:/Users/
The DocumentRoot folder was under
C:/Users/
Cached items are stored under htdocs like
C:/Users/
What exactly is the issue
The above error essentially prevents the image from being served by the HTTP Server and throws a 403 forbidden error