DougR, much obliged for that note about "Limit" in the Apache configuration. I had a new Subversion repository all set up, httpd all set up, htpassword accounts all set up, authz all set up, the SELinux contexts and context types etc were all good to go...and I couldn't log in from anything to save my life. Nothing was even asking for credentials. The Apache error_log unfortunately was not illuminating, precisely because it was the result of adding a . The only thing that saved me was reading your response here. Once I finish setting up my new home dev environment (the usual routine after getting new kit) I'll probably learn up on why the caused such a blocker. More out of curiosity than because it's important. Thanks again.
Glad that it helped! Cheers.
Turn off SELinux if you find it on. Requires a reboot. Make sure that all path components (e.g. "/", "/opt", "/opt/svn", "/opt/svn/reponame") are properly owned, grouped and permissioned. Make sure that your "/var/log/httpd" directory is properly protected, etc. If you're not starting Apache as "root" then it won't be able to log into the normal location so you'll need to choose paths for logs, etc. that work. And you're going to need to use a port > 1024.
Weird: I set SELinux to permissive:
sudo setenforce Permissive and it started to prompt for password as expected. Aha, an SELinux issue!. Just to make sure, I set SELinux to enforcing and test if it fails again ...
sudo setenforce Enforcing but it keeps prompting for password! I rebooted, and it keeps working ... I don't understand what has happened here, but now I get my system working as expected, thanks a lot for pointing me in the right direction ... Cheers!
That's strange. I hope it keeps on working. Cheers.