An SVN error (200 OK) when checking out from my online repository

I'm trying to set up my first repository on my host and am getting this error when I use TortoiseSVN to checkout the project:

Error: OPTIONS of 'http://mywebsite.com/svn/myproject': 200 OK (http://mywebsite.com)

Here is what I did:

1. Ssh into my host and head to /home/myaccnt and 'svnadmin create svn'

2. Create my project repository: 'svn mkdir svn/myproject'

3. Add files to the repository: cd /home/myaccnt/.../myproject (which has /tags, /branch, /trunk); 'svn import file:///home/myaccnt/svn/myproject' (the big old list of files being added is seen at this point.)
   At this point I think that I've setup my repository and imported my project into the repository. So, I'm ready to checkout using TortoiseSVN on my Windows box. So:

4. In the folder I'd like to checkout to, I right click and SVN Checkout, and then make sure my URL is: http://mywebsite.com/svn/myproject

Result?

Error: OPTIONS of 'http://mywebsite.com/svn/myproject': 200 OK (http://mywebsite.com)

Anyone have any thoughts for me? I'm likely missing something fundamental with the structure of my repository or htaccess... or something.

I had to dig into this issue too and found the following pages which lead me to the solution: - http://comments.gmane.org/gmane.comp.version-control.subversion.devel/117844 (See especially the link to "Julian's patch".)

There is stated that the "OPTIONS of <url>: 200 (<url>) OK" error is quite misleading and often just means that the repository URL is wrong.

I had a similar problem with a simple "svn list" command.

To extend Vitor Mateus' answer regarding slashes: While setting up my own repository using Apache on an in-house server, my original Location tag in the Apache 2 configuration file looked like:

<Location "/svn/repo_address/">
    ...
</Location>

Where there was a trailing "/" after "repo_address". There should not be a slash there:

<Location "/svn/repo_address">
    ...
</Location>

Something subtle, but it makes a huge difference. Now a call to

svn list http://my.server.com/svn/repo_address

works fine. Sometimes it helps to read the manual carefully ;-)

Apparently, this is more a restriction issue by my host, and I am working with them to resolve it.

Thanks, 1800.

BTW, the answer here was that my host, A2 Web Hosting, requires that SVN be handled via SSH using a public_key and configuring, in my case, TortoiseSVN to do the job. It was sort of funky for someone who has just a little experience setting up keys, but it was pretty satisfying once it was done!

You can find information about SVN on the A2 host in their support wiki.