Open Tech Notes

PROPFIND request failed on ‘/path/to/repo’ and PROPFIND of ‘/path/to/repo’: 301 Moved Permanently

There are a lot of reasons cause this problem in SVN client. But the problem is in server side.
Here is a comprehensive explain about this issue :
http://www.checkupdown.com/status/E301.html

For my case, whenever I create a folder under /opt/lampp/htdocs and if the name is same with ‘path/to/repo’ , it will cause this error message:

Error: PROPFIND request failed on ‘/reponame’ 
Error: PROPFIND of ‘/reponame’: 301 Moved Permanently (http://www.vancouvereasy.com) 

12:Option expected

This is the only error message I encountered on setting up SVN sever on Windows 2003.

Here is the config file:

### This file controls the configuration of the svnserve daemon, if you
### use it to allow access to this repository. (If you only allow
### access through http: and/or file: URLs, then this file is
### irrelevant.)

### Visit http://subversion.tigris.org/ for more information.

[general]
### These options control access to the repository for unauthenticated
### and authenticated users. Valid values are "write", "read",
### and "none". The sample settings below are the defaults.
 anon-access=read
 auth-access=write
### The password-db option controls the location of the password
### database file. Unless you specify a path starting with a /,
### the file’s location is relative to the conf directory.
### Uncomment the line below to use the default password file.
 password-db=passwd
### The authz-db option controls the location of the authorization
### rules for path-based access control. Unless you specify a path
### starting with a /, the file’s location is relative to the conf
### directory. If you don’t specify an authz-db, no path-based access
### control is done.
### Uncomment the line below to use the default authorization file.
# authz-db = authz
### This option specifies the authentication realm of the repository.
### If two repositories have the same authentication realm, they should
### have the same password database, and vice versa. The default realm
### is repository’s uuid.
# realm = My First Repository

———————-

Solution is very simple, just remove the SPACE in front of lines which are not be commented.

Taking advantage of “post-commit”

If the SVN system could be a good backup system, then the "post-commit" script would be a hidden gem. After I have done the "weird" requirement from the programmers, It trigger me think about a nice backup system.

Writing a remote executable SSH command in post-commit script of the SVN system. After every commit, the system will automatically put all files to two different hosts. The two hosts can be located in two different cities, even two different countries.

post commit

Programmers require that they want see the effect right after they commit their codes and fortunately the SVN system provides such a great tool to do so.

Under /repository name/hooks/, there is a file called post-commit.tmpl, it is a template file that you can revise it to fit your needs.

Upon the requirements from programmers, I have implemented two post commit scripts:

1) the website and the SVN server  reside in the same machine
2) the website and the SVN server  reside in two different machine

Avoid using the “same” name in SVN repository

In Linux, the file name is case-sensitive whereas in Windows it is not.

When I commit two files like "file.php" and "File.php" under Linux, it is ok. However, when I update it under Windows, it cause problem.