Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have SVN setup on the server, but when I try to do a checkout remotely via SSH it throws a 200 OK response, rather than processing my checkout. I think I've missed a step with the SVN and how it communicates with apache.... any thoughts?

share|improve this question
200 OK? Isn't that an HTTP response? – jldugger Mar 26 '10 at 19:48
If you've setup your svn repositories to be served by apache (via mod_dav_svn) then you should be using an http/https url for your repository, not ssh+svn most likely. Otherwise need more context for a real answer. – shollyman Mar 26 '10 at 19:53
up vote 4 down vote accepted

Do yourself a favor and bookmark the official SVN book. It's got many handy references, like this table. Let me call your attention to this table There are three common ways to connect to SVN:

  1. SVN procotol. SVN server listening on port 3690. URIs start with svn://
  2. SVN+SSH. SSH listening (port 22 by default) with a local SVN daemon launched for the duration of the transaction. URIs start with svn+ssh://
  3. HTTP. Apache listening on port 80/443 for HTTP requests, and directing them to mod_dav_svn. This is what you claim to be using. URIs start with https://

If you have only set up Apache then you need to use something like

share|improve this answer
https uses port 443, not 447. – Bert Huijben Mar 29 '10 at 9:53

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.