How do I provide a username and password to wget?
I've tried to connect to a server via wget:
wget http://<user>:<pass>@serveradress
But wget responds: invalid port
I know that the server accepts incoming traffic at port 80.
How can I fix this issue?
wget
edited Jan 7 '14 at 15:56
Braiam
51.5k20136220
asked Mar 5 '11 at 2:54
pschmidtpschmidt
1,10231213
add a comment |
I've tried to connect to a server via wget:
wget http://<user>:<pass>@serveradress
But wget responds: invalid port
I know that the server accepts incoming traffic at port 80.
How can I fix this issue?
wget
edited Jan 7 '14 at 15:56
Braiam
51.5k20136220
asked Mar 5 '11 at 2:54
pschmidtpschmidt
1,10231213
I don't think you can reliably use the user:pass@name syntax there;wgethas separate command line options for those instead, so is probably naively parsing the string after the:as a port number.
– geekosaur
Mar 5 '11 at 3:02
add a comment |
I've tried to connect to a server via wget:
wget http://<user>:<pass>@serveradress
But wget responds: invalid port
I know that the server accepts incoming traffic at port 80.
How can I fix this issue?
wget
edited Jan 7 '14 at 15:56
Braiam
51.5k20136220
asked Mar 5 '11 at 2:54
pschmidtpschmidt
1,10231213
I've tried to connect to a server via wget:
wget http://<user>:<pass>@serveradress
But wget responds: invalid port
I know that the server accepts incoming traffic at port 80.
How can I fix this issue?
wget
wget
edited Jan 7 '14 at 15:56
Braiam
51.5k20136220
asked Mar 5 '11 at 2:54
pschmidtpschmidt
1,10231213
edited Jan 7 '14 at 15:56
Braiam
51.5k20136220
asked Mar 5 '11 at 2:54
pschmidtpschmidt
1,10231213
edited Jan 7 '14 at 15:56
Braiam
51.5k20136220
edited Jan 7 '14 at 15:56
Braiam
51.5k20136220
edited Jan 7 '14 at 15:56
Braiam
51.5k20136220
51.5k20136220
asked Mar 5 '11 at 2:54
pschmidtpschmidt
1,10231213
asked Mar 5 '11 at 2:54
pschmidtpschmidt
1,10231213
asked Mar 5 '11 at 2:54
pschmidtpschmidt
1,10231213
1,10231213
I don't think you can reliably use the user:pass@name syntax there;wgethas separate command line options for those instead, so is probably naively parsing the string after the:as a port number.
– geekosaur
Mar 5 '11 at 3:02
add a comment |
I don't think you can reliably use the user:pass@name syntax there;wgethas separate command line options for those instead, so is probably naively parsing the string after the:as a port number.
– geekosaur
Mar 5 '11 at 3:02
I don't think you can reliably use the user:pass@name syntax there;
wget has separate command line options for those instead, so is probably naively parsing the string after the : as a port number.– geekosaur
Mar 5 '11 at 3:02
I don't think you can reliably use the user:pass@name syntax there;
wget has separate command line options for those instead, so is probably naively parsing the string after the : as a port number.– geekosaur
Mar 5 '11 at 3:02
add a comment |
4 Answers
4
active
oldest
votes
Wget interprets <pass>@serveraddress as port. To specify a username and password, use the --user and --password switches:
wget --user user --password pass http://example.com/
From man wget:
--user=user
--password=password
Specify the username user and password password for both FTP and HTTP file retrieval. These parameters can be overridden using the
--ftp-userand--ftp-passwordoptions for FTP connections and the--http-userand--http-passwordoptions for HTTP connections.
edited Jun 2 '16 at 7:29
MadMike
3,79172244
answered Mar 5 '11 at 8:51
LekensteynLekensteyn
120k48263355
33
I prefer the--ask-passwordoption described by Nabil Kadimi's answer. It has you enter the password invisibly on another line and avoids storing it in your shell history.
– Kevin
Apr 8 '14 at 1:23
6
@Kevin You can avoid storing it in the shell history by starting the line with at least one space (as shown by Nabil). If the password/resource is sensitive, then you should worry more about the unencrypted HTTP/FTP/whatever connection than storing it on your disk.
– Lekensteyn
Apr 8 '14 at 8:58
I agree to the unencrypted password issue being more important in some cases than the shell history, but the answer is also useful for secure protocols. Also, sometimes you DO have to worry more about spies that have access to your computer than online spies (that are not interested by the content you're accessing or for which you don't care). The --ask-password answer below is clearly better for interactive usage, while the --password answer here is easier for automation. The comment by Ixgr about .wgetrc and chmod is also interesting in some cases.
– youen
Jul 17 '17 at 12:21
add a comment |
You have 3 options and here there are in no specific order other than guts feeling:
1/ Password is visible to anyone (using the command history)
wget --user=remote_user --password=SECRET ftp://ftp.example.com/file.ext
The password will also be visible in ps, top, htop and similar.
2/ Password is visible to anyone looking behind your shoulders
wget --user=remote_user --password=SECRET ftp://ftp.example.com/file.ext
Notice the white space before the command, it prevents saving it to your history
The password will also be visible in ps, top, htop and similar.
3/ Password is not visible to anyone including you
wget --user=remote_user --ask-password ftp://ftp.example.com/file.ext
Password for user `remote_user': [SECRET (not visible)]
edited Dec 5 '18 at 15:16
Karl Richter
2,39083568
answered Jan 4 '14 at 11:17
Nabil KadimiNabil Kadimi
1,0811816
5
While it is not visible in history, it is visible to all who conduct a ps, top, htop or similar command while the process is running.
– user412812
May 22 '15 at 20:04
4
@AbdennourTOUMI Why would you disable certificate checks, especially if you are sending a password with the request? That is definitely not advisable in general. As far as "hiding" the password on logs or /proc is concerned, the wget manpage gives an additional option: "To prevent the passwords from being seen, store them in .wgetrc or .netrc, and make sure to protect those files from other users with "chmod"."
– lxgr
Jun 10 '16 at 9:32
2
If--ask-passwordis not available or you don't want to type the password every time,wget -i link.txtcan help, wherelink.txtcontainsftp://remote_user:SECRET@ftp.example.com/file.ext
– tehnicaorg
Apr 27 '18 at 13:57
add a comment |
The command could have used --http-user and --http-password instead of --user and --password. In case of ftp request the options are --ftp-user and --ftp-password.
edited Jun 15 '17 at 13:51
0xF2
2,35722045
answered Jun 15 '17 at 9:05
MradulMradul
1
2
This is not entirely correct:man wgetindicates that --user and --password are valid options, which can be overridden by --http-user or --ftp-password
– Charles Green
Jun 15 '17 at 13:04
add a comment |
This procedure is working ok in Linux server with no GUI if you need to download from web sites (like oracle.com) where you need to login and also accept Oracle rules of usage.
Part - you need machine with GUI or just smartphone only to get final link which you will use to download**
Login to Oracle or whatever site you need login to start downloading something, accept usage rules and start download in Chrome or any other browser and than copy download link from download tab, it should contain authorization parameter. Link should look something like this:
Pause download in Chrome.
Paste that download link to place from where you can wget-it or just type it in if it's not too long.
and justwgetthat whole link in your Linux machine with:
wget http://download.oracle.com/otn/linux/oracle12c/122010/linuxx64_12201_database.zip?AuthParam=1539333101_448acded002c607377c51b62730a816f
Works like charm :). I'm downloading Oracle database from:
https://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html
to Ubuntu like this.
It's probably not going to work for every case but works fine for my case :)
answered Oct 12 '18 at 8:36
HarveyHarvey
992
3
One (the crucial, in fact) purpose ofwgetis to download web content from the commandline without any GUI involved.
– PerlDuck
Oct 12 '18 at 8:48
@PerlDuck It looks like you didn't read my answer at all. You do not need GUI in linux machine for download using this procedure. This procedure only involves GUI for logging and for finding correct link to downloading . Thank you for unreasonable -1.
– Harvey
Dec 11 '18 at 6:19
I didn't downvote your post, sorry.
– PerlDuck
Dec 11 '18 at 9:14
@PerlDuck I'm sorry then. You don't have to downvote, others will do that after they look at your comment/reputation and without reading more than twitter amount of text from my post...
– Harvey
Dec 11 '18 at 11:44
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f29079%2fhow-do-i-provide-a-username-and-password-to-wget%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
Wget interprets <pass>@serveraddress as port. To specify a username and password, use the --user and --password switches:
wget --user user --password pass http://example.com/
From man wget:
--user=user
--password=password
Specify the username user and password password for both FTP and HTTP file retrieval. These parameters can be overridden using the
--ftp-userand--ftp-passwordoptions for FTP connections and the--http-userand--http-passwordoptions for HTTP connections.
edited Jun 2 '16 at 7:29
MadMike
3,79172244
answered Mar 5 '11 at 8:51
LekensteynLekensteyn
120k48263355
33
I prefer the--ask-passwordoption described by Nabil Kadimi's answer. It has you enter the password invisibly on another line and avoids storing it in your shell history.
– Kevin
Apr 8 '14 at 1:23
6
@Kevin You can avoid storing it in the shell history by starting the line with at least one space (as shown by Nabil). If the password/resource is sensitive, then you should worry more about the unencrypted HTTP/FTP/whatever connection than storing it on your disk.
– Lekensteyn
Apr 8 '14 at 8:58
I agree to the unencrypted password issue being more important in some cases than the shell history, but the answer is also useful for secure protocols. Also, sometimes you DO have to worry more about spies that have access to your computer than online spies (that are not interested by the content you're accessing or for which you don't care). The --ask-password answer below is clearly better for interactive usage, while the --password answer here is easier for automation. The comment by Ixgr about .wgetrc and chmod is also interesting in some cases.
– youen
Jul 17 '17 at 12:21
add a comment |
Wget interprets <pass>@serveraddress as port. To specify a username and password, use the --user and --password switches:
wget --user user --password pass http://example.com/
From man wget:
--user=user
--password=password
Specify the username user and password password for both FTP and HTTP file retrieval. These parameters can be overridden using the
--ftp-userand--ftp-passwordoptions for FTP connections and the--http-userand--http-passwordoptions for HTTP connections.
edited Jun 2 '16 at 7:29
MadMike
3,79172244
answered Mar 5 '11 at 8:51
LekensteynLekensteyn
120k48263355
33
I prefer the--ask-passwordoption described by Nabil Kadimi's answer. It has you enter the password invisibly on another line and avoids storing it in your shell history.
– Kevin
Apr 8 '14 at 1:23
6
@Kevin You can avoid storing it in the shell history by starting the line with at least one space (as shown by Nabil). If the password/resource is sensitive, then you should worry more about the unencrypted HTTP/FTP/whatever connection than storing it on your disk.
– Lekensteyn
Apr 8 '14 at 8:58
I agree to the unencrypted password issue being more important in some cases than the shell history, but the answer is also useful for secure protocols. Also, sometimes you DO have to worry more about spies that have access to your computer than online spies (that are not interested by the content you're accessing or for which you don't care). The --ask-password answer below is clearly better for interactive usage, while the --password answer here is easier for automation. The comment by Ixgr about .wgetrc and chmod is also interesting in some cases.
– youen
Jul 17 '17 at 12:21
add a comment |
Wget interprets <pass>@serveraddress as port. To specify a username and password, use the --user and --password switches:
wget --user user --password pass http://example.com/
From man wget:
--user=user
--password=password
Specify the username user and password password for both FTP and HTTP file retrieval. These parameters can be overridden using the
--ftp-userand--ftp-passwordoptions for FTP connections and the--http-userand--http-passwordoptions for HTTP connections.
edited Jun 2 '16 at 7:29
MadMike
3,79172244
answered Mar 5 '11 at 8:51
LekensteynLekensteyn
120k48263355
Wget interprets <pass>@serveraddress as port. To specify a username and password, use the --user and --password switches:
wget --user user --password pass http://example.com/
From man wget:
--user=user
--password=password
Specify the username user and password password for both FTP and HTTP file retrieval. These parameters can be overridden using the
--ftp-userand--ftp-passwordoptions for FTP connections and the--http-userand--http-passwordoptions for HTTP connections.
edited Jun 2 '16 at 7:29
MadMike
3,79172244
answered Mar 5 '11 at 8:51
LekensteynLekensteyn
120k48263355
edited Jun 2 '16 at 7:29
MadMike
3,79172244
edited Jun 2 '16 at 7:29
MadMike
3,79172244
edited Jun 2 '16 at 7:29
MadMike
3,79172244
3,79172244
answered Mar 5 '11 at 8:51
LekensteynLekensteyn
120k48263355
answered Mar 5 '11 at 8:51
LekensteynLekensteyn
120k48263355
answered Mar 5 '11 at 8:51
LekensteynLekensteyn
120k48263355
120k48263355
33
I prefer the--ask-passwordoption described by Nabil Kadimi's answer. It has you enter the password invisibly on another line and avoids storing it in your shell history.
– Kevin
Apr 8 '14 at 1:23
6
@Kevin You can avoid storing it in the shell history by starting the line with at least one space (as shown by Nabil). If the password/resource is sensitive, then you should worry more about the unencrypted HTTP/FTP/whatever connection than storing it on your disk.
– Lekensteyn
Apr 8 '14 at 8:58
I agree to the unencrypted password issue being more important in some cases than the shell history, but the answer is also useful for secure protocols. Also, sometimes you DO have to worry more about spies that have access to your computer than online spies (that are not interested by the content you're accessing or for which you don't care). The --ask-password answer below is clearly better for interactive usage, while the --password answer here is easier for automation. The comment by Ixgr about .wgetrc and chmod is also interesting in some cases.
– youen
Jul 17 '17 at 12:21
add a comment |
33
I prefer the--ask-passwordoption described by Nabil Kadimi's answer. It has you enter the password invisibly on another line and avoids storing it in your shell history.
– Kevin
Apr 8 '14 at 1:23
6
@Kevin You can avoid storing it in the shell history by starting the line with at least one space (as shown by Nabil). If the password/resource is sensitive, then you should worry more about the unencrypted HTTP/FTP/whatever connection than storing it on your disk.
– Lekensteyn
Apr 8 '14 at 8:58
I agree to the unencrypted password issue being more important in some cases than the shell history, but the answer is also useful for secure protocols. Also, sometimes you DO have to worry more about spies that have access to your computer than online spies (that are not interested by the content you're accessing or for which you don't care). The --ask-password answer below is clearly better for interactive usage, while the --password answer here is easier for automation. The comment by Ixgr about .wgetrc and chmod is also interesting in some cases.
– youen
Jul 17 '17 at 12:21
33
33
I prefer the
--ask-password option described by Nabil Kadimi's answer. It has you enter the password invisibly on another line and avoids storing it in your shell history.– Kevin
Apr 8 '14 at 1:23
I prefer the
--ask-password option described by Nabil Kadimi's answer. It has you enter the password invisibly on another line and avoids storing it in your shell history.– Kevin
Apr 8 '14 at 1:23
6
6
@Kevin You can avoid storing it in the shell history by starting the line with at least one space (as shown by Nabil). If the password/resource is sensitive, then you should worry more about the unencrypted HTTP/FTP/whatever connection than storing it on your disk.
– Lekensteyn
Apr 8 '14 at 8:58
@Kevin You can avoid storing it in the shell history by starting the line with at least one space (as shown by Nabil). If the password/resource is sensitive, then you should worry more about the unencrypted HTTP/FTP/whatever connection than storing it on your disk.
– Lekensteyn
Apr 8 '14 at 8:58
I agree to the unencrypted password issue being more important in some cases than the shell history, but the answer is also useful for secure protocols. Also, sometimes you DO have to worry more about spies that have access to your computer than online spies (that are not interested by the content you're accessing or for which you don't care). The --ask-password answer below is clearly better for interactive usage, while the --password answer here is easier for automation. The comment by Ixgr about .wgetrc and chmod is also interesting in some cases.
– youen
Jul 17 '17 at 12:21
I agree to the unencrypted password issue being more important in some cases than the shell history, but the answer is also useful for secure protocols. Also, sometimes you DO have to worry more about spies that have access to your computer than online spies (that are not interested by the content you're accessing or for which you don't care). The --ask-password answer below is clearly better for interactive usage, while the --password answer here is easier for automation. The comment by Ixgr about .wgetrc and chmod is also interesting in some cases.
– youen
Jul 17 '17 at 12:21
add a comment |
You have 3 options and here there are in no specific order other than guts feeling:
1/ Password is visible to anyone (using the command history)
wget --user=remote_user --password=SECRET ftp://ftp.example.com/file.ext
The password will also be visible in ps, top, htop and similar.
2/ Password is visible to anyone looking behind your shoulders
wget --user=remote_user --password=SECRET ftp://ftp.example.com/file.ext
Notice the white space before the command, it prevents saving it to your history
The password will also be visible in ps, top, htop and similar.
3/ Password is not visible to anyone including you
wget --user=remote_user --ask-password ftp://ftp.example.com/file.ext
Password for user `remote_user': [SECRET (not visible)]
edited Dec 5 '18 at 15:16
Karl Richter
2,39083568
answered Jan 4 '14 at 11:17
Nabil KadimiNabil Kadimi
1,0811816
5
While it is not visible in history, it is visible to all who conduct a ps, top, htop or similar command while the process is running.
– user412812
May 22 '15 at 20:04
4
@AbdennourTOUMI Why would you disable certificate checks, especially if you are sending a password with the request? That is definitely not advisable in general. As far as "hiding" the password on logs or /proc is concerned, the wget manpage gives an additional option: "To prevent the passwords from being seen, store them in .wgetrc or .netrc, and make sure to protect those files from other users with "chmod"."
– lxgr
Jun 10 '16 at 9:32
2
If--ask-passwordis not available or you don't want to type the password every time,wget -i link.txtcan help, wherelink.txtcontainsftp://remote_user:SECRET@ftp.example.com/file.ext
– tehnicaorg
Apr 27 '18 at 13:57
add a comment |
You have 3 options and here there are in no specific order other than guts feeling:
1/ Password is visible to anyone (using the command history)
wget --user=remote_user --password=SECRET ftp://ftp.example.com/file.ext
The password will also be visible in ps, top, htop and similar.
2/ Password is visible to anyone looking behind your shoulders
wget --user=remote_user --password=SECRET ftp://ftp.example.com/file.ext
Notice the white space before the command, it prevents saving it to your history
The password will also be visible in ps, top, htop and similar.
3/ Password is not visible to anyone including you
wget --user=remote_user --ask-password ftp://ftp.example.com/file.ext
Password for user `remote_user': [SECRET (not visible)]
edited Dec 5 '18 at 15:16
Karl Richter
2,39083568
answered Jan 4 '14 at 11:17
Nabil KadimiNabil Kadimi
1,0811816
5
While it is not visible in history, it is visible to all who conduct a ps, top, htop or similar command while the process is running.
– user412812
May 22 '15 at 20:04
4
@AbdennourTOUMI Why would you disable certificate checks, especially if you are sending a password with the request? That is definitely not advisable in general. As far as "hiding" the password on logs or /proc is concerned, the wget manpage gives an additional option: "To prevent the passwords from being seen, store them in .wgetrc or .netrc, and make sure to protect those files from other users with "chmod"."
– lxgr
Jun 10 '16 at 9:32
2
If--ask-passwordis not available or you don't want to type the password every time,wget -i link.txtcan help, wherelink.txtcontainsftp://remote_user:SECRET@ftp.example.com/file.ext
– tehnicaorg
Apr 27 '18 at 13:57
add a comment |
You have 3 options and here there are in no specific order other than guts feeling:
1/ Password is visible to anyone (using the command history)
wget --user=remote_user --password=SECRET ftp://ftp.example.com/file.ext
The password will also be visible in ps, top, htop and similar.
2/ Password is visible to anyone looking behind your shoulders
wget --user=remote_user --password=SECRET ftp://ftp.example.com/file.ext
Notice the white space before the command, it prevents saving it to your history
The password will also be visible in ps, top, htop and similar.
3/ Password is not visible to anyone including you
wget --user=remote_user --ask-password ftp://ftp.example.com/file.ext
Password for user `remote_user': [SECRET (not visible)]
edited Dec 5 '18 at 15:16
Karl Richter
2,39083568
answered Jan 4 '14 at 11:17
Nabil KadimiNabil Kadimi
1,0811816
You have 3 options and here there are in no specific order other than guts feeling:
1/ Password is visible to anyone (using the command history)
wget --user=remote_user --password=SECRET ftp://ftp.example.com/file.ext
The password will also be visible in ps, top, htop and similar.
2/ Password is visible to anyone looking behind your shoulders
wget --user=remote_user --password=SECRET ftp://ftp.example.com/file.ext
Notice the white space before the command, it prevents saving it to your history
The password will also be visible in ps, top, htop and similar.
3/ Password is not visible to anyone including you
wget --user=remote_user --ask-password ftp://ftp.example.com/file.ext
Password for user `remote_user': [SECRET (not visible)]
edited Dec 5 '18 at 15:16
Karl Richter
2,39083568
answered Jan 4 '14 at 11:17
Nabil KadimiNabil Kadimi
1,0811816
edited Dec 5 '18 at 15:16
Karl Richter
2,39083568
edited Dec 5 '18 at 15:16
Karl Richter
2,39083568
edited Dec 5 '18 at 15:16
Karl Richter
2,39083568
2,39083568
answered Jan 4 '14 at 11:17
Nabil KadimiNabil Kadimi
1,0811816
answered Jan 4 '14 at 11:17
Nabil KadimiNabil Kadimi
1,0811816
answered Jan 4 '14 at 11:17
Nabil KadimiNabil Kadimi
1,0811816
1,0811816
5
While it is not visible in history, it is visible to all who conduct a ps, top, htop or similar command while the process is running.
– user412812
May 22 '15 at 20:04
4
@AbdennourTOUMI Why would you disable certificate checks, especially if you are sending a password with the request? That is definitely not advisable in general. As far as "hiding" the password on logs or /proc is concerned, the wget manpage gives an additional option: "To prevent the passwords from being seen, store them in .wgetrc or .netrc, and make sure to protect those files from other users with "chmod"."
– lxgr
Jun 10 '16 at 9:32
2
If--ask-passwordis not available or you don't want to type the password every time,wget -i link.txtcan help, wherelink.txtcontainsftp://remote_user:SECRET@ftp.example.com/file.ext
– tehnicaorg
Apr 27 '18 at 13:57
add a comment |
5
While it is not visible in history, it is visible to all who conduct a ps, top, htop or similar command while the process is running.
– user412812
May 22 '15 at 20:04
4
@AbdennourTOUMI Why would you disable certificate checks, especially if you are sending a password with the request? That is definitely not advisable in general. As far as "hiding" the password on logs or /proc is concerned, the wget manpage gives an additional option: "To prevent the passwords from being seen, store them in .wgetrc or .netrc, and make sure to protect those files from other users with "chmod"."
– lxgr
Jun 10 '16 at 9:32
2
If--ask-passwordis not available or you don't want to type the password every time,wget -i link.txtcan help, wherelink.txtcontainsftp://remote_user:SECRET@ftp.example.com/file.ext
– tehnicaorg
Apr 27 '18 at 13:57
5
5
While it is not visible in history, it is visible to all who conduct a ps, top, htop or similar command while the process is running.
– user412812
May 22 '15 at 20:04
While it is not visible in history, it is visible to all who conduct a ps, top, htop or similar command while the process is running.
– user412812
May 22 '15 at 20:04
4
4
@AbdennourTOUMI Why would you disable certificate checks, especially if you are sending a password with the request? That is definitely not advisable in general. As far as "hiding" the password on logs or /proc is concerned, the wget manpage gives an additional option: "To prevent the passwords from being seen, store them in .wgetrc or .netrc, and make sure to protect those files from other users with "chmod"."
– lxgr
Jun 10 '16 at 9:32
@AbdennourTOUMI Why would you disable certificate checks, especially if you are sending a password with the request? That is definitely not advisable in general. As far as "hiding" the password on logs or /proc is concerned, the wget manpage gives an additional option: "To prevent the passwords from being seen, store them in .wgetrc or .netrc, and make sure to protect those files from other users with "chmod"."
– lxgr
Jun 10 '16 at 9:32
2
2
If
--ask-password is not available or you don't want to type the password every time, wget -i link.txt can help, where link.txt contains ftp://remote_user:SECRET@ftp.example.com/file.ext– tehnicaorg
Apr 27 '18 at 13:57
If
--ask-password is not available or you don't want to type the password every time, wget -i link.txt can help, where link.txt contains ftp://remote_user:SECRET@ftp.example.com/file.ext– tehnicaorg
Apr 27 '18 at 13:57
add a comment |
The command could have used --http-user and --http-password instead of --user and --password. In case of ftp request the options are --ftp-user and --ftp-password.
edited Jun 15 '17 at 13:51
0xF2
2,35722045
answered Jun 15 '17 at 9:05
MradulMradul
1
2
This is not entirely correct:man wgetindicates that --user and --password are valid options, which can be overridden by --http-user or --ftp-password
– Charles Green
Jun 15 '17 at 13:04
add a comment |
The command could have used --http-user and --http-password instead of --user and --password. In case of ftp request the options are --ftp-user and --ftp-password.
edited Jun 15 '17 at 13:51
0xF2
2,35722045
answered Jun 15 '17 at 9:05
MradulMradul
1
2
This is not entirely correct:man wgetindicates that --user and --password are valid options, which can be overridden by --http-user or --ftp-password
– Charles Green
Jun 15 '17 at 13:04
add a comment |
The command could have used --http-user and --http-password instead of --user and --password. In case of ftp request the options are --ftp-user and --ftp-password.
edited Jun 15 '17 at 13:51
0xF2
2,35722045
answered Jun 15 '17 at 9:05
MradulMradul
1
The command could have used --http-user and --http-password instead of --user and --password. In case of ftp request the options are --ftp-user and --ftp-password.
edited Jun 15 '17 at 13:51
0xF2
2,35722045
answered Jun 15 '17 at 9:05
MradulMradul
1
edited Jun 15 '17 at 13:51
0xF2
2,35722045
edited Jun 15 '17 at 13:51
0xF2
2,35722045
edited Jun 15 '17 at 13:51
0xF2
2,35722045
2,35722045
answered Jun 15 '17 at 9:05
MradulMradul
1
answered Jun 15 '17 at 9:05
MradulMradul
1
answered Jun 15 '17 at 9:05
MradulMradul
1
1
2
This is not entirely correct:man wgetindicates that --user and --password are valid options, which can be overridden by --http-user or --ftp-password
– Charles Green
Jun 15 '17 at 13:04
add a comment |
2
This is not entirely correct:man wgetindicates that --user and --password are valid options, which can be overridden by --http-user or --ftp-password
– Charles Green
Jun 15 '17 at 13:04
2
2
This is not entirely correct:
man wget indicates that --user and --password are valid options, which can be overridden by --http-user or --ftp-password– Charles Green
Jun 15 '17 at 13:04
This is not entirely correct:
man wget indicates that --user and --password are valid options, which can be overridden by --http-user or --ftp-password– Charles Green
Jun 15 '17 at 13:04
add a comment |
This procedure is working ok in Linux server with no GUI if you need to download from web sites (like oracle.com) where you need to login and also accept Oracle rules of usage.
Part - you need machine with GUI or just smartphone only to get final link which you will use to download**
Login to Oracle or whatever site you need login to start downloading something, accept usage rules and start download in Chrome or any other browser and than copy download link from download tab, it should contain authorization parameter. Link should look something like this:
Pause download in Chrome.
Paste that download link to place from where you can wget-it or just type it in if it's not too long.
and justwgetthat whole link in your Linux machine with:
wget http://download.oracle.com/otn/linux/oracle12c/122010/linuxx64_12201_database.zip?AuthParam=1539333101_448acded002c607377c51b62730a816f
Works like charm :). I'm downloading Oracle database from:
https://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html
to Ubuntu like this.
It's probably not going to work for every case but works fine for my case :)
answered Oct 12 '18 at 8:36
HarveyHarvey
992
3
One (the crucial, in fact) purpose ofwgetis to download web content from the commandline without any GUI involved.
– PerlDuck
Oct 12 '18 at 8:48
@PerlDuck It looks like you didn't read my answer at all. You do not need GUI in linux machine for download using this procedure. This procedure only involves GUI for logging and for finding correct link to downloading . Thank you for unreasonable -1.
– Harvey
Dec 11 '18 at 6:19
I didn't downvote your post, sorry.
– PerlDuck
Dec 11 '18 at 9:14
@PerlDuck I'm sorry then. You don't have to downvote, others will do that after they look at your comment/reputation and without reading more than twitter amount of text from my post...
– Harvey
Dec 11 '18 at 11:44
add a comment |
This procedure is working ok in Linux server with no GUI if you need to download from web sites (like oracle.com) where you need to login and also accept Oracle rules of usage.
Part - you need machine with GUI or just smartphone only to get final link which you will use to download**
Login to Oracle or whatever site you need login to start downloading something, accept usage rules and start download in Chrome or any other browser and than copy download link from download tab, it should contain authorization parameter. Link should look something like this:
Pause download in Chrome.
Paste that download link to place from where you can wget-it or just type it in if it's not too long.
and justwgetthat whole link in your Linux machine with:
wget http://download.oracle.com/otn/linux/oracle12c/122010/linuxx64_12201_database.zip?AuthParam=1539333101_448acded002c607377c51b62730a816f
Works like charm :). I'm downloading Oracle database from:
https://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html
to Ubuntu like this.
It's probably not going to work for every case but works fine for my case :)
answered Oct 12 '18 at 8:36
HarveyHarvey
992
3
One (the crucial, in fact) purpose ofwgetis to download web content from the commandline without any GUI involved.
– PerlDuck
Oct 12 '18 at 8:48
@PerlDuck It looks like you didn't read my answer at all. You do not need GUI in linux machine for download using this procedure. This procedure only involves GUI for logging and for finding correct link to downloading . Thank you for unreasonable -1.
– Harvey
Dec 11 '18 at 6:19
I didn't downvote your post, sorry.
– PerlDuck
Dec 11 '18 at 9:14
@PerlDuck I'm sorry then. You don't have to downvote, others will do that after they look at your comment/reputation and without reading more than twitter amount of text from my post...
– Harvey
Dec 11 '18 at 11:44
add a comment |
This procedure is working ok in Linux server with no GUI if you need to download from web sites (like oracle.com) where you need to login and also accept Oracle rules of usage.
Part - you need machine with GUI or just smartphone only to get final link which you will use to download**
Login to Oracle or whatever site you need login to start downloading something, accept usage rules and start download in Chrome or any other browser and than copy download link from download tab, it should contain authorization parameter. Link should look something like this:
Pause download in Chrome.
Paste that download link to place from where you can wget-it or just type it in if it's not too long.
and justwgetthat whole link in your Linux machine with:
wget http://download.oracle.com/otn/linux/oracle12c/122010/linuxx64_12201_database.zip?AuthParam=1539333101_448acded002c607377c51b62730a816f
Works like charm :). I'm downloading Oracle database from:
https://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html
to Ubuntu like this.
It's probably not going to work for every case but works fine for my case :)
answered Oct 12 '18 at 8:36
HarveyHarvey
992
This procedure is working ok in Linux server with no GUI if you need to download from web sites (like oracle.com) where you need to login and also accept Oracle rules of usage.
Part - you need machine with GUI or just smartphone only to get final link which you will use to download**
Login to Oracle or whatever site you need login to start downloading something, accept usage rules and start download in Chrome or any other browser and than copy download link from download tab, it should contain authorization parameter. Link should look something like this:
Pause download in Chrome.
Paste that download link to place from where you can wget-it or just type it in if it's not too long.
and justwgetthat whole link in your Linux machine with:
wget http://download.oracle.com/otn/linux/oracle12c/122010/linuxx64_12201_database.zip?AuthParam=1539333101_448acded002c607377c51b62730a816f
Works like charm :). I'm downloading Oracle database from:
https://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html
to Ubuntu like this.
It's probably not going to work for every case but works fine for my case :)
answered Oct 12 '18 at 8:36
HarveyHarvey
992
edited Dec 11 '18 at 7:19
answered Oct 12 '18 at 8:36
HarveyHarvey
992
answered Oct 12 '18 at 8:36
HarveyHarvey
992
answered Oct 12 '18 at 8:36
HarveyHarvey
992
992
3
One (the crucial, in fact) purpose ofwgetis to download web content from the commandline without any GUI involved.
– PerlDuck
Oct 12 '18 at 8:48
@PerlDuck It looks like you didn't read my answer at all. You do not need GUI in linux machine for download using this procedure. This procedure only involves GUI for logging and for finding correct link to downloading . Thank you for unreasonable -1.
– Harvey
Dec 11 '18 at 6:19
I didn't downvote your post, sorry.
– PerlDuck
Dec 11 '18 at 9:14
@PerlDuck I'm sorry then. You don't have to downvote, others will do that after they look at your comment/reputation and without reading more than twitter amount of text from my post...
– Harvey
Dec 11 '18 at 11:44
add a comment |
3
One (the crucial, in fact) purpose ofwgetis to download web content from the commandline without any GUI involved.
– PerlDuck
Oct 12 '18 at 8:48
@PerlDuck It looks like you didn't read my answer at all. You do not need GUI in linux machine for download using this procedure. This procedure only involves GUI for logging and for finding correct link to downloading . Thank you for unreasonable -1.
– Harvey
Dec 11 '18 at 6:19
I didn't downvote your post, sorry.
– PerlDuck
Dec 11 '18 at 9:14
@PerlDuck I'm sorry then. You don't have to downvote, others will do that after they look at your comment/reputation and without reading more than twitter amount of text from my post...
– Harvey
Dec 11 '18 at 11:44
3
3
One (the crucial, in fact) purpose of
wget is to download web content from the commandline without any GUI involved.– PerlDuck
Oct 12 '18 at 8:48
One (the crucial, in fact) purpose of
wget is to download web content from the commandline without any GUI involved.– PerlDuck
Oct 12 '18 at 8:48
@PerlDuck It looks like you didn't read my answer at all. You do not need GUI in linux machine for download using this procedure. This procedure only involves GUI for logging and for finding correct link to downloading . Thank you for unreasonable -1.
– Harvey
Dec 11 '18 at 6:19
@PerlDuck It looks like you didn't read my answer at all. You do not need GUI in linux machine for download using this procedure. This procedure only involves GUI for logging and for finding correct link to downloading . Thank you for unreasonable -1.
– Harvey
Dec 11 '18 at 6:19
I didn't downvote your post, sorry.
– PerlDuck
Dec 11 '18 at 9:14
I didn't downvote your post, sorry.
– PerlDuck
Dec 11 '18 at 9:14
@PerlDuck I'm sorry then. You don't have to downvote, others will do that after they look at your comment/reputation and without reading more than twitter amount of text from my post...
– Harvey
Dec 11 '18 at 11:44
@PerlDuck I'm sorry then. You don't have to downvote, others will do that after they look at your comment/reputation and without reading more than twitter amount of text from my post...
– Harvey
Dec 11 '18 at 11:44
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f29079%2fhow-do-i-provide-a-username-and-password-to-wget%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I don't think you can reliably use the user:pass@name syntax there;
wgethas separate command line options for those instead, so is probably naively parsing the string after the:as a port number.– geekosaur
Mar 5 '11 at 3:02