Re: New SCM problems in Xcode
Re: New SCM problems in Xcode
- Subject: Re: New SCM problems in Xcode
- From: Bill Bumgarner <email@hidden>
- Date: Sun, 28 Oct 2007 19:15:37 -0700
On Oct 28, 2007, at 5:53 PM, Chris Hanson wrote:
On Oct 28, 2007, at 5:27 PM, Bill Monk wrote:
On 28 Oct 2007 00:59:03 -0700, Chris Espinosa <email@hidden> wrote:
Wow, it really wants "email@hidden" as the user name, as in svn
+ssh://
email@hidden@mysvnserver.net/svn/repository/balh/blah/blah? That's
certainly funky.
Ah, but according to the OP, it's actually "http://
email@hidden@svn.bar.com/svn/repository". Which makes slightly more
sense; they probably have Apache set up to connect to the same auth
system as their email environment or something like that.
Interestingly, http://email@hidden@svn.bar.com/ is not a valid URL.
That is, any "@", "/" or ":" found in the username or password fields
MUST be encoded. Alas, standards are often less about following the
well documented and obvious rules and more about dealing with whatever
odd interpretation of reality someone happens to have made popular. ;)
The RFC (RFC 1738, specifically) states:
...
3.1. Common Internet Scheme Syntax
While the syntax for the rest of the URL may vary depending on the
particular scheme selected, URL schemes that involve the direct use
of an IP-based protocol to a specified host on the Internet use a
common syntax for the scheme-specific data:
//<user>:<password>@<host>:<port>/<url-path>
Some or all of the parts "<user>:<password>@", ":<password>",
":<port>", and "/<url-path>" may be excluded. The scheme specific
data start with a double slash "//" to indicate that it complies
with
the common Internet scheme syntax. The different components obey the
following rules:
user
An optional user name. Some schemes (e.g., ftp) allow the
specification of a user name.
password
An optional password. If present, it follows the user
name separated from it by a colon.
The user name (and password), if present, are followed by a
commercial at-sign "@". Within the user and password field, any ":",
"@", or "/" must be encoded.
Note that an empty user name or password is different than no user
name or password; there is no way to specify a password without
specifying a user name. E.g., <URL:ftp://@host.com/> has an empty
user name and no password, <URL:ftp://host.com/> has no user name,
while <URL:ftp://foo:@host.com/> has a user name of "foo" and an
empty password.
...
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden