On 07/16/2018 02:53 PM, James Moe wrote:
> After the upgrade from v2.4.23 to v2.4.33, https requests yield error
> 403: Access forbidden!
> http requests return: error 400 Bad request!
>
I have read the docs. I have added what seemed like the correct
directive for allowing access. Still no access allowed.
What is incorrect with this vhost?
<VirtualHost *:80>
ServerAdmin jimoe@xxxxxxxxxxxxxx
ServerName sma-v3.sma.com
DocumentRoot "/data01/t-drv/websites/sma-v3"
ErrorDocument 404 /404.php
ErrorDocument 410 /410.php
ErrorDocument 401 /401.php
ErrorLog "/data01/t-drv/websites/.logs/sma-v3-error_log"
CustomLog "/data01/t-drv/websites/.logs/sma-v3-access_log" common
<Directory "/data01/t-drv/websites/sma-v3">
Options Indexes FollowSymLinks
AllowOverride All
Require all granted
</Directory>
</VirtualHost>
<IfDefine SSL>
<IfModule mod_ssl.c>
<VirtualHost *:443>
# General setup for the virtual host
DocumentRoot "/data01/t-drv/websites/sma-v3"
ServerName sma-v3.sma.com
ServerAdmin jimoe@xxxxxxxxxxxxxx
ErrorLog "/data01/t-drv/websites/.logs/sma-v3s-error_log"
CustomLog "/data01/t-drv/websites/.logs/sma-v3s-access_log" common
TransferLog "/data01/t-drv/websites/.logs/access_log"
ErrorDocument 404 /404.php
ErrorDocument 410 /410.php
ErrorDocument 401 /401.php
<Directory "/data01/t-drv/websites/sma-v3">
AllowOverride All
Options -ExecCGI
Options Indexes FollowSymLinks
Require all granted
</Directory>
SSLEngine on
SSLCertificateChainFile "/data01/srv/vhosts.sma/ssl/sma-ca-chain.cert.pem"
SSLCertificateFile "/data01/srv/vhosts.sma/ssl/www.sma.com.cert-01.pem"
SSLCertificateKeyFile
"/data01/srv/vhosts.sma/ssl/www.sma.com.insecure-01.key"
# SSLCipherSuite HIGH:!SSLv2:!ADH:!aNULL:!eNULL:!NULL
SSLProtocol ALL -SSLv2
</VirtualHost>
</ifmodule>
</ifdefine>
--
James Moe
moe dot james at sohnen-moe dot com
520.743.3936
Think.
Attachment:
signature.asc
Description: OpenPGP digital signature
|