[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-wget] Shouldn't wget strip leading spaces from a URL?
From: |
Ander Juaristi |
Subject: |
Re: [Bug-wget] Shouldn't wget strip leading spaces from a URL? |
Date: |
Tue, 13 Jun 2017 19:34:27 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0 |
On 13/06/17 02:09, L A Walsh wrote:
>
>
> Dale R. Worley wrote:
>> L A Walsh <address@hidden> writes:
>>> W/cut+paste into target line, where URL is double-quoted. More often
>>> than not, I find it safer to double-quote a URL than not, because, for
>>> example, shells react badly to embedded spaces, ampersands and
>>> question marks.
>>
>> But of course, no URL contains an embedded space.
> ---
> Why not?
>
> John Mueller of Google posted a note about spaces in the URL on Google+.
> You know, the URLs that look like www.domain.com/file name goes here.html.
>
> Should you fill those holes?
>
> John Mueller of Google said "the answer is not "no"" when it comes to
> the
> question "Should you encode spaces in URLs as "%20", "+" or
> as a space (" ")?"
>
But those are correctly handled by wget.
I guess the whole point of this thread is to handle leading (and probably also
trailing) spaces. And the easiest way to 'handle' them is to remove them. So we
need a patch that trims the URL, as Tim said (I think), shouldn't be hard.
Other than that, there's nothing more to worry about, is it? Spaces within a
path/query are already correctly dealt with, and spaces in any other place
(htt ps://... !!!) are probably incorrect and should be reported as such.
>
> But what would someone at google know?
>
>
>
>