Re: New Internet-Draft: finger URL

>would cause a finger client to send the request "someuser<CRLF>" to
>port 79 at
>--Paul Hoffman

ok, I feel better now, thanks.

>should be rejected by the client software.

how about interpreting "someuser" as "@someuser"?

However, I wouldn't mind seeing some discussion (even from people 
who haven't said anything yet) on 2 points that apply to but also 
transcend the finger url discussion--

1. ability to specify alternate port, how important is this?
   I know I've indicated this isn't too important in real life
   use of finger but I was able to come up with an instance where 
   this would be useful (imagine using the ":" as port separator)--

   If you want to know the temp outside my office.

2. adherence to the scheme://host/ method of indicating the host
   name. I can't think of a better exception to this rule than
   finger--but are there any hidden costs?


University of Tennessee, Knoxville            Dept of Computer Science
Netlib Development Group            'I was kidding,' says bomb suspect -- <URL:>

Received on Sunday, 19 February 1995 21:58:00 UTC