Hi Trevor, It's probably easiest to make the wiki instance of Apache run on port 443, and proxy any requests to a certain URL, such as /svn/ to VisualSVN Server, rather than the other way around. The only reason for saying this is that it can be difficult to get binaries of the
On Mon, Sep 14, 2009 at 4:29 AM, . . <[email protected]> wrote: > > We currently have both a VisualSVN server and a wiki server on two separate > machines. We'd like to be able to access both externally on port 443 > (https) without having to resort to getting another static IP address. > > It looks like this sort of thing is possible with either mod_proxy (setup > as a reverse proxy) or even mod_proxy_ajp (the wiki server is hosted by > Tomcat), for a default Apache installation, but I'm wondering if this is > possible with the VisualSVN Apache configuration? > > I know we could set up another Apache server as a proxy to direct requests > to either the VisualSVN server or the wiki server, but it would be less > complex (perhaps more efficient?) if I could use the VisualSVN Apache server > to do all the work. > > Any suggestions or ideas? > Thanks, > Trevor > > -- > _______________________________________________ > Surf the Web in a faster, safer and easier way: > Download Opera 9 at http://www.opera.com > > Powered by Outblaze >
