Serendipity Forums

s9y oviously ignores the
setting in apache2-config and assumes it set to .htaccess constantly.

Background: for security or compatibility issues you may want to move away from files nameed .htaccess to files named whatever lets say .xyz.

as for compatibility issues there is an easy workaround by just linking
you may nevertheless wish to prevent that link if you chose to use the AccessFileName Directive for security reasons.

As it should not be too hard to read the AccessFileName setting of the apache2.conf File from php, one might want to change the very code to use the setting made by the siteadmin instead of constantly writing to .htaccess (which is probably not used according to what was mentioned above. (e.g. in line 57 of /include/admin/configuration.inc.php)

Hi!

Yes, there is no way for PHP-Scripts to detect that setting of Apache. It's an apache setting that PHP has no knowledge of.

You could configure the filename of .htaccess in s9y, but IMHO this makes things too complicated. I hardly know of setups where people really use different names for that file

So if you change it, you will need to patch code - I don't think a config setting for this would help most people, it would only confuse more people...?

As it should not be too hard to read the AccessFileName setting of the apache2.conf File from php

It would be hard. You would need to parse the whole file, parse out specific Virtual Hosts etc. Also, you don't know where the Apache config file lies exactly. And you would need to parse "Include" settings of that file because the directive could be in different files. Parsing this file is WAY too much work

Best regards,
Garvin

Yeah garv,

I'm totaly with you.

A user accesible config-setting would be too much for this.

Though one could probably think of putting this into a config file only accessible to Installation Admins (same as) setting in serendipity_config.inc.php.

I realy was not aware and will have to convince myself oneday, that this is a "per virtual host" setting, as I knew AccessFileName only from apache2.conf as a Global per Server setting.

But actually even this file has root:root as owner an you're right, that on many (hardened) machines you will not have 755 settings on that to make it redable by the apache-chrooted-user.

Sorry for suggesting this.

regards
Michael