There have been a number of responses to Wandisco's Shaking Up Subversion post (which I linked to awhile back). Never a dull moment, I guess.

This is interesting.

Subversions's CMike (C. Michael Pilato) submitted the vision statement I mentioned just a few days ago. See what you think.

I've been using Subversion since about version 0.12 (released sometime in 2002 I imagine). I've been on the dev and user mailing lists for just as long. Since that time version control systems have seen major improvements. It's hard to believe that the best open source version control system ten years ago was CVS. There are now a wealth of systems and most of them are targeted at a distributed development model. One thing that distinguishes Subversion from the others is that it continues in the tradition of a centralized repository and has eschewed the trend toward decentralization. I think it's great that there are now so many choices. I also hope to see Subversion continue to thrive, and so I was pleased to see several posts about a recent Subversion Vision Conference. The conference was really an informal gathering of a small number of Subversion developers and their attempt to plan a roadmap for the next few years of svn development. The roadmap is currently unpublished and unofficial, but I expect that it will appear, in some form, sometime soon.

This is a duplication of a blog post I made in 2005 on a different blog.

When receiving an error like 502 Bad Gateway from Apache.

A small mod_perl2 module I wrote to fix a problem when proxying a Subversion server. Specifically, if you have a Subversion server on a private/local network and a reverse proxy on a public network, and a user connects to the reverse proxy via HTTPS and the reverse proxy connects to the Subversion server via HTTP. This causes problems with the COPY and MOVE HTTP methods. This is because mod_dav sends a Destination header with the wrong scheme. Your reverse proxy will not rewrite the path scheme properly (i.e. it will not change HTTPS to HTTP). The following code rewrites the scheme properly.

Here is the mailing list thread that started it all.

The code is named ProxyDav.pm and is valid for any mod_perl2 installation with a version greater than 1.999022.

The Apache configuration is simple:

    <Location /svn>
      SetHandler               perl-script
      PerlHeaderParserHandler  ProxyDav
    </Location>