WGET and CURL
目录
WGET and CURL
对比
CURL 和WGET都可以用来下载文件，用法也类似：curl/wget [-option...] [url..]
但两者还是有区别的
|对比||
|--|--|
|curl| 1. curl是LInux下的数据传输工具，可以通过URL想服务器上传数据，或者从服务器下载数据。curl支持HTTP、FTP、SMTP、RSTP等应用层协议。 2. curl参数更多更复杂，需要依赖libcurl库，可以把 cURL 想象成一个精简的命令行网页浏览器。它支持几乎你能想到的所有协议，可以交互访问几乎所有在线内容。唯一和浏览器不同的是，cURL 不会渲染接收到的相应信息
|wget |wget是Linux系统中的文件下载命令， 支持HTTP、FTP等协议。 wget是非交互性的，且具有自动下载功能， 能自己在后台工作。 也就是说在用户logout之后，wget仍然能够继续完成自己的工作。 wget更简单，不依赖其他的库，且没有那么多的复杂参数|
wget
| 参数 | 解释 |
|---|---|
| -d： | 调试模式 -d参数能够打印出wget运行时的调试信息：如HTTP报文头等。这个参数非常有用。 |
| -O： | 指定本地文件名 wget www.sina.com -O sina.html表示将www.sina.com 的内容下载到sina.html。 |
| -b： | 后台运行 wget运行在后台，用户logout之后仍能继续下载 |
curl
| 参数 | 用法 | 详解 |
|---|---|---|
| -o | 传输到指定文件，也就是要指定文件名 | eg：curl -o baidu_index.html www.baidu.com可以将百度首页的html源码保存到baidu_index.html文件中 |
| -O | 使用url默认文件名传输 | eg：curl -O http://img.wallpapersking.com/800/2012-8/20120812103710.jpg 直接将图片保存到本地文件20120812103710.jpg |
| -A | --user-agent | 设置用户代理发送给服务器 |
| -b | --cookie <name=string/file> | cookie字符串或文件读取位置 |
| -c小写c | --cookie-jar | 操作结束后把cookie写入到这个文件中 |
| -C大写C | --continue-at | 断点续转 |
| -D | --dump-header | 把header信息写入到该文件中 |
| -e | --referer | 来源网址 |
| -f | --fail | 连接失败时不显示http错误 |
| -o | --output | 把输出写到该文件中 |
| -O | --remote-name | 把输出写到该文件中，保留远程文件的文件名 |
| -r | --range | 检索来自HTTP/1.1或FTP服务器字节范围 |
| -s | --silent | 静音模式。不输出任何东西 |
| -T | --upload-file | 上传文件 |
| -u | --user <user[:password]> | 设置服务器的用户和密码 |
| -w | --write-out [format] | 什么输出完成后 |
| -x | --proxy <host[:port]> | 在给定的端口上使用HTTP代理 |
| -# | --progress-bar | 进度条显示当前的传送状态 |
curl使用示例
下载docker compose包到指定文件
curl -L https://github.com/docker/compose/releases/download/1.24.0-rc1/docker-compose-Linux-x86_64> /usr/local/bin/docker-compose
|用法|命令|解释|
|--|--|--|
|下载页面： |curl -o index.html http://url.com |
|下载文件并显示简单进度条：|curl -# -o centos6.8.iso http://mirrors.aliyun.com/centos/6.8/isos/x86_64/CentOS-6.8-x86_64-minimal.iso |
|断点续传： |curl -# -o centos6.8.iso -C - http://mirrors.aliyun.com/centos/6.8/isos/x86_64/CentOS-6.8-x86_64-minimal.iso |
|伪造来源页面： |curl -e http://url.com http://B.com | #告诉B目标网站，我是从地址url来的
|伪造代理设备： |curl -url " Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" http://B.com | 告诉B目标网站，我是GOOGLE爬虫蜘蛛" Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)"当然其实换成"Mozilla/5.0 AppleWebKit/600 Mobile MicroMessenger/6.0"就是微信内置浏览器
|查看本站的http头： |curl -I http://url.com |输出内容一般为：HTTP/1.1 200 OK；Date: Fri, 25 Nov 2016 16:45:49 GMT；Server: Apache；Set-Cookie: rox__Session=abdrt8vesprhnpc3f63p1df7j4; path=/；...
|设置http请求头： |curl -H "Cache-Control:no-cache" http://url.com |
|发送表单数据： |curl -F "pic=@logo.png" -F "site=aiezu" http://url.com/ |
|发送cookie： |curl -b "domain=url.com" http://url.com
curl退出码
| 退出码 | 错误描述 |
|---|---|
| 1 | Unsupported protocol. This build of curl has no support for this protocol. |
| 2 | Failed to initialize. |
| 3 | URL malformed. The syntax was not correct. |
| 5 | Couldn't resolve proxy. The given proxy host could not be resolved. |
| 6 | Couldn't resolve host. The given remote host was not resolved. |
| 7 | Failed to connect to host. |
| 8 | FTP weird server reply. The server sent data curl couldn't parse. |
| 9 | FTP access denied. The server denied login or denied access to the particular resource or directory you wanted to reach. Most often you tried to change to a directory that doesn't exist on the server. |
| 11 | FTP weird PASS reply. Curl couldn't parse the reply sent to the PASS request. |
| 13 | FTP weird PASV reply, Curl couldn't parse the reply sent to the PASV request. |
| 14 | FTP weird 227 format. Curl couldn't parse the 227-line the server sent. |
| 15 | FTP can't get host. Couldn't resolve the host IP we got in the 227-line. |
| 17 | FTP couldn't set binary. Couldn't change transfer method to binary. |
| 18 | Partial file. Only a part of the file was transferred. |
| 19 | FTP couldn't download/access the given file, the RETR (or similar) command failed. |
| 21 | FTP quote error. A quote command returned error from the server. |
| 22 | HTTP page not retrieved. The requested url was not found or returned another error with the HTTP error code being 400 or above. This return code only appears if -f/--fail is used. |
| 23 | Write error. Curl couldn't write data to a local filesystem or similar. |
| 25 | FTP couldn't STOR file. The server denied the STOR operation, used for FTP uploading. |
| 26 | Read error. Various reading problems. |
| 27 | Out of memory. A memory allocation request failed. |
| 28 | Operation timeout. The specified time-out period was reached according to the conditions. |
| 30 | FTP PORT failed. The PORT command failed. Not all FTP servers support the PORT command, try doing a transfer using PASV instead! |
| 31 | FTP couldn't use REST. The REST command failed. This command is used for resumed FTP transfers. |
| 33 | HTTP range error. The range "command" didn't work. |
| 34 | HTTP post error. Internal post-request generation error. |
| 35 | SSL connect error. The SSL handshaking failed. |
| 36 | FTP bad download resume. Couldn't continue an earlier aborted download. |
| 37 | FILE couldn't read file. Failed to open the file. Permissions? |
| 38 | LDAP cannot bind. LDAP bind operation failed. |
| 39 | LDAP search failed. |
| 41 | Function not found. A required LDAP function was not found. |
| 42 | Aborted by callback. An application told curl to abort the operation. |
| 43 | Internal error. A function was called with a bad parameter. |
| 45 | Interface error. A specified outgoing interface could not be used. |
| 47 | Too many redirects. When following redirects, curl hit the maximum amount. |
| 48 | Unknown TELNET option specified. |
| 49 | Malformed telnet option. |
| 51 | The peer's SSL certificate or SSH MD5 fingerprint was not ok. |
| 52 | The server didn't reply anything, which here is considered an error. |
| 53 | SSL crypto engine not found. |
| 54 | Cannot set SSL crypto engine as default. |
| 55 | Failed sending network data. |
| 56 | Failure in receiving network data. |
| 58 | Problem with the local certificate. |
| 59 | Couldn't use specified SSL cipher. |
| 60 | Peer certificate cannot be authenticated with known CA certificates. |
| 61 | Unrecognized transfer encoding. |
| 62 | Invalid LDAP URL. |
| 63 | Maximum file size exceeded. |
| 64 | Requested FTP SSL level failed. |
| 65 | Sending the data requires a rewind that failed. |
| 66 | Failed to initialize SSL Engine. |
| 67 | The user name, password, or similar was not accepted and curl failed to log in. |
| 68 | File not found on TFTP server. |
| 69 | Permission problem on TFTP server. |
| 70 | Out of disk space on TFTP server. |
| 71 | Illegal TFTP operation. |
| 72 | Unknown TFTP transfer ID. |
| 73 | File already exists (TFTP). |
| 74 | No such user (TFTP). |
| 75 | Character conversion failed. |
| 76 | Character conversion functions required. |
| 77 | Problem with reading the SSL CA cert (path? access rights?). |
| 78 | The resource referenced in the URL does not exist. |
| 79 | An unspecified error occurred during the SSH session. |
| 80 | Failed to shut down the SSL connection. |
| 82 | Could not load CRL file, missing or wrong format (added in 7.19.0). |
| 83 | Issuer check failed (added in 7.19.0). |
| XX | More error codes will appear here in future releases. The existing ones are meant to never change. |
本博客为Swagger-Ranger的笔记分享，文中源码地址： https://github.com/Swagger-Ranger
欢迎交流指正，如有侵权请联系作者确认删除： liufei32@outlook.com
