Apache 2.0 changed the default DocumentRoot permissions to be very restrictive. While I can’t argue this is a better security paradigm than less restrictive default permissions, in the real world upgrading a server with 300+ domains, it can be a pain to script permissions changes in all of the config files.
<Directory />
AllowOverride None
Order Deny,Allow
Deny from all
</Directory>
AllowOverride None
Order Deny,Allow
Deny from all
</Directory>
Change the default permissions to be less restrictive with this instead:
<Directory />
AllowOverride None
Order Deny,Allow
</Directory>
AllowOverride None
Order Deny,Allow
</Directory>
[ad#Google Story Inline]
Popularity: 100% [?]
{ 6 comments… read them below or add one }
Terrific fix. Many thanks.
Lovely lovely lovey
That was it
thx!
At last! Thank you very much for this info.
I’m doing some Apache/PHP/mySQL tutorials and not being able to start my personal web pages for testing was driving me insane. All is well with the world now and I can stick my virtual hair back onto my head.
thanks a lot . You save my job. I have confused with this error for a week, try to solve it from google but always fail. Until I find the right solution from you. Thank you guy!
Hi, I am getting a 403 error for all my static content which should be served by apache. I tried to comment out the line which you have mentioned above, but that did not take care of the error. I have checked all the permissions and the apache user has permissions to view all the static content. What could the problem be???? Please help as we go live in a week!!!
Have you looked in the error log to see the full error?
{ 1 trackback }