• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Possible Bug: .php files in aliased path's are not executed...

neutron

New Pleskian
Hi there,

Trying my best to explain what i mean. First of all, normal websites function properly, whatever php version and settings i choose, works perfect. When i'm inserting additonal directives for a vhost, in this case an alias for a application, as example (example.com/index.php works normally):

Code:
Alias /webaccess /usr/share/webaccess

<Directory /usr/share/zarafa-webaccess/>
    DirectoryIndex index.php
    Options -Indexes +FollowSymLinks
    AllowOverride Options

    <IfModule !mod_authz_core.c>
      Order allow,deny
      Allow from all
    </IfModule>
    <IfModule mod_authz_core.c>
      Require all granted
    </IfModule>
</Directory>

This would lead to the url example.com/webaccess.

The strange part, while example.com/index.php works as normal, example.com/webaccess downloads the index.php which is in "/usr/share/zarafa-webaccess/". It's like PHP is completely disabled in this aliased location, but WHY ? What i'm overseeing here ? I know that worked before, but now with this fresh install of CentOS 7 and Plesk i have this behaviour.

Any help would be really nice.

regards,

Markus
 
You didn't add a handler for PHP.

In plain English: In this section, Apache doesn't know what to do with a PHP file, so it treats it just like any other file. PHP files are processed server side, and output (mostly) HTML after execution.
 
Since when do i need to do this ? On my old Server, also using Plesk 12.5 but CentOS 6 this worked out of the box without adding an extra handler. This information is just set up in the vhost.conf and/or vhost_ssl.conf so it should use the php version/handler that is already set up for the whole domain, we are just talking about an alias with another location, but still using the same domain.

So, the only difference is CentOS 6 with Apache 2.2, vs CentOS with Apache 2.4
 
BTW, IF i supply a handler (which can't be the way) i get "No Input File specified.". There's something wrong for sure.
 
Back
Top