Titbits: Making Ape work with Plesk 9.5.1

If you have Ape and Plesk installed on your server, you may come across the issue that Ape is not working in it’s entirity. This may be caused by the fact that Plesk overrides the handlers list for each domain it creates. Like this:

<location path="Example.com">
        <system.webServer>
            <handlers accessPolicy="Read, Script">
                <clear />
                <add name="Plesk_Handler_05171048" path="*.dll" verb="*"
                    modules="IsapiModule" resourceType="File"
                    requireAccess="Execute" allowPathInfo="true" />
                <add name="Plesk_Handler_05171080" path="*.exe" verb="*"
                    modules="CgiModule" resourceType="File"
                    requireAccess="Execute" allowPathInfo="true" />
                <add name="StaticFile" path="*" verb="*"
                    modules="StaticFileModule,DefaultDocumentModule,
                    DirectoryListingModule" resourceType="Either" />
            </handlers>
            ...
    </location>

To add handler for Helicon Ape, you need to add this simple spell to the root web.config for the site:

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
  <system.webServer>

    <handlers>
      <add name="Helicon.Ape Handler" path="*.apehandler" verb="*"
          type="Helicon.Ape.Handler" resourceType="Unspecified"
          preCondition="integratedMode" />
    </handlers>

  </system.webServer>
</configuration>

Guess, this small hint will make Plesk and Ape cohabitation on your server more peaceful.

Best regards,
Sergey, Anton – Helicon Tech Team

This entry was posted in Helicon Ape and tagged . Bookmark the permalink.

482 Responses to Titbits: Making Ape work with Plesk 9.5.1

  1. Johnny Smith says:

    Really illuminating appreciate it, I do think your subscribers would definitely want a great deal more articles along these lines carry on the great hard work.