Greets;
How is SuSE setting up apache to serve public_html files?
1. I have uncommented the following
-----------------------------------------------------
# The next three lines are commented out here. These directives and the access
# control section have been put into /etc/httpd/suse_public_html.conf.
# If the variable HTTPD_SEC_PUBLIC_HTML in /etc/sysconfig/apache
# is set to "yes" (default), SuSEconfig will include that file via
# /etc/httpd/suse_include.conf.
# Also note that for the /home/*/public_html directories to be browsable the
# executable flag must be set on the /home/* directories.
#....editted /ch
<IfModule mod_userdir.c>
UserDir public_html
</IfModule>
#
# Control access to UserDir directories. The following is an example
# for a site where these directories are restricted to read-only.
#....editted /ch
On Wed, 9 Oct 2002 13:47:56 -0400
Chris Herrnberger
How is SuSE setting up apache to serve public_html files?
set the /home/testuser/public_html/index.html path to chmod -R 744 and added the user <testuser> to the group <nogroup>
You don't need to add the testuser to "nogroup" This is the way it works: 1. The apache server will start suexec for the home directories, if it finds it. It's in /usr/sbin/suexec. Now suexec will let apache run as <testuser><users> in testuser's public_html directory. This is different from the way apache normally runs as <nobody><nogroup>. Now suexec puts alot of restrictions , and it checks all cgi files, and will refuse to run them if the permissions are off. You need to read the apache docs on suexec. It allows you to run your public_html as mode 700, but it is more dangerous, because it lets people come into your public_html as the user, instead of nobody. In the main server httdocs and cgi-bin, apache will run as <nobody><nogroup>; SuSE uses a user called wwwrun instead of nobody, but it's about the same. So you may want to rename suexec to disable it, unless you want to read up on it. Your testuser should be in group users. There is a suexec log in the /var/log/httpd logs, it will give you some clues.
http://testsite/~testuser give me no access permission error???
Change your testuser back into group users, and make your cgi scripts 755, and your html 644. Then either turn off suexec or check the suexec log.
So what am I doing wrong. Something probably very obviouse to another pair of eyes.
-- use Perl; #powerful programmable prestidigitation
* Chris Herrnberger;
Greets;
How is SuSE setting up apache to serve public_html files?
by editting /etc/sysconfig/apache and then running SuSEconfig --module apache # # do you want to allow access to UserDirs (like /home/*/public_html)? # (yes|no) # if yes, this is defined in /etc/httpd/suse_public_html.conf # HTTPD_SEC_PUBLIC_HTML=yes -- Togan Muftuoglu Unofficial SuSE FAQ Maintainer http://dinamizm.ath.cx
On Wednesday 09 October 2002 14:05, Togan Muftuoglu wrote: OK lets go through this one more time if I may. 1. test account permissions set to -R 754 /home/testuser/public_html/index.html 2. /etc/httpd/httpd/conf file set to all access to user dir 3. /etc/sysconfig/apache set to server user files "HTTPD-xxxxx"=yes 4. /sbin/SuSEconfig --module apache .....done 5. http://testaccoount/!testuser 403 forbidden error (file permission is 754) Im frazzled...the rpms used are the latest updates via you apache-1.3.23-137 and only using the base apache install not with extra modules. Ideas?? /ch
On Wednesday 09 October 2002 14:50, Chris Herrnberger wrote:
On Wednesday 09 October 2002 14:05, Togan Muftuoglu wrote:
OK lets go through this one more time if I may.
Perhaps this is the issue....I have apache also set up to serve IP based virtual site from the public_html directories of selected users and server doc root is /home/httpd/html Now while it is customary to server virtual sites from in this case /home/httpd/html/V1 /V2 /V3 in this particular setup it is inconventient. so IP based virtual sites are served from /home/VS_user/public_html Could this be the issue...is there a conflict somewhere.. I know I just fishing at this point as I am out of ideas. /ch
On Wednesday 09 October 2002 5:47 pm, Chris Herrnberger wrote:
How is SuSE setting up apache to serve public_html files?
This used to be an issue, but in the last few SuSE versions, so far as I remember, you don't need to do anything - just put a HTML file in the public_html directory, and it shows up. the only thing that needs to be changed in the Apache conf file is the IndexDir variable, to allow (eg) index.php as well as index.html.
http://testsite/~testuser give me no access permission error???
Try it with a slash at the end, and with a page named index.html in the public_html dir. HTH Kevin
participants (4)
-
Chris Herrnberger -
Kevin Donnelly -
Togan Muftuoglu -
zentara