Expand my Community achievements bar.

Nomination window for the Adobe Community Advisor Program, Class of 2025, is now open!

Server Side Include(SSI) in IIS with AEM Dispatcher

Avatar

Former Community Member

I am using Dispatcher 4.1.8 with IIS7.5. On interpreting the '<!--#include virtual=path'  SSI tag, getting an error 'Error Processing SSI file' on the page.

But the same is working with Apache HTTP server.

4 Replies

Avatar

Level 10

Have you configured IIS to handle SSI?  From the logs is request going to dispatcher & then publish,If so verify IIS config

 

http://tech.mikeal.com/blog1.php/server-side-includes-for-html-in-iis7

Avatar

Former Community Member

Yes, I have enabled SSI in IIS as per the link you gave. There are nothing in the logs (request and dispatcher logs) for the page to be included dynamically.

But one thing what i have observed is that, if I manually cache the page in the docroot location, the SSI tag is replaced by the actual content. But in this case the content is what cached in the docroot location of dispatcher.

Avatar

Level 10

AEM Dispatcher with IIS wrote...

Yes, I have enabled SSI in IIS as per the link you gave. There are nothing in the logs (request and dispatcher logs) for the page to be included dynamically.

But one thing what i have observed is that, if I manually cache the page in the docroot location, the SSI tag is replaced by the actual content. But in this case the content is what cached in the docroot location of dispatcher.

 

If i understand correctly cq caching the page replacing ssl with actual content. This should not happen please file daycare request we can take a look.

Avatar

Level 5

To resolve the "Error Processing SSI file" in IIS with AEM Dispatcher:

  1. Enable SSI in IIS:

    • Go to IIS Manager > Handler Mappings.
    • Add Script Map for SSI: Request path: *.shtml, Executable: C:\Windows\System32\inetsrv\ssinc.dll.
  2. Configure Dispatcher:

    • Ensure Dispatcher is not blocking or caching SSI files in the dispatcher.any config.
  3. Check File Extensions:

    • Ensure your file has .shtml extension or IIS is configured for .html with SSI.

Test by creating a simple .shtml file to verify the setup.