Re: Using http:// URL that contains a username

Greetings, jhanley_at_dgtlrift.com!

>>>> For different copies and purposes, may be. But still, I would stick to one
>>>> way or another, reusing SVN auth cache as much as possible without
>>>> unnecessary
>>>> bloating.
>>
>>> It's not bloating, its implementing section 3.2.1 of RFC 3986
>>
>> You messing things.
>> Bloating in my sentence was in reference to the way SVN storing auth cache.
>> For svn://host and https://host it'll be two different entries in database.

> Ahh, Yes. I see and agree - this example would clutter up the cred db,
> but I believe the original author was just using the two URLs to the
> same server for illustration purposes tto show that there is a
> difference in operation. I don't picture individual users accessing
> the same server by different protocol means.

> You bring up a point & question that is beyond the scope of this
> thread - would every protocol to the same resource generate additional
> entries to the db? ie http, https, svn, svn+ssh, file, future
> protocols? Additionally, what about hostname vs fqdn? ie would
> http://oursvnserver/ vs http://oursvnserver.ourcompany.com/ generate
> multiple entries?

Right. Ok.
My only thought is that if any change could be done in this regard, the auth
creds could be bound to repository UUID.
Not explicitly universal scheme, but i see very few operations where the UUID
couldn't known in advance.
For that matter, it would be probably worth storing all used access methods in
the cache file and if we need to authorize for export (one of possible
examples), and repository asking us for authentication before providing UUID,
we could try the URL math first, then ask user if none matched or one we tried
was rejected.
Like this example (completely hand-made for illustrative purposes only)
> K 15
> svn:UUID
> V 36
> f4de985e-6dcf-9f4d-8c76-0c4191c3a480
> K 8
> passtype
> V 8
> wincrypt
> K 8
> password
> V ***
> hereitis
> K 15
> svn:repositoryroot
> V 37 35 36 38
> https://svn.example.com:443/svn/repos
> http://svn.example.com:80/svn/repos
> svn://svn.example.com:port/svn/repos
> svn+ssh://svn.example.com:22/svn/repos
> K 8
> username
> V 9
> AnrDaemon
> END

Sidenote.
I've found that SVN storing auth cache per-realm
i.e.
svn:realmstring
V 48
<http://svn.example.com:80> Subversion repository

But it is likely that for different repositories on the same realm you could
be using different names.

--
WBR,
 Andrey Repin (anrdaemon_at_freemail.ru) 08.04.2009, <17:51>
Sorry for my terrible english...
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1596957
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].