And the winner of the prise! That did it. However, there is a already mod_userdir.conf that has all of the data in it. I cut and pasted to the default-server.conf - restarted apache2 and it is fixed. Thaks for the fast resolve to this problem. Patrick Shanahan wrote:

* Donn Washburn [09-25-05 19:54]:

...

I was trying to setup SuSE 9.3 and 10 so as to have https work I tried using Yast2 which seemed to work correctly but soon there after using my public_html directory gives me this. _______________________ Access forbidden!

You don't have permission to access the requested object. It is either read-protected or not readable by the server.

If you think this is a server error, please contact the webmaster. Error 403 ____________________________

Last week on the list:

Date: Tue, 20 Sep 2005 16:16:16 -0400 X-Message-Number-For-Archive: 3128 From: Carl Hartung To: opensuse@opensuse.org Message-Id: <200509201616.17140.suselinux@cehartung.com> Subject: Re: [opensuse] RC1 Apache2 - problem [SOLVED] user public_html dirs Mailing-List: contact opensuse-help@opensuse.org; run by ezmlm

On Tuesday 20 September 2005 07:44, Carl Hartung wrote: <snipped>

And the winner of the prise

Thanks Robert,

I found the problem. The default Apache2 installation on 10.0 RC1 omitted the section, below, from /etc/apache2/default-server.conf. When I inserted it and restarted Apache2, my ~/public_html directory became available.

- Carl

-- excerpt -- # UserDir: The name of the directory that is appended onto a user's home # directory if a ~user request is received. # # To disable it, simply remove userdir from the list of modules in APACHE_MODULES # in /etc/sysconfig/apache2. # <IfModule mod_userdir.c> # Note that the name of the user directory ("public_html") cannot simply be # changed here, since it is a compile time setting. The apache package # would have to be rebuilt. You could work around by deleting # /usr/sbin/suexec, but then all scripts from the directories would be # executed with the UID of the webserver. UserDir public_html # The actual configuration of the directory is in # /etc/apache2/mod_userdir.conf. Include /etc/apache2/mod_userdir.conf # You can, however, change the ~ if you find it awkward, by mapping e.g. # http://www.example.com/users/karl-heinz/ --> /home/karl-heinz/public_html/ #AliasMatch ^/users/([a-zA-Z0-9-_.]*)/?(.*) /home/$1/public_html/$2 </IfModule> -- end excerpt --

-- 73 de Donn Washburn Hpage:" http://www.hal-pc.org/~n5xwb " Ham Callsign N5XWB Email : " n5xwb@hal-pc.org " 307 Savoy St. HAMs:" n5xwb@arrl.net " Sugar Land, TX 77478 BMW MOA #: 4146 - Ambassador LL# 1.281.242.3256 " http://counter.li.org " #279316

On Sun, Sep 25, 2005 at 08:18:12PM -0500, Patrick Shanahan wrote:

Last week on the list:

Date: Tue, 20 Sep 2005 16:16:16 -0400 X-Message-Number-For-Archive: 3128 From: Carl Hartung To: opensuse@opensuse.org Message-Id: <200509201616.17140.suselinux@cehartung.com> Subject: Re: [opensuse] RC1 Apache2 - problem [SOLVED] user public_html dirs Mailing-List: contact opensuse-help@opensuse.org; run by ezmlm

On Tuesday 20 September 2005 07:44, Carl Hartung wrote: <snipped>

Thanks Robert,

I found the problem. The default Apache2 installation on 10.0 RC1 omitted the section, below, from /etc/apache2/default-server.conf. When I inserted it and restarted Apache2, my ~/public_html directory became available.

It is impossible that the section was missing.

- Carl

-- excerpt -- # UserDir: The name of the directory that is appended onto a user's home # directory if a ~user request is received. # # To disable it, simply remove userdir from the list of modules in APACHE_MODULES # in /etc/sysconfig/apache2. # <IfModule mod_userdir.c> # Note that the name of the user directory ("public_html") cannot simply be # changed here, since it is a compile time setting. The apache package # would have to be rebuilt. You could work around by deleting # /usr/sbin/suexec, but then all scripts from the directories would be # executed with the UID of the webserver. UserDir public_html # The actual configuration of the directory is in # /etc/apache2/mod_userdir.conf. Include /etc/apache2/mod_userdir.conf # You can, however, change the ~ if you find it awkward, by mapping e.g. # http://www.example.com/users/karl-heinz/ --> /home/karl-heinz/public_html/ #AliasMatch ^/users/([a-zA-Z0-9-_.]*)/?(.*) /home/$1/public_html/$2 </IfModule> -- end excerpt --

Peter -- the pink machine that goes "ping" imitated the big cardinal

On Fri, Sep 30, 2005 at 09:22:30AM -0400, Carl Hartung wrote:

On Friday 30 September 2005 07:05, poeml@cmdline.net wrote: <snip>

...

...

I found the problem. The default Apache2 installation on 10.0 RC1 omitted the section, below, from /etc/apache2/default-server.conf. When I inserted it and restarted Apache2, my ~/public_html directory became available.

In hindsight, the above description is not very accurate. The system in question started as a Beta 1 "fresh install" that was updated via YaST2 to Betas 2, 3, 4 and finally to RC1. This means the default-server.conf file I was inspecting could have been written incorrectly or mangled at any time during that process. A better description would have included this update/upgrade path. I apologize if my hastily written words have caused you any hair-pulling... :-)

Well, I personally know that the file has not been touched since quite a while. I am the one who packages it. The timestamp of the last modification is 2004-03-18 17:41 It does include the /etc/apache2/mod_userdir.conf configuration. So if your local copy doesn't contain it, there must be something else at fault. I can not think of anything in the build/packaging process which would remove arbitrary configuration from the file. Also, there is nothing special happening during the beta phase or the update process which could induce such a change.

...

It is impossible that the section was missing.

Under the circumstances, "impossible" is still a little too strong... I didn't dream the problem up and someone else reported the same thing a few days later. I suspect we probably followed the same update path and procedure.

Unless and until another explanation surfaces, I've written this one off as an anomaly induced by the beta process, itself.

Well, I don't have an explanation either ;) Peter -- the big machine that goes "ping" imitated the tasty machine that goes "ping"