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

Re: 301 Redirects

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2006-02-09 18:50:19 CET

Tatham Oddie (Fuel Advance) wrote:

> Rather than showing an error like this:
> Error: PROPFIND request failed on '/FuelAdvance.Components'
> Error: PROPFIND of '/FuelAdvance.Components': 301 Moved Permanently
> (http://svn.services.fueladvance.com)
> … would it not be more logical to follow the redirect and automatically
> offer the user to relocate?
> Many browsers will automatically update bookmarks without asking users
> if there is a 301 redirect in place. Many RSS readers do this as well to
> make the process of moving a feed easier. I just moved our repository
> from *http* to *https* and if TortoiseSVN could have followed the 301
> then I wouldn’t have even had to notify my users.

First, this kind of request should be made on the Subversion mailing
list. It's the Subversion library that handles all networking issues,
not TSVN.

Second: this has come up before. This isn't implemented because the URL
of the repository is stored in your working copy. To follow the
redirect, Subversion would have to modify your whole working copy.
And btw: browsers will follow that redirect only once. If you have a
bookmark for such an URL, the browser won't adjust your bookmark either.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu Feb 9 18:57:50 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.