You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by "Martin v. Löwis" <ma...@v.loewis.de> on 2003/06/10 21:11:21 UTC
ra_dav and RedirectPermanent
I'm trying to move an existing repository to a new location, without
invalidating existing sandboxes.
To do so, I put an Apache RedirectPermanent directive into the old
location. When a client connects, I see that a proper 301 status is
returned on "PROPFIND /playground HTTP/1.0".
However, instead of following the redirect, the client then issues
"PROPFIND / HTTP/1.0", which fails (as DAV is not available on /, only
on /playground).
Is this a known problem? Should I file a bug report? Is there anything
I can do to ease migration? Giving a proper error message would be
more helpful than the "Access Denied" code that the clients currently
get.
Regards,
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: ra_dav and RedirectPermanent
Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
On Tue, Jun 10, 2003 at 11:11:21PM +0200, Martin v. Lwis wrote:
> Is this a known problem? Should I file a bug report? Is there anything
> I can do to ease migration? Giving a proper error message would be
> more helpful than the "Access Denied" code that the clients currently
> get.
Try 'svn switch --relocate' which was just merged. -- justin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: ra_dav and RedirectPermanent
Posted by "Martin v. Löwis" <ma...@v.loewis.de>.
mark benedetto king <mb...@lowlatency.com> writes:
> It's tricky to add functionality to old clients. :-)
>
> Off the top of my head, maybe you could have PROPFIND / generate
> a "400 Update Your SVN Client And Run switch --relocate to NEWURL"
> status
> code.
Unfortunately, that does not work. If libsvn_ra_dav gets any error, it
tries to PROPFIND in a next-higher directory, as it tries to find the
root of the repository. It eventually comes out at /, where it gets
405; this is the error it reports.
So I can only hope that users will point their webbrowsers to the
URL...
Regards,
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: ra_dav and RedirectPermanent
Posted by mark benedetto king <mb...@lowlatency.com>.
On Tuesday, June 10, 2003, at 05:41 PM, Martin v. Löwis wrote:
> mark benedetto king <mb...@lowlatency.com> writes:
>
>> Until Issue 660 is fixed, you can use any post-revision-6170 svn
>> client to "switch --relocate" the WCs. It's not transparent, but
>> it's easier than teaching your users perl.
>
> Is there a way to have clients (preferably old clients) print out some
> error message to that effect? Ideally, I'd like to write a CGI script
> that generates the error response.
>
It's tricky to add functionality to old clients. :-)
Off the top of my head, maybe you could have PROPFIND / generate
a "400 Update Your SVN Client And Run switch --relocate to NEWURL"
status
code.
--ben
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: ra_dav and RedirectPermanent
Posted by "Martin v. Löwis" <ma...@v.loewis.de>.
mark benedetto king <mb...@lowlatency.com> writes:
> Until Issue 660 is fixed, you can use any post-revision-6170 svn
> client to "switch --relocate" the WCs. It's not transparent, but
> it's easier than teaching your users perl.
Is there a way to have clients (preferably old clients) print out some
error message to that effect? Ideally, I'd like to write a CGI script
that generates the error response.
Regards,
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: ra_dav and RedirectPermanent
Posted by mark benedetto king <mb...@lowlatency.com>.
On Tuesday, June 10, 2003, at 05:11 PM, Martin v. Löwis wrote:
>
> Is this a known problem? Should I file a bug report? Is there anything
> I can do to ease migration? Giving a proper error message would be
> more helpful than the "Access Denied" code that the clients currently
> get.
>
Until Issue 660 is fixed, you can use any post-revision-6170 svn client
to "switch --relocate" the WCs. It's not transparent, but it's easier
than
teaching your users perl.
--ben
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: ra_dav and RedirectPermanent
Posted by mark benedetto king <mb...@lowlatency.com>.
On Tuesday, June 10, 2003, at 05:11 PM, Martin v. Löwis wrote:
> I'm trying to move an existing repository to a new location, without
> invalidating existing sandboxes.
>
> To do so, I put an Apache RedirectPermanent directive into the old
> location. When a client connects, I see that a proper 301 status is
> returned on "PROPFIND /playground HTTP/1.0".
>
> However, instead of following the redirect, the client then issues
> "PROPFIND / HTTP/1.0", which fails (as DAV is not available on /, only
> on /playground).
>
> Is this a known problem? Should I file a bug report? Is there anything
> I can do to ease migration? Giving a proper error message would be
> more helpful than the "Access Denied" code that the clients currently
> get.
>
>
http://subversion.tigris.org/issues/show_bug.cgi?id=660
--ben
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org