I’ve got VisualSVN Server running behind a reverse proxy in IIS 6, Windows Server 2003. This isn’t ideal, but for the main web app on the server I’ve only got one IP address and SSL certificate available.

Everything works except for when trying to commit to or browse the default ASP.NET directories (App_Browsers, App_Code, App_Data). SVN commits fail for these directories – which I believe is because IIS will never serve them by default.

The reverse proxy uses a virtual directory in IIS – is there a change I can make in the web.config for this virtual directory to get around the issue?

  • What errors do you get in a web browser and in a client? What errors do you see on the log? – bahrep Oct 31 '12 at 12:05
  • Browser: "The system cannot find the file specified." – user143344 Nov 1 '12 at 15:13
  • SVN Client: "Commit failed. Unable to connect to a repository URL. 'trunk/App_Code' path not found." Log: "Item 'trunk/App_Code' is out of date [409, #170004]" – user143344 Nov 1 '12 at 15:18
  • Did you end up finding an answer to this? I'm also having problems running VisualSVN behind a reverse proxy in IIS. – ajbeaven Oct 5 '17 at 5:55

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.