The following reply was made to PR general/2733; it has been noted by GNATS.
From: Marc Slemko <[EMAIL PROTECTED]> To: Ben Bullock <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED] Subject: Re: general/2733: .htaccess file ignored Date: Wed, 29 Jul 1998 09:57:06 -0700 (PDT) On 29 Jul 1998, Ben Bullock wrote: > The following reply was made to PR general/2733; it has been noted by GNATS. > > From: Ben Bullock <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Re: general/2733: .htaccess file ignored > Date: Wed, 29 Jul 1998 11:19:46 -0400 > > [EMAIL PROTECTED] wrote: > > > > Synopsis: .htaccess file ignored > > > > State-Changed-From-To: feedback-closed > > State-Changed-By: marc > > State-Changed-When: Tue Jul 28 22:15:08 PDT 1998 > > State-Changed-Why: > > You have: > > > > <Directory /~bullock> > > > > in your config file. That is not a valid setting; you > > can't use "/~user" anywere (eg. not even in a shell), and > > ~ isn't valid in Apache config files anyway. Setup a > > proper section enabling the AllowOverride and it will > > work. > > OK, I've got it working now, but the "/~user" business wasn't the Yes, that is the problem. > real problem; closely related to it though. It was the fact that > at the very beginning of access.conf I originally had this > section: > > # First, we configure the "default" to be a very restrictive set > of > # permissions. > > <Directory /> > Options FollowSymLinks > AllowOverride None > </Directory> > > > > Writing it this way did the trick: > > # First, we configure the "default" to be a very restrictive set > of > # permissions. > > <Directory /www/share/apache/htdocs> > Options FollowSymLinks > AllowOverride None > </Directory> > > > BTW, when this is done, then later on in access.conf I can use > <Directory /~bullock> OR <Directory > /www/share/apache/htdocs/bullock> OR <Directory > /www/share/apache/htdocs/~bullock>. Erm... no. You are completely missing what you are doing; the directory you are trying to change the config for is /home/bullock/public_html, not any of the above. None of the above have any impact whatsoever, and changing the other one only means that you don't have any section applying to /home, which means that by default things are allowed. > > I would respectfully suggest that the stock access.conf file > provided with the apache distribution include a preface to this > important section that would read something like this: > > # First, we configure the "default" to be a very restrictive set > of > # permissions for the document root directory. Be sure to > specify > # the correct path to YOUR document root in the first line. > # For example: <Directory /usr/local/apache/htdocs> This should > # agree with what you set DocumentRoot to in srm.conf. No, that is not what it is supposed to be and it explicitly uses / to avoid allowing, by default, users to do bad things outside the documentroot.
