Re: [Duplicity-talk] Re: Re: Re: First restore failing

[Kenneth Loafman]

Peter Schuller wrote:
>>> What I still don't get for the life of me, is why it is behaving as
>>> if 'https' was an unknown scheme...
>> Well, what determines if something is a known scheme or not?
> 
> urlparse has an internal list of various attributes associated with certain 
> schemes. One of these attributes determines whether the component after 
> scheme:// is a hostname. This is determined by affirmatively stating that a 
> particular scheme is of this form; the default otherwise is to treat it the 
> other way around.
> 
> Without actually looking into the standard, I am personally slightly peeved 
> by 
> this behavior and would prefer to have unknown schemes default to assuming a 
> hostname, since this is much more common.
> 
> However, the bundled version of urlparse_2_5 *does* have https listed:
> 
> uses_netloc = ['ftp', 'http', 'gopher', 'nntp', 'telnet',
>                'imap', 'wais', 'file', 'mms', 'https', 'shttp',
>                'snews', 'prospero', 'rtsp', 'rtspu', 'rsync', '',
>                'svn', 'svn+ssh', 'sftp']

The problem is that uses_netloc is overridden in line 48 of backends.py
to match only the URLs that duplicity is interested in.

To fix this behavior, import urlparse_2_5 as something other than
urlparser for use in parsing webDAV internal URLs.

...Ken

signature.asc
Description: OpenPGP digital signature