[10945] in www-talk@info.cern.ch

home help back first fref pref prev next nref lref last post

Re: ftp URLs and browser behaviour

daemon@ATHENA.MIT.EDU (Steven Heaney)
Tue Aug 19 13:30:45 1997

Date: 19 Aug 97 18:26:53 +0100
From: "Steven Heaney" <heaney@cambridge.scr.slb.com>
To: "Larry Masinter" <masinter@parc.xerox.com>, S.N.Brodie@ecs.soton.ac.uk
Cc: www-talk@w3.org
Resent-From: www-talk@w3.org

On Tue, Aug 19, 1997 5:26 pm, Larry Masinter
<mailto:masinter@parc.xerox.com> wrote:
>There's no way to say "prompt the user for a name & password".
>Some browsers do it if anonymous fails, others don't.
>If you want to add that as a requirement, then you'd have
>to say so.
>
>If you want to add a new syntax, or say
>   ftp://:@<host>/<urlpath>
>
>means "prompt the user if sending the empty string fails",
>then we'd have to recycle *those* at proposed, too.
>
>In any case, nobody uses the ";type=d" thing we added 
>to the Proposed Standard, I don't think, so I'd like to
>just drop it as we move forward.
>
>Larry
>

As you say, it looks like there is no way currently to access an FTP 
resource which is password protected without placing a valid username 
in the URL.  This is somewhat limiting.

Thinking about it, the behaviour I'm looking for would simply be a 
mirror of that when requesting an HTTP resource which requires 
authentication.

Regards,

Steve. 





home help back first fref pref prev next nref lref last post