Problems with .htaccess options FollowSymLinks and SymLinksifOwnerMatch – are they really needed?

[nurkka]

I often have problems with the ProcessWire .htaccess file. As my clients are using different hosting providers and I am working with DDEV locally, I have to deal with htaccess issues very often. The main problem seems to be the directive `Options +FollowSymLinks` and `Options +SymLinksifOwnerMatch`, but sometimes also the other options, which are marked as error 500 critical in the ProcessWire htaccess file. Currently, I have a project with two different htaccess files, because the staging and production server allow and deny different options.

- Is `Options +FollowSymLinks` or `Options +SymLinksifOwnerMatch` really needed? Or can they be omitted?

 

[bernhard]

Both directives are needed if you have symlinks in your setup, which will be the case if you use RockMigrations deployments for example. If you don't have any symlinks I guess you could remove them, but I'm not sure if anything else needs them.

I don't have any problems with DDEV.

[nurkka]

Thanks @bernhard , for the info, that RockMigrations deployments are using symlinks. I am using RockMigrations but not RockMigrations deployments (yet).
So if ProcessWire doesn't use symlinks, I could simply comment out those two symlink directives and would have only one version of my .htaccess to maintain.
Do you or does anybody know if ProcessWire itself uses symlinks?

[bernhard]

11 minutes ago, nurkka said:

So if ProcessWire doesn't use symlinks, I could simply comment out those two symlink directives and would have only one version of my .htaccess to maintain.
Do you or does anybody know if ProcessWire itself uses symlinks?

Or something like this? (untested, never used)

<If "%{HTTP_HOST} == 'foo.ddev.site'">
    Options +FollowSymLinks
</If>
<Else>
    Options +SymLinksifOwnerMatch
</Else>

 

[nurkka]

Wow, I never thought that would be possible – although I am using something similar in my config.php 🙂

Thanks @bernhard !