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

[Peter Schuller]

> We may be revisiting the design choice made in Bug #21475 and Patch
> #6300.  In particular, the reported problem can be a side-effect of this
> chunk:

[snip]

> -            userinfo = netloc.rsplit("@", 1)[0]
> +            userinfo = netloc.split("@", 1)[0]

Interesting. I remembered there was some history with urlparse but wasn't sure 
what. 

I was under the impression that it now worked for Thorsten, when not using 
SSL, indicating that the @ handling did not cause problems in his case. But 
as you note, and I missed, his latest example does have a @ in the username.

The other problem was that my initial patch was entirely broken, because I did 
not look into the return value of urlparse() properly.

What I still don't get for the life of me, is why it is behaving as if 'https' 
was an unknown scheme...

-- 
/ Peter Schuller

PGP userID: 0xE9758B7D or 'Peter Schuller <address@hidden>'
Key retrieval: Send an E-Mail to address@hidden
E-Mail: address@hidden Web: http://www.scode.org

signature.asc
Description: This is a digitally signed message part.