[5304] in www-talk@info.cern.ch
Finger URL, second cut
daemon@ATHENA.MIT.EDU (Reed Wade)
Tue Aug 23 23:01:05 1994
Date: Wed, 24 Aug 1994 04:58:53 +0200
Errors-To: listmaster@www0.cern.ch
Errors-To: listmaster@www0.cern.ch
Reply-To: wade@cs.utk.edu
From: Reed Wade <wade@cs.utk.edu>
To: Multiple recipients of list <www-talk@www0.cern.ch>
After looking over the finger rfc again and assimilating
comments I've made some changes to my original finger URL
proposal.
Reed Wade
---------
wade@cs.utk.edu -- http://www.netlib.org/utk/people/ReedWade.html
Finger URL
finger://hostname/[W/][username][hostlist]
hostlist ::= @hostname | @hostname{hostlist}
finger://cs.utk.edu/@garlic
finger://cs.utk.edu/W/wade@honk@garlic
finger://cs.utk.edu/W/ <-- these are different,
finger://cs.utk.edu/W <-- here W is the username
finger://cs.utk.edu/wade
Encoded CR's and LF's are not permitted in any part of the URL.
If the "W/" element is present then the finger request is preceded
by the /W (or /W<sp> as required) per rfc1128.
Returned Data Interpretation:
Existing finger servers return user information in unpredictable
ways. There are cases where it is not possible to get information
on only a single user. Interpreting returned data as plain text
is the only reasonable thing to do. Instead of attempting to wedge
more utility into finger, whois++ or http should be used.
