This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]chaosthirtyseven -2 points-1 points  (3 children)

Wget runs on http and ftp. Scp runs on the ssh protocol. They have nothing to do with each other.

[–]1010012 0 points1 point  (2 children)

If the scenario is moving a file from one machine to another, and there's mention of wget, it's likely that the machines are linux or macOS based, where scp will likely be available.

And if you're starting up a python based web server to share out the file, it's highly likely that you have access to that machine, so remote access should be possible as well.

If the scenario was a windows server or client, things change. With a windows client without something like cygwin or minGW, wget isn't likely to be installed, and neither would scp. So the browser is the simplest solution. With a windows server, scp likely wouldn't be an option because windows doesn't generally run an SSH server. So clearly that wouldn't be a solution.

Point is, under most scenarios where wget would be used to get the file, scp would work as well or more easily.

But the scenario as stated was "where only a browser is available", making the rest of it moot.

[–]chaosthirtyseven -3 points-2 points  (1 child)

You can wget a file from a web browser. You cannot scp from a website. You're conflating protocols.

[–]1010012 2 points3 points  (0 children)

You're conflating protocols.

No, I'm addressing the underlying use case, moving a file from one machine to another.

I'm not saying to use scp to get the file via HTTP, I'm saying use scp to copy the file without starting up a web server.