W3C home > Mailing lists > Public > uri@w3.org > February 2004

Re: localhost

From: Martin Duerst <duerst@w3.org>
Date: Mon, 16 Feb 2004 12:22:40 -0500
Message-Id: <4.2.0.58.J.20040216121757.057b9498@localhost>
To: "Adam M. Costello BOGUS address, see signature" <BOGUS@BOGUS.nicemice.net>(by way of Martin Duerst <duerst@w3.org>), uri@w3.org

Hello Adam, Roy,

- I think the 'localhost' convention should only apply to reg-names that
   are domain/host names. I think it's inappropriate to impose this
   convention on other registry names; they may have completely different
   needs (i.e. not actually refering to machines,...) or syntax
   (e.g. numerical,...).

- On the other hand, 'localhost' should work for all dns-based schemes.
   "Individual URI schemes can require support for this custom." may
   suggest otherwise.

- For the exact details, I don't really think it matters that much
   whether 'localhost' is resolved by lookup or otherwise.

Regards,   Martin.



At 09:14 04/02/16 -0500, Adam M. Costello BOGUS address, see signature wrote:




>Roy T. Fielding <fielding@gbiv.com> wrote:
>
> > Fixed.
>
>I'm not sure I know how to interpret the new text:
>
> > If "localhost" is not determined by a host name lookup, then it should
> > be interpreted to mean the machine on which the URI is being resolved.
>
>Does this mean:
>
>1) Either perform a host name lookup on "localhost" or interpret it to
>mean the machine you're running on, your choice.
>
>or
>
>2) Perform a host name lookup on "localhost".  If you don't get an
>answer, then interpret it to mean the machine you're running on.
>
>or
>
>3) Perform a host name lookup on "localhost" or don't, your choice.
>If you don't get an answer (possibly because you didn't perform the
>lookup), then interpret it to mean the machine you're running on.
>
>or
>
>4) If the reg_name is supposed to be a host name, then treat "localhost"
>like any other host name (that is, look it up).  Otherwise interpret
>"localhost" to mean the machine you're running on.
>
>In any case, are you sure you want to leave room for more than one
>outcome?  RFC-1738 left no room for doubt; localhost was required to
>refer to the machine you're running on (but only for file: URIs).  That
>implied that you could legitimately use the host name resolver for
>localhost only if you could depend on your resolver to map localhost to
>the machine you're running on.
>
>Maybe the best we can do is say something like:
>
>     "localhost" customarily refers to the machine on which it is
>     interpreted, but this has not yet been formally standardized.
>     All reg-name registries are encouraged to support this custom.
>     Individual URI schemes can require support for this custom.
>
>AMC
>http://www.nicemice.net/amc/
Received on Monday, 16 February 2004 12:38:21 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:25:07 UTC