Re: [Lynx-dev] Is this a bug ?

[Thorsten Glaser]

David Woolley dixit:

>   should be ignored in URLs, as it should have been resolved before the
> parameter is treated as a URL, and true whitespace is ignored, as it would be
> ambiguous in printed URLs.  %20 should be treated as significant in URLs.

%20 must.

Note that wget 'http://…/foo bar.mp3' works (and requests foo%20bar.mp3 but
stores it as 'foo bar.mp3' on the disc), while BSD ftp(1) fails on the same
URI but does not strip the space either.

Now, while embedded spaces may be invalid and ambiguous, they do have some
benefit in that case…

//mirabilos
-- 
“It is inappropriate to require that a time represented as
 seconds since the Epoch precisely represent the number of
 seconds between the referenced time and the Epoch.”
        -- IEEE Std 1003.1b-1993 (POSIX) Section B.2.2.2