Apache chapter 3

[Michael Satterwhite]

Brian Fahrlander wrote:
> Michael Satterwhite wrote:
>>> This is getting *VERY* weird.
>>>
>>> Yesterday / today, I had a configuration error that prevented me from
>>> opening php files ... apache didn't know what to do with them. After
>>> some memory prodding and help, I got the first site to open.
>>>
>>> Problem: I have another site ON THE SAME SERVER. Both sites are defined
>>> in /var/www the same way, by a symlink to the directories containing the
>>> ssites. Permissions are identical, both sites have a start page of
>>> index.php.
>>>
>>> The first page opens fine - hence my assumption that the problem was fixed.
>>> The second site gives the error
>>>    You have chosen to open
>>>
>>>    which is a PHTML file
>>>
>>> Note that no page is named in the message. There is no file with a phtml
>>> extension.
>>>
>>> On the other error, I had seen things like that before, I just had an
>>> admitted case of brain freeze. With a little memory jogging from the
>>> experts here, I knew where I was going. I've *NEVER* seen anything like
>>> this one before. I've been googling for an answer, but so far haven't
>>> found anything.
>>>
>>> The amount of knowledge here is incredible; I'm sure someone has seen
>>> this. Any help from anywhere?
> 
>     There is an apache keyword for "symlinks"; maybe it's default
> behavior is to deny such links, instead of following them.  I'd help you
> look, but I'm walking out the door, and I remember the (very
> Google-able) keyword.  I'll bet this is key.

I'll start looking at it, but remember that *BOTH* sites are addressed
by symlink. One is working, the other isn't. ... not that apache is
always consistent <g>