Re: [Bug-wget] Shouldn't wget strip leading spaces from a URL?

[L A Walsh]

Ander Juaristi wrote:
> Your shell strips all the additional spaces between command-line arguments, so
> it's effectively like a browser ;)
>
> How are you running wget?
---
        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.

	The URL I was copying was itself a link (but not to the 
same place, but some link-counter), but to not activate the link,
I had to start a bit before or after the link -- thus picked up a space.

        Basically comes down to wget deliberately submitting a
URL that it knows is incorrect, OR as good-user-agent, trimming leading
spaces or not.  Mindless obedience is almost never a good thing,
whereas common sense is usually valued (both of these are in
reference to how a program behaves).

It should take extra effort for wget to NOT strip 
leading+trailing spaces, since stripping those leading and 
trailing spaces is what users would be used to in a browser
AND because it would be the common-sense & user-friendly
thing to do.