[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: snv URL does not use FQDN

From: Jaap Vermeulen <jaap_at_skyscape.com>
Date: 2004-11-12 16:58:01 CET

I've been looking at the responses to this message on the mailing list.

What I'm asking for is much simpler than what is discussed. And it follows
standard (and predictable) practices.

When you provide a name, it will be resolved to a FQDN. In other words, if
you type "blarvitz", the DNS libraries will automatically add the domain
based on a list of primary/subdomains that your machine is in. (This is
true both for UNIX or Windows.) For example, try a ping to your SVN server
without the primary domain and examine its output; it will have the FQDN.
This is done by routines like "gethostbyname()" or "getaddrinfo()".

The only thing I'm asking for is that the host part of the svn: URL is
resolved to a FQDN. This can be done either by resolving both the given and
stored host name and then comparing them (probably best), or by storing the
resolved host name and only resolving the given host name and then comparing
it.

This avoid issues where if you provide a partial host name, it will not
match with the stored (partial) host name, even though they will both be
resolved to the same FQDN. If an IP address is used, you simply try a
reverse lookup. If either the lookup or the reverse lookup fails, you keep
the original string (of course). In the end the host names either match or
don't match, and the result is no worse than what we have now. :-)

Thanks,

        -Jaap-

> -----Original Message-----
> From: Jaap Vermeulen [mailto:jaap@skyscape.com]
> Sent: Monday, November 08, 2004 6:38 PM
> To: users@subversion.tigris.org
> Subject: snv URL does not use FQDN
>
>
>
> Hi,
>
> I just want to know whether it is reasonable to file an issue
> against the svn: protocol urls with respect to fully-qualified
> domain names. If a machine "A" is in domain "B.C", and you refer
> in the URL to the machine as "svn://A/...", you should also be
> able to refer to it as "svn://A.B.C/..." without SVN getting
> confused and ornery and refusing to update or do other operations
> on a working copy because the URLs don't match.
>
> Thanks,
>
> -Jaap-
>
> PS: I quickly checked the issue DB and didn't see related issues.
> Let me know if there is already an outstanding issue for this.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Nov 12 21:01:24 2004

This is an archived mail posted to the Subversion Users mailing list.