I followed the steps to set up lxr, and I think I have everything set up
correctly except for Apache. When I try to open http://localhost/lxr/, I
get the following error:
"Forbidden You don't have permission to access /lxr/ on this server."
Most "403 Forbidden" problems come from incorrect access rights to the LXR root directory.
To protect the server owner against malicious accesses, web browsers often require that EVERY directory on the path from / to the terminal directory (LXR root directory in this case) can be accessed (flag x) and read (flag r), i.e. have at least permission r-xr-xr-x or 555.
Note, for example, that thttpd REQUIRES "world-readability (man states that setting access rights for the thttpd user is not sufficient, thttpd explicitly tests world-read bit).
Can I close this topic as "self-resolved"? (It will still be accessible in the archives.)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I followed the steps to set up lxr, and I think I have everything set up
correctly except for Apache. When I try to open http://localhost/lxr/, I
get the following error:
"Forbidden You don't have permission to access /lxr/ on this server."
I am able to access the default page http://localhost/.
Has anyone seen this before?
Thanks,
Patrick
I found the problem. It was a permissions issue with one of the parent directories.
Most "403 Forbidden" problems come from incorrect access rights to the LXR root directory.
To protect the server owner against malicious accesses, web browsers often require that EVERY directory on the path from / to the terminal directory (LXR root directory in this case) can be accessed (flag x) and read (flag r), i.e. have at least permission r-xr-xr-x or 555.
Note, for example, that thttpd REQUIRES "world-readability (man states that setting access rights for the thttpd user is not sufficient, thttpd explicitly tests world-read bit).
Can I close this topic as "self-resolved"? (It will still be accessible in the archives.)