Re: MIME multipart/* vs HTTP

• Messages sorted by: [ date ][ thread ][ subject ][ author ]
• Next message: Josh Cohen: "FTP urls"
• Previous message: Josh Cohen: "Re: MIME multipart/* vs HTTP"
• In reply to: Josh Cohen: "Re: MIME multipart/* vs HTTP"
• Next in thread: Josh Cohen: "FTP urls"
• Reply: Josh Cohen: "FTP urls"

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

• Next message: Josh Cohen: "FTP urls"
• Previous message: Josh Cohen: "Re: MIME multipart/* vs HTTP"
• In reply to: Josh Cohen: "Re: MIME multipart/* vs HTTP"
• Next in thread: Josh Cohen: "FTP urls"
• Reply: Josh Cohen: "FTP urls"