Re: [Ovirt-devel] [PATCH server] Changed how taskomatic handles a Cobbler image record.

[Laine Stump <laine laine org>]

On 12/22/2008 11:14 AM, Darryl L. Pierce wrote:
> On Mon, Dec 22, 2008 at 09:32:51AM -0500, Laine Stump wrote:
>   
> > > Is the host-then-colon pattern valid if not port follows?
> > >   
> > >       
> > That caught my eye too. It's a bit degenerate, but the BNF for NFS URLs  
> > (in RFC 2224) allows it:
> >
> >   hostport      = host [ ":" port ]
> >   port          = *digit
> >
> > So port is 0 or more occurrences of digit.
> >     
>
> Yeah, I noticed that as well and think it's an oversight on their
> part. But, be that as it may, they do describe handling by saying if
> no port is specified to then use the one for the given protocol. So,
> if no protocol is specified, then treat it as an error.
>   

Definitely an oversight - the original URL RFC (1738) uses 1*digits for 
port rather than *digits.

My guess is that the particular style of URL given in the cobbler docs 
started when someone took
the location format used by mount, rsync, etc (host:/path) and tacked 
nfs:// on the beginning.