Greetings, John Pye!
>>>> Looking at your VH definition... it's messy.
>>>> Reduce the number of entities. Add next one only after you have the previous
>>>> work "as expected".
>>>> And put
>>>>
>>>> Order allow,deny
>>>> Allow from all
>>>>
>>>> Before <Location> blocks.
>>>>
>>>>
>>
>>
>>> You can't put Order or Allow statements outside either <Location> or
>>> <Directory> tags, AIUI.
>>>
>>
>> Still, it's messy.
>>
>> Try starting from
>>
>> <VirtualHost *:80>
>> ServerAdmin john.pye_at_anu.edu.au
>> ServerName ascendsvn.cheme.cmu.edu
>>
>> DocumentRoot /var/www/svn
>>
>> # Possible values include: debug, info, notice, warn, error, crit,
>> # alert, emerg.
>> LogLevel debug
>> ErrorLog /var/log/apache2/svn-error.log
>>
>> RedirectMatch ^/stats/?$ http://ascend.cheme.cmu.edu/awstats/awstats.pl?config=ascendsvn.cheme.cmu.edu
>>
>> #RedirectMatch permanent ^/$ /ascend
>>
>> CustomLog /var/log/apache2/svn.log combined
>> ServerSignature On
>>
>> <Location />
>> Order Allow,Deny
>> Allow from all
>> DAV svn
>> SVNParentPath /home/svn
>> </Location>
>>
>> </VirtualHost>
>>
>> And see how that would work.
>>
> I tried this, I get exactly the same error message. svn-error.log
> contains...
> [Tue May 19 19:35:42 2009] [error] [client 128.2.52.249] client denied
> by server configuration: /var/www/svn/ascend
> This error is completely weird because it relates to
> /var/www/svn/ascend, which doesn't exist and should NEVER be being
> requested...
Hm. Try setting
DocumentRoot /home/svn
?
> I appreciate your general approach but as far as I can see we're not
> touching the root cause of this problem yet.
Well, two things I know may produce this result:
Location/Directory block referencing the path requested and the general
Allow/Deny rule over the "/" of filesystem.
It's really hard to tell what is the case by looking only at the extracted
part of Apache configuration.
> And I am still baffled as to why I could see this problem on some
> machines, but not on others. We need to understand what things can vary
> from machine to machine to cause this problem to occur.
If you change your problematic machine IP to one which does not experience
this problem, does it get to work?
--
WBR,
Andrey Repin (anrdaemon_at_freemail.ru) 20.05.2009, <22:02>
Sorry for my terrible english...
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2333455
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-20 20:10:58 CEST