On Sep 9, 2008, at 8:02 PM, Jonathan Coles wrote:
> Ryan Schmidt wrote:
>
>> On Sep 9, 2008, at 7:27 PM, Jonathan Coles wrote:
>>
>>> Even more strange, I can now also access my repository using the
>>> URL "http://<server>/svn/myproduct". That makes no sense at all!
>>> There is nothing to link that location with the repository!
>>>
>>> Any idea what is going on here?
>>
>> You're saying you can access your repository using http://<server>/
>> svn/myproduct even though there is no <Location /svn/> directive?
>>
>> I assume someone else already set up a <Location /svn/> directive
>> for you and you just don't know it. Maybe another administrator,
>> or maybe your OS distribution provided it. Search *all* your
>> Apache configuration files, not just the main httpd.conf but also
>> all extra conf files it might include.
>
> I didn't realize that Apache reads all files in conf.d, not just
> *.conf. My old locations definition file, renamed with a .bak
> extension, contains SVNPath definitions. That must have caused a
> conflict when creating a parent path with that name and of course,
> it explains why the /svn/ paths to existing repositories continued
> to work. I added "~" to the end of my .bak file, making it a backup
> which Apache seems to know enough to ignore.
It depends on how your httpd.conf is set up. If it includes a line like:
Include conf.d/*
Then every file in the conf.d directory will be included regardless
of extension. If instead it says:
Include conf.d/*.conf
Then only .conf files should get included.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-09-10 05:31:25 CEST