On 31.01.2011 14:49, Bolstridge, Andrew wrote:
>> -----Original Message-----
>> From: Daniel Shahaf [mailto:d.s_at_daniel.shahaf.name]
>> Sent: 28 January 2011 19:03
>> To: Bolstridge, Andrew
>> Cc: dev_at_subversion.apache.org
>> Subject: Re: [Feature] New feature about handling 'HTTP Error 302
>> Bolstridge, Andrew wrote on Fri, Jan 28, 2011 at 12:46:40 +0000:
>>>> On 01/27/2011 08:27 PM, Wu Di wrote:
>>>>> I found path in subversion sometimes too long, it's hard to be
>>>>> sent by Email and something else.
>>>>> And 'Tiny URL' is more popular now. it redirect a short URL to a long
>>>>> I thing is a good idea if TortoiseSvn could handle 'HTTP Error 302
>>>>> Moved temporarily' to support Tiny URL and something like that?
>>> Just as long as it doesn’t use a 3rd party redirection service that may (or
>> may not) continue to be available in the future - eg. tinyurl.com or bit.ly or
>> Don't those services use 301 redirects?
> It doesn’t matter how they redirect as the association between the short-code and the real url has to be stored somewhere, so if the url-shortening service goes down (or is switched off for whatever reason - maybe someone decided they have a patent on url shortening, or they just stop making money, or get bought out by Oracle or whatever)(it's happened, look at evilurl.com) then the short urls stop working.
> In fact, download a tinyurl link (eg their example, http://tinyurl.com/6 and open it in an editor. Be prepared to be amazed :)
But really, does anyone who's using shortened URLs really expect them to
be there forever? I guess not.
In other words, 'svn co' should not store the URL that it found on the
command line, but first follow any permanent redirects (301) and use the
last one as the canonical repository URL. If that still redirects with
302, follow it, but don't store the location.
Same goes for update, and externals URLs, etc.
Received on 2011-01-31 17:50:33 CET