On Oct 5, 2006, at 01:08, Reza Mostafid wrote:
> On 10/1/06, Ryan Schmidt wrote:
>> On Sep 30, 2006, at 07:56, Reza Mostafid wrote:
>> > * Firing up apache works fine. No errors.
>> > * apachectl -M shows the svn modules are loaded as shared.
>> > * I can test the server with the built in Firefox browser
>> > and I get the 'It works!' message.
>> That message is of course from Apache, not the Subversion module.
>> > * When I try to view the repository in the browser via
>> > http://localhost/repos I get an error:
>> > '403 Forbidden
>> > You don't have permission to access /repos on this server'
>> > * The necessary directives are there in the httpd.conf file
>> > right after the LoadModule directives:
>> > <Location /repos>
>> > DAV svn
>> > SVNParentPath <my own repository path>
>> > </Location>
>> <my own repository path> is the path to the repository, or the path
>> to a directory containing several repositories? If the former, then
>> you need SVNPath, not SVNParentPath.
> I do realize the 'It works' comes from the ?.hml file in the htdocs/
> dir under the 'Document Root' of Apache.
> Next thing is the SVNParentPath directive. Here again I do realize
> that 'SVNPath' is for redirecting a URL to a single repository and
> 'SVNParentPath' is for multiple repositories.
> I have already done a YUM update which placed the *.so files neatly
> where they belong to and even added a 'subversion.conf' file to
> Fedora's preinstalled httpd conf/ directory.
> I further configured that setup to work over the network and could get
> Tortoise and IntelliJIDEA to work flawlessly with the Linux Apache
> based server. I even successfully experimineted with the authorization
> and access control features.
> What puzzlesz me is that when building Apache & subversion myself, the
> build proceeds in an apparantly flawless manner, and the httpd works
> fine when accessing ordinary *.html files but no access to the
> repository is permitted as already described in the previous post.
> In other words I have checked all the pobvious things ( permissions,
> paths, spelling etc. ) and only then did I fire-up the e-mail to send
> this post.
> Can you think of anything that might cause the 403 ERROR when
> accessing the repos?
Let's keep the discussion on the mailing list so others can benefit
Have you looked in the Apache error log? This should tell you what
file or directory it thinks you don't have access to. Maybe this will
point you to a misconfiguration.
Check also that Apache has permissions to read the repository and its
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Thu Oct 5 21:44:51 2006