I had the same problem, but I managed to resolve this issue.
However, the accepted answer may not be the best solution, depending on how secure your Apache configuration is.
I think that the solution should mention two things: first, security is not compromised, but the second; Understanding the difference in access control configuration between Apache versions 2.2 and 2.4.
Security is not compromised
Commenting out the suggested lines:
<Directory /> AllowOverride none Require all denied </Directory>
Allows you to remove the default default protection that applies to all directories on your machine, as I understand it. Someone else can create a configuration that points to your C:\very\sensitive\information directory and send content from there to the website (which is likely to be a problem for the shared host). Interestingly, the following comment was made on this block:
# First, we configure the "default" to be a very restrictive set of
Then under this block:
Everything makes sense to block everything, then conditionally unlock for each directory.
I came up with the following, which indicates the location on my machine where all my sites (served through Apache virtual hosts) will live. This immediately follows the <Directory "d:/wamp/www/"></Directory> block.
<Directory "d:/wamp/sites/"> Options Indexes FollowSymLinks AllowOverride all Require all granted </Directory>
Then, in each of your virtual host configurations / aliases, you can set the configuration that applies to this directory.
The difference in access control configuration
Access control settings in later versions of Apache have changed.
Before:
Order allow,deny Allow from all
Must be:
Require all granted
For more information: http://httpd.apache.org/docs/current/upgrading.html