> "TR" == Tim Rühsen writes: TR> Wget is not supposed to support file://. Yes, I am just saying if it did it would make testing easier. If something doesn't work, if it also doesn't even work with just file:///, then one would know it wasn't a network problem, etc.
rsync too. In fact I can't think of one other remote copying / network downloader that doesn't also work just the same if given both a local origin and destination.
Just like one can use $ scp fileA fileB with no network needed.
On 17.05.19 07:37, 積丹尼 Dan Jacobson wrote: > I can do > $ curl file:///dev/null > > If I could do the same with wget, then I could e.g., see the effects of > adding --quiet vs. not adding it, without needing a HTTP server. > Wget is not supposed to support file://. You can easily use 'cp' or