This is a discussion on newbie: priviledges of public_html? within the Apache Web Server forums, part of the Web Server and Related Forums category; Hello, I have configured Aapche to use UserDirs. I created public_html directory in ~robert folder but I don't know ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
"R.A.M." <r_ahimsa_m@poczta.onet.pl> wrote in message
news:fumg99$lh0$1@news2.task.gda.pl... > Hello, > I have configured Aapche to use UserDirs. I created public_html directory in > ~robert folder but I don't know what access rigths I should assign to it. > Please help. Thank you! > /RAM/ The user(s) should have rwx (owner). Apache needs rx (group, or others) to serve the pages. For individual files, rw owner and r for apache. I usually assign this subdirectory for each user to apache's group and use the s bit so that when users create more subdirectories, apache's group is automatically selected. In this setup, I set the access for others to none. |
|
|||
|
D. Stussy wrote:
> The user(s) should have rwx (owner). Apache needs rx (group, or others) > to serve the pages. > > For individual files, rw owner and r for apache. I usually assign this > subdirectory for each user to apache's group and use the s bit so that > when users create more subdirectories, apache's group is automatically > selected. In this setup, I set the access for others to none. I assigned priviledges to public_html as you described. Unfortunately I still receive (at localhost/~robert): Forbidden You don't have permission to access /~robert on this server. Please help. Thank you! /RAM/ |
|
|||
|
"R.A.M." <r_ahimsa_m@poczta.onet.pl> wrote in message
news:fuvuue$p6d$1@news2.task.gda.pl... > D. Stussy wrote: > > The user(s) should have rwx (owner). Apache needs rx (group, or others) > > to serve the pages. > > > > For individual files, rw owner and r for apache. I usually assign this > > subdirectory for each user to apache's group and use the s bit so that > > when users create more subdirectories, apache's group is automatically > > selected. In this setup, I set the access for others to none. > > I assigned priviledges to public_html as you described. > Unfortunately I still receive (at localhost/~robert): > Forbidden > You don't have permission to access /~robert on this server. > Please help. Is apache able to access ALL the directories above the "public_html" directory (usually "/", "/home", and "/home/*" for each user that has web pages)? If not, there's your problem. Apache needs at least "x" access (or "rx") to each of those. |
|
|||
|
Now I have:
drwxrwxr-x 6 robert apache 4096 maj 13 07:36 public_html but when I try to open localhost/~robert in browser, I still receive: Forbidden You don't have permission to access /~robert/ on this server. Please help. Thanks. /RAM/ |
|
|||
|
<r_ahimsa_m@poczta.onet.pl> wrote in message
news:g0cj15$mvs$1@news2.task.gda.pl... > Now I have: > drwxrwxr-x 6 robert apache 4096 maj 13 07:36 public_html > but when I try to open localhost/~robert in browser, I still receive: > Forbidden > You don't have permission to access /~robert/ on this server. > Please help. 1) Group access doesn't need "w". 2) Does Apache have "x" or "rx" access to "/", "/home", and "/home/robert"? |
|
|||
|
D. Stussy wrote:
> 2) Does Apache have "x" or "rx" access to "/", "/home", and > "/home/robert"? No, because I don't know how to assign apache group to priviledges of these folders. I use GNOME interface and when I choose Properties of folder I don't see field for new assigning group to the folder. Could you help me? /RAM/ |
|
|||
|
<r_ahimsa_m@poczta.onet.pl> wrote in message
news:g0e2q7$f01$1@news2.task.gda.pl... > D. Stussy wrote: > > 2) Does Apache have "x" or "rx" access to "/", "/home", and > > "/home/robert"? > > No, because I don't know how to assign apache group to priviledges of these > folders. I use GNOME interface and when I choose Properties of folder I > don't see field for new assigning group to the folder. > Could you help me? > /RAM/ No. I don't know the interface you're using. However, Apache has to be able to access ALL directories in the pathname else a 403 error results - and that's what you're getting. |