[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

fishy 404

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2002-06-05 17:40:48 CEST

So now the latest version of mod_dav_svn uses /!svn/ as its opaque url
identifier, instead of /$svn/. Once we upgrade svn.collab.net (and
other people upgrade their existing repositories), there are three
things that can be done with existing working copies:

 1. Throw out the working copy, do a fresh checkout. All secretly
    cached urls are correct.

 2. 'svn switch' the working copy to the URL it already represents.
    This should rewrite all the vsn-rsc-urls, but not the activity

 3. Do nothing. Commits will take longer (the cached urls will be
    invalid and need to regenerate themselves via extra network round
    trips), but over time the correct urls will creep in.

It's situation #3 that I'm a little worried about. When the client
attempts to CHECKOUT a /$svn/ url into some dav activity, it gets a
404 error back and then attempts to rediscover the url. But I'm
worried about the way in which the 404 is happening.

AFAICT from my ethereal traces, the server is sending a 404 because
it can't find "/$svn/..." within the repository filesystem! This
can't be right. gstein, shouldn't /$svn/ be invalidated some other
way? I mean, what if /$svn were a real top-level directory in the

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 5 17:43:07 2002

This is an archived mail posted to the Subversion Dev mailing list.