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

Re: svn switch and URL:s with colons

From: Julian Foad <julianfoad_at_btopenworld.com>
Date: 2006-06-30 02:15:25 CEST

Daniel Rall wrote:
> On Thu, 29 Jun 2006, Fredrik Arnerup wrote:
>>In 1.3.1, svn switch does not seem to consider "svn://server:/foobar"
>>and "svn://server/foobar" to be the same repo.
[...]
>>Can anyone confirm this? Should I file a bug report?
>
> Many common tools (Firefox, CVS, etc.) handle this format. Section
> 3.2.2 and 3.2.3 of RFC 2616 are slightly at odds with each other on
> this topic, suggesting first that the colon should only be included
> with a port number, then going on to say that a colon which lacks a
> port number should be treated identically as one without for
> comparison purposes.

I don't see any inconsistency. Both sections talk about when the "port ... is
empty or not given", and in the syntax notation the "port" in '[ ":" port ]' is
defined as zero or more digits if you follow the reference to RFC2396. I
assume "empty" means the colon is present but the port isn't, and "not given"
means neither the colon nor the port, but we don't need my assumption.

Also, the general principle of "be tolerant in what you receive and strict in
what you send" tells us to accept an empty port number but never to generate one.

> http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.2
> (Another reference might be more appropriate for ra_svn.)
>
> Perhaps we should support the colon-without-number format, at least
> for comparsions?

Yes, definitely. So, Fredrik, please file a bug report (or send a patch to fix
it!)

- Julian

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jun 30 02:15:28 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.