[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] Re: POSSIBLY SOLVED - IMP set-up, .htaccess file --> magic_quotes_gpc ERROR
- Subject: Re: [cobalt-users] Re: POSSIBLY SOLVED - IMP set-up, .htaccess file --> magic_quotes_gpc ERROR
- From: "Steve Werby" <steve-lists@xxxxxxxxxxxx>
- Date: Wed May 30 10:22:02 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
"Tim Bolt" <timbolt@xxxxxxxxxxx> wrote:
> Thank you folks, WE HAVE A WINNER! (almost :-)
Almost? You sure? Anyway, glad you got it working. :-)
> You are correct that I did not have a <Directory /home/sites/home>
section.
> However, I did have two sections:
>
> <Directory /home/sites/>
> <Directory /home/sites/*/>
>
> Now, when I added <Directory /home/sites/home> between these and restarted
Apache, it did not help. Still errors.
I said /home/sites/home b/c I was doing work on a client's home site.
Obviously if you're IMP install is on another site, say site12 the container
would look like <Directory /home/sites/site12>. If that wasn't the problem
then it's probably b/c you appear to have put the <Directory> block I
suggested in between the two you mentioned. I am pretty sure that's not
what I suggested, if anything I suggested adding to the bottom of the file.
Honestly, I don't know how nesting of <Directory> blocks works.
>
> When I replaced:
> <Directory /home/sites/*/>
> Options -FollowSymLinks +SymLinksIfOwnerMatch
> </Directory>
>
> with:
> <Directory /home/sites/*/>
> AllowOverride All
> Options -FollowSymLinks +SymLinksIfOwnerMatch
> </Directory>
>
> it works!
Yep. And it would have worked if you did AllowOverride All for the site in
question instead of *all* sites as you did when you added to the block
above. FYI, "*" is a wildcard which matches all characters.
> Why did:
>
> <Directory /home/sites/*/>
> AllowOverride AuthConfig Indexes Limit
> Options -FollowSymLinks +SymLinksIfOwnerMatch
> </Directory>
>
> not work? I wouldhave thought this was a "AuthConfig" option?
AllowOverride controls which directives override directives declared
earlier. The AuthConfig directive type covers authorization related
directives. PHP directives are not authorization related and so they're not
covered by it. I think they are covered by FileInfo, but I'm not certain.
> 2) Is <Directory /home/sites/*/> inherently less safe that: <Directory
/home/sites/home/> ?
Not as asked. But overriding more types of directives in "*" affects *all*
sites, while doing so in "home" effects only one site - home.
> 3) Precdence, can one have both and depending which is higher, ect.?
Yes, not sure what the precedence is, but I do not think the order within
the config file is important. That is, I don't think moving one higher in
the file changes the behavior of Apache.
> 4) Good explaination of what the
> AllowOverride AuthConfig Indexes Limit
> Options -FollowSymLinks +SymLinksIfOwnerMatch
> Lines are allowing my clients to actually do!
Perhaps the Apache manual is too technical, but you can visit
http://httpd.apache.org/docs/mod/core.html#allowoverride and read more
there. If you search google.com maybe you can find an explanation that's
better.
--
Steve Werby
President, Befriend Internet Services LLC
http://www.befriend.com/