Topic: Client denied by server configuration: ".htaccess

[PremM]

Hi All,
I am trying a webpage siremis whenever i try to login i am getting below error in error log of apache

[client 192.168.137.7:4758] AH01630: client denied by server configuration: /opt/siremis-4.0.0/siremis/.htaccess

in httpd.conf following is the rule
Alias /siremis "/opt/siremis-4.0.0/siremis"
<Directory "/opt/siremis-4.0.0/siremis">
Options Indexes FollowSymLinks MultiViews

AllowOverride None
Order deny,allow
Allow from all
<FilesMatch "\.xml$">
Order deny,allow
Allow from all
</FilesMatch>
<FilesMatch "\.inc$">
Order deny,allow
Allow from all
</FilesMatch>

</Directory>


i am using apache 2 and php 5.5.1 and mysql 5.6.12

Please let me know how to overcome this issue.


Thanks and Regards,
Prem Chandiran M

[glsmith]

I'm going to assume Siremis came with a .htaccess file included, which is why in their install directions they have defined;

AllowOverride All

You have AllowOverride set to none which means there cannot be any .htaccess file, or at least it cannot have anything in it.

[PremM]

Hi glsmith,
Thanks for your reply.
yes siremis comes with .htaccess file, if i set AllowOverride All then i am getting 403 forbidden. After changing AllowOverride None i am able to access the page but login fails due to .htaccess error.
in httd.conf
i can see below line
#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<Files ".ht*">
Require all denied

</Files>
if i make Require all as granted then apache stops writing error log

Please let me know how to resolve.

[glsmith]

<Files ".ht*">
Require all denied
</Files>

This must stay as denied, or anybody can see the .htaccess and .htpasswd files that may be laying around.

Since I am now noticing that you are running 2.4, change all:

Order Allow, Deny
Allow from all

to simply:

Require all granted

Apache 2.4 doesn't like mix and match old style/new style auth/access directives. Even with mod_access_compat loaded, one or the other will cause a 403. It's best to get everything one style or the other, might as well just go with the new style and do not even load mod_access_compat module.

Is this a bug? Not sure but it is the reality I had run into when I started using 2.4. It is definitely not what one expects from mod_access_compat though!