0

I have a problem with apache 2.4 in debian 8. I am using virtualhosts in apache with fake domains (example.42). What happens is that when I do the example.42.conf file and I enable it to a2ensite example.42, when I enter the browser I miss an error 400: Bad request, do you know why it will be?

The domain is pointed correctly to the apache (I already made pings and everything well). There are people who tell me that it is apache problem, which is misconfigured virtualhosts. I already tried with all the settings and it does not remove the error.

The file virtualhost:

<VirtualHost *:80> 
ServerName example.42 
ServerAdmin webmaster@example.42 
DocumentRoot /var/www/html 
ErrorLog ${APACHE_LOG_DIR}/error.log 
CustomLog ${APACHE_LOG_DIR}/access.log combined 
</VirtualHost>
Abraham Morales
  • 101
  • 3
  • 13

1 Answers1

0

The problem is the domain ".42", because apache has http header settings and the ".42" domain is invalid to verify https://httpd.apache.org/security/vulnerabilities_24.html (CVE-2016-8743)

Possible solution (not recommended for sysadmin): Changing the HttpProtocolOptions Strict variable by HttpProtocolOptions Unsafe

Check: http://httpd.apache.org/docs/2.4/en/mod/core.html#HttpProtocolOptions

Abraham Morales
  • 101
  • 3
  • 13