Bug 25614 - RFE: Add documentation on ~public_html permissions requirements
Summary: RFE: Add documentation on ~public_html permissions requirements
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: apache
Version: 7.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact: David Lawrence
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-02-02 04:03 UTC by R P Herrold
Modified: 2007-04-18 16:31 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2001-02-02 04:47:09 UTC


Attachments (Terms of Use)

Description R P Herrold 2001-02-02 04:03:05 UTC
Add a brief explanation of the need to chmod 0771 ~userid, and
~userid/public_html in httpd.conf.  The existing text is Apache 
generic and does not reflect the Red hat approach to home directory
security ...

Position it just above:

UserDir public_html 

-------proposed text------
#
#     The path to the end user account 'public_html' directory must 
#     accessible to the webserver userid.  This usually means that 
#     ~userid must have permissions of 711 and ~userid/public_html 
#     must have permissions of 755 
#
#     To the client browser, an error such as:
#        Forbidden
#  You don't have permission to access /~username on this server
#
#     And /var/log/htpd/access_log will have a '403' return 
#     respecting the path in question:
#
#     10.0.0.2 - - [01/Feb/2001:22:00:06 -0500] \
#           "GET /~userid  HTTP/1.0" 403 206 
#                                   ^^^^^ -- note the '403'
#     Thiis is NOT an execution error, so far as the web SERVER 
#     is concerned -- just a proper return of a 403 code in the
#     ACCESS_log.
#

----------------text ends---------------------

Comment 1 R P Herrold 2001-02-02 04:47:05 UTC
also suggested -- add a link:
   http://httpd.apache.org/docs/misc/FAQ.html#forbidden

Comment 2 Nalin Dahyabhai 2001-02-23 20:09:32 UTC
Done.  It'll show up in 1.3.14-12.


Note You need to log in before you can comment on or make changes to this bug.