Re: another apache permissions problem
From: Henrik Vendelbo <hvendelbo_at_bluprints.com>
Date: 2004-12-07 18:53:32 CET
Would sulinux be involved in this security issue ? it is enabled for apache in fedora core 3
Daniel Anderson wrote:
Gary Thomas wrote:
svn: PROPFIND request failed on '/MyProject'
... or through a browser:
The Apache error log shows the following:
[Mon Dec 06 16:28:22 2004] [error] [client 192.168.254.119]
The error doesn't make any sense to me because I set global write
This is my http.conf entry (again, no permissions):
If anyone has an idea as to what the problem is, please let me know.
This works great for me - I actually have multiple repositories under
(*) IIRC the trouble I had was that ViewCVS didn't like things that
Following your suggestion, I tried to setup a repository within the /var/www/ tree. It worked fine. Unfortunately I need the repository outside the /var/www tree. The problem seems to be with Apache, but I can't figure it out for the life of me. I can't even get Apache to serve ANY html or text page outside of the /var/www/html tree. I have tried using symbolic links and by specifying an alias and directory as follows...
Alias /foo "/foo"
I can get Apache to show a directory listing, but no files show up except nested directories. When I try to access a file (e.g. test.txt) in this directory via a url, the following error is written to the error log...
(13)Permission denied: access to /foo/test.txt denied
I have tried everything in terms of permissions and ownership on the files and directories. I am by no means knowledgable of Apache configuration, but I have never had any trouble setting up directories like this. It seems like a pretty basic task. I just can't figure this out.
I am running Apache/2.0.52 (Fedora). Is there something new to this version or unique to Fedora that I am missing? This is driving me crazy.
Any help would be greatly appreciated.
I *finally* figured this out. Hopefully this will help prevent someone else from wasting countless hours trying to figure it out. The SELinux security was somehow interfering with Apache. I don't understand the specifics, but when I shut down the SELinux, everything began to work as expected.
This is an archived mail posted to the Subversion Users mailing list.