# Re: Revised Internet-Draft: finger URL

Larry Masinter (masinter@parc.xerox.com)
Sun, 26 Feb 1995 12:55:07 PST

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Jared_Rhine@hmc.edu: "Re: Revised Internet-Draft: finger URL"
- Previous message: Peter Koch: "Re: New Internet-Draft: finger URL"
- In reply to: Paul Hoffman: "Re: Revised Internet-Draft: finger URL"
- Next in thread: Andrew McRae: "Re: Revised Internet-Draft: finger URL"

    To: ietf-lists@proper.com

    In-Reply-To: Paul Hoffman's message of Sun, 26 Feb 1995 10:59:24 -0800 <v02110104ab767dfa6b29@[165.227.40.27]>

    Subject: Re: Revised Internet-Draft: finger URL

    From: Larry Masinter <masinter@parc.xerox.com>

    Message-Id: <95Feb26.125511pst.2760@golden.parc.xerox.com>

    Date: Sun, 26 Feb 1995 12:55:07 PST

> - How to allow
> finger:user@usershost@host1@host2

Can't this be done with:
finger://host2/user@usershost@host1

Don't confuse the common Unix command line interface with the
protocol.

> - How to allow "/W". Again, I think this is very rarely used and would be
> willing to toss it out.

Can't this be done with:

finger://host//W

or

finger://host//W%20user

As for serving other ports, if you allow it, add the same security
warnings that were there for gopher. I think the justification that
makes me think this might be useful is the possibility of using
'finger:' URLs for whois++.

- Next message: Jared_Rhine@hmc.edu: "Re: Revised Internet-Draft: finger URL"
- Previous message: Peter Koch: "Re: New Internet-Draft: finger URL"
- In reply to: Paul Hoffman: "Re: Revised Internet-Draft: finger URL"
- Next in thread: Andrew McRae: "Re: Revised Internet-Draft: finger URL"