W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > May to August 1997

Re: MIME multipart/* vs HTTP

From: Ben Laurie <ben@gonzo.ben.algroup.co.uk>
Date: Tue, 6 May 1997 16:42:26 +0100 (BST)
To: josh@netscape.com
Cc: masinter@parc.xerox.com, http-wg@cuckoo.hpl.hp.com
Message-Id: <9705061642.aa06861@gonzo.ben.algroup.co.uk>
Josh Cohen wrote:
> 3.2.2. FTP url-path
> 
>    The url-path of a FTP URL has the following syntax:
> 
>         <cwd1>/<cwd2>/.../<cwdN>/<name>;type=<typecode>
> 
>    Where <cwd1> through <cwdN> and <name> are (possibly encoded) strings
>    and <typecode> is one of the characters "a", "i", or "d".  The part
>    ";type=<typecode>" may be omitted. The <cwdx> and <name> parts may be
>    empty. The whole url-path may be omitted, including the "/"
>    delimiting it from the prefix containing user, password, host, and
>    port.
> 
> The lynx user asserts this to mean "an ftp URL may not be terminated
>  by a slash "

It clearly states that <name> may be empty, and ";type=<typecode>" may be
omitted, but the slash cannot be omitted (unless the url-path is empty),
therefore it _can_ end with a slash. QED.

Cheers,

Ben.

-- 
Ben Laurie                Phone: +44 (181) 994 6435  Email: ben@algroup.co.uk
Freelance Consultant and  Fax:   +44 (181) 994 6472
Technical Director        URL: http://www.algroup.co.uk/Apache-SSL
A.L. Digital Ltd,         Apache Group member (http://www.apache.org)
London, England.          Apache-SSL author
Received on Tuesday, 6 May 1997 08:58:13 EDT

This archive was generated by hypermail pre-2.1.9 : Wednesday, 24 September 2003 06:32:41 EDT