Apache handlers control how the web server processes specific file types.
They tell the server which engine or interpreter should handle a file when it is requested.

Apache handlers affect how websites execute scripts.

What an Apache Handler Does #

An Apache handler:

• Links a file type to a processing method
• Determines how files are executed or displayed
• Controls how dynamic content is handled

Without a correct handler, files may not work as expected.

Common Apache Handler Examples #

Typical handler use cases include:

• PHP files processed by a PHP engine
• Scripts executed instead of downloaded
• Custom processing rules for specific file types

Handlers do not change file content, only how it is handled.

Apache Handlers and PHP #

PHP execution depends on handlers.

Handlers determine:

• Which PHP version processes .php files
• Whether PHP is executed or treated as plain text

PHP version selection is usually managed via MultiPHP Manager.

When Apache Handlers Are Used #

Apache handlers are used when:

• Running scripts on the server
• Hosting dynamic websites
• Supporting multiple runtime environments

Most CMS platforms rely on default handlers.

Managing Apache Handlers in cPanel #

Apache handlers can be viewed or adjusted via:

• Apache Handlers in cPanel

Changes apply immediately and affect the entire account.

Common Use Cases #

You may need to adjust handlers if:

• A script downloads instead of running
• A specific file type must be executed
• A custom application requires a handler

Most standard websites do not require changes.

Common Mistakes #

• Removing default handlers
• Assigning handlers to incorrect file types
• Breaking PHP execution
• Applying changes without testing

Incorrect handlers can make websites unusable.

Security Considerations #

Improper handler configuration can:

• Expose source code
• Allow unintended script execution
• Create security risks

Only configure handlers if you understand their effect.

When Not to Change Apache Handlers #

Do not change handlers if:

• Your website works correctly
• You are using WordPress or similar CMS
• You do not fully understand the requirement

Default configuration is safe for most users.

Responsibility Notice #

You are responsible for:

• Any handler changes you apply
• Ensuring website functionality after changes
• Reverting misconfigurations if needed

ProRedLine does not automatically restore handler settings.