[Httpd Wiki] Update of "Errors/13PermissionDenied" by NoirinPlunkett

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Httpd Wiki" for change notification.

The following page has been changed by NoirinPlunkett:
http://wiki.apache.org/httpd/Errors/13PermissionDenied

The comment on the change is:
Tidying

------------------------------------------------------------------------------
  = (13) Permission Denied =
- '''Error 13 indicates a filesystem permissions problem. That is, Apache was denied access to a file or directory due to incorrect permissions. '''See ''man chmod'' for details on fixing these.
+ '''Error 13 indicates a filesystem permissions problem. That is, Apache was denied access to a file or directory due to incorrect permissions. '''
  
- gnu based systems often have a {{{namei}}} program that helps in viewing the permissions of a complete path.
+ On *nix systems, use {{{ls -l}}} to see the current permissions, and see {{{man chmod}}} for details on fixing these.
  
- You should check the permissions of that file.  Make sure that the user your Apache server runs as can at least read the file.
+ GNU based systems often have a {{{namei}}} program that helps in viewing the permissions of a complete path.
  
- Files need to be readable by the Apache user (e.g. 644).  Directories and scripts need the x bit too (e.g. 755).  That includes *all* parent directories of a resource.  If you have !AllowOverride for an unreadable directory, the error message will refer to .htaccess
+ Make sure that the file to which permission was denied is at least readable by the Apache user (eg {{{-r--r--r--}}} or 444 as a minimum. {{{-rw-r--r--}}} or 644 is more usual). 
  
- Use 'setenforce 0' to test if it is a selinux issue and use chcon to fix permissions. Use ls -alZ to view current permissions.
+ Directories and scripts also need to be 'executable' ({{{dr-xr-x-r-x}}} or 555. {{{drwxr-xr-x}}} or 755 is more common). This includes '''all''' parent directories of a resource too!
  
- ''noodl: The !AllowOverride and .htaccess error has a different message''
+ {{{setenforce 0}}} can be used to test if this is caused by a SELinux issue - in that case, use {{{chcon}}} to fix permissions. Use {{{ls -alZ}}} to view current permissions on such systems.