[users@httpd] Re: 0 length robot.txt
On 03 Oct 2018, at 12:07, Filipe Cifali <cifali.filipe@xxxxxxxxx> wrote:
> you can check what virtualhost is being served via apache2ctl like this: $ apache2ctl -S
> $ apache2ctl -h provides this info:
> -S : a synonym for -t -D DUMP_VHOSTS -D DUMP_RUN_CFG
Yes that is all fine, and the site was loading perfectly for almost three and a half hours.
port 443 namevhost www.XXX.com (/usr/local/etc/apache24/users/XXX.conf:1)
port 80 namevhost www.XXX.com (/usr/local/etc/apache24/users/XXX,conf:26)
I do not have an apache2ctl, just apachectl (apache 2.4 FreeBSD 11.2-REALEASE compiled from ports)
> After checking that the right vhost is being served, start removing proxy logic and just make the txt work again, then slowly start adding the proxy config to make the php work again.
There is exactly one line in the site configuration that, when commented, makes the site work again. Though, possibly only for a little while. I’ll have to check more in 3-4 hours. There is no other proxy logic at all.
> If you can, post the full vhost here regarding the domain that misbehaves.
Sure, but other than the host name, it is identical to all the other sites.
#ProxyPassMatch ^/(.*\.php)$ fcgi://127.0.0.1:9000/www/XXX/$1
Options +Indexes +FollowSymLinks +MultiViews -SymLinksIfOwnerMatch
Require all granted
SSLProtocol ALL -SSLv2 -SSLv3
# 15638400 seconds is 181 dayds
# 63072000 seconds is 730 days
Header always set Strict-Transport-Security "max-age=15638400; includeSubdomains;"
Header always set X-Frame-Options DENY
CustomLog /home/user1/logs/XXX.access_log combined
> The important part is: Having a zeroed robots.txt doesn't break httpd.
Yeah, it didn’t seem likely, but then again it seemed to work for q bit…
And, just for kicks:
# apachectl -M
# cat /www/XXX/.htaccess
Options +Includes +FollowSymLinks +MultiViews
One tequila, two tequila, three tequila, floor.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx