I have set up VisualSVN server, a Subversion server that internally uses Apache, to serve my subversion repositories.

I've managed to integrate WebSVN into it as well, and just now was able to get it to serve my repositories through WebSVN without having to authenticate, ie. no username or password prompt comes up. This is good.

However, with this set up there is apparently no way for me to authenticate to WebSVN at all, which means all my private repositories are now invisible as far as WebSVN goes.

I noticed there is a "Listen 81" directive in the .conf file, since I'm running the server on port 81 instead of 80, so I was wondering if I could set up a https:// connection to a different port, that did require authentication?

The reason I need access to my private repositories is that I have linked my bug tracking system to the subversion repositories, so if I click a link in the bug tracking system, it will take me to diffs for the relevant files in WebSVN, and some products are in private repositories.

Here's my Location section for WebSVN:

<Location /websvn/>
   Options FollowSymLinks

   SVNListParentPath on
   SVNParentPath "C:/Repositories/"
   SVNPathAuthz on

   AuthName "Subversion Repository"
   AuthType Basic
   AuthBasicProvider file
   AuthUserFile "C:/Repositories/htpasswd"
   AuthzSVNAccessFile "C:/Repositories/authz"

   Satisfy Any
   Require valid-user
</Location>

Is there any way I can set up a separate section for a different port, say 8100, that does not have the Satisfy Any directive there, which is what enable anonymous access.

Note that a different sub-directory on the server is acceptable as well, so /websvn_secure/, if I can make a location section for that and effectively serve the same content only without the Satisfy Any directive, that'd be good too.