[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Apache 1.3
OK, you write that apache follows links in it's serverroot dir. But how do
i tell it to follow links in the user dirs ?
I looked at the page, but it only lists many keywords. I looked at
<Directory> and some more, but it's all the same style.
Anyway, in my httpd.conf the user dirs are set as follows:
<Directory /*/public_html>
AllowOverride All
Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec
<Limit GET POST OPTIONS PROPFIND>
Order allow,deny
Allow from all
</Limit>
<Limit PUT DELETE PATCH PROPPATCH MKCOL COPY MOVE LOCK UNLOCK>
Order deny,allow
Deny from all
</Limit>
</Directory>
I think that this is a reasonable config put there by my distri.
The point is, what do I have to put in the .htaccess in ~/public_html to
allow all the things I need. The problem is very simple. I made a dir
(public_html/film) and when i tell the browser ..../~schapiro/film I get
an access denied page. dir rights are 755 and should be fine. It seems to
me that apache doesn't allow entrance into subdirs in the userdirs at all
and I wonder how to tell it in my .htaccess that for this specific dir it
should allow it.
Thanks for your help & patience
Schlomo
On Mon, 3 May 1999, Oded Arbel wrote:
>
>
> On Mon, 3 May 1999, Schlomo Schapiro wrote:
>
> > Hi,
> >
> > I am trying to configure Apache 1.3 httpd. My aim is to use the
> > public_html user dirs and allow mostly all in those dirs. My config is
> > pretty much standart (SuSE 6.0) and I simply don't know how to make apache
> > follow symlinks and allow access to subdirs of public_html. I would also
> > like to restrict certain subdirs/symlinks to users in a password database
> > (e.g. where the browser asks for a password).
> everything should be pretty obvious .. about symlinks, as far as I can
> remember, apache will follow symlink that resolve to a legitimate URL
> under ServerRoot.
> about password, I think there's a built in module in apache that does this
> (maybe you need to add or activate it), but I usually use CGIs to do that.
> much easier and more configurable.
>
> > configured apache (e.g. i couldn't find a doc explaining how the http.conf
> > files look, how the .htaccess files look and I couldn't find a big howto
> just open the file, it's well commented out. I didn't read anything but
> the man page and the files in /etc/httpd/conf and i didn't had any
> problems with setting up, including public_html (and sub dirs).
> about .htaccess, read this - http://www.apache.org/docs-1.2/mod/core.html
> it should be a starting point.
>
> Oded
>