Apache [forbidden 403]错误的解决办法

2007-11-05 00:13:47  来源:网页教学网 站长整理

WebjxCom友情提示:今天准备试着在Apache服务器上配置用户目录(User Directory)。遇到一个棘手的问题,现将配置过程和问题及其解决总结如下

今天准备试着在Apache服务器上配置用户目录(User Directory)。遇到一个棘手的问题,现将配置过程和问题及其解决总结如下:

adduser web           
passwd  web

mkdir public_html
chmod 755 public_html -R

# UserDir: The name of the directory that is appended onto a user's home
# directory if a ~user request is received.
# The path to the end user account 'public_html' directory must be
# accessible to the webserver userid.  This usually means that ~userid
# must have permissions of 711, ~userid/public_html must have permissions
# of 755, and documents contained therein must be world-readable.
# Otherwise, the client will only receive a "403 Forbidden" message.
# See also: http://httpd.apache.org/docs/misc/FAQ.html#forbidden
<IfModule mod_userdir.c>
    # UserDir is disabled by default since it can confirm the presence
    # of a username on the system (depending on home directory
    # permissions).
    #UserDir disable
    # To enable requests to /~user/ to serve the user's public_html
    # directory, remove the "UserDir disable" line above, and uncomment
    # the following line instead:
    UserDir public_html


You don't have permission to access /~web on this server.

Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.


Apache/2.0.54 (Fedora) Server at Port 80


用Google以Apache 403搜了好一会,终于在一个博客里看到,作者遇到和我完全相同的问题:Apache、目录的配置都没问题,但就是不能显示页面。而解决方法恰恰就是修改Selinux对public_html的访问控制。
chcon -R -t httpd_user_content_t public_html/ 


Fedora Core 5 SELinux FAQ
http://fedora.redhat.com/docs/selinux-faq-fc5/#faq-entry-public_html Q:  How do I make a user public_html directory work under SELinux? 
A: This process presumes that you have enabled user public HTML directories in your Apache configuration file, /etc/httpd/conf/httpd.conf. This process only covers serving static Web content. For more information about Apache HTTP and SELinux, refer to http://fedora.redhat.com/docs/selinux-apache-fc3/. 

If you do not already have a ~/public_html directory, create it and populate it with the files and folders to be served. 

cd ~mkdir public_htmlcp /path/to/content ~/public_html

At this point, httpd is configured to serve the contents, but you still receive a 403 forbidden error. This is because httpd is not allowed to read the security type for the directory and files as they are created in the user's home directory. Change the security context of the folder and its contents recursively using the -R option: 

ls -Z -d public_html/drwxrwxr-x  auser    auser    user_u:object_r:user_home_t      public_htmlchcon -R -t httpd_user_content_t public_html/ls -Z -d public_html/drwxrwxr-x  auser    auser    user_u:object_r:httpd_user_content_t public_html/ls -Z public_html/-rw-rw-r--  auser    auser    user_u:object_r:httpd_user_content_t bar.html-rw-rw-r--  auser    auser    user_u:object_r:httpd_user_content_t baz.html-rw-rw-r--  auser    auser    user_u:object_r:httpd_user_content_t foo.html

You may notice at a later date that the user field, set here to user_u, is changed to system_u. This does not affect how the targeted policy works. The field that matters is the type field. 

Your static webpages should now be served correctly. If you continue to have errors, ensure that the Boolean which enables user home directories is enabled. You can set it using system-config-securitylevel. Select the SELinux tab, and then select the Modify SELinux Policy area. Select Allow HTTPD to read home directories. The changes take effect immediately. 


ls -Z -d public_html/
      #显示文件/目录的安全语境-Z, --context
             Display  security context so it fits on most displays.  Displays only mode, user, group, security              context and file name.-d, --directory
              list directory entries instead of contents, and do not dereference symbolic links

chcon -R -t httpd_user_content_t public_html/
       #修改文件/目录的安全语境-R, --recursive
              change files and directories recursively-t, --type
              set type TYPE in the target security context