I ran into the same consideration but I believe there is a better way. Using ISA you can publish the external port as 443 and then have ISA bridge the traffic to the internal server on whatever port you want. So start by creating a normal web listener on port 443 and then create a new publishing policy for your VisualSVN Server. In the publishing policy configure the Bridging tab to redirect requests to port 8443 (or whatever you need) and you should be good to go.
This is also a good way to have the VisualSVN be addressable externally using a different SSL certificate than what is installed on the VisualSVN server. You can keep using the selfsigned certificate on the VisualSVN server but just export the public key and import it into the ISA Trusted Root store. Then you can configure your ISA server with a public private/public key certificate (ex. Verisign) and then use that certificate to publish the site. client --- https://www.myvisualsvn.com (port 443) ---> ISA --- https://myserver (port 8443) --> myserver Works really clean. Lot's more configuration options available if anyone needs more info about ISA Publishing... Chris
