3 ms·
Same here, I thought it caused cURL to do a GET request and throw away the body, but it doesn't, and I've gotten different results more than once.
by StavrosK 5y ago
Same here, I thought it caused cURL to do a GET request and throw away the body, but it doesn't, and I've gotten different results more than once.
- johnvaluk 5y agoAlso consider changing the user-agent from the default. I set mine to a typical browser string in ~/.curlrc, but you can also use -A/--user-agent on the command line.
- iampims 5y agocurl -i (lowercase) prints the headers as well as the response body without the verbosity of -v
- nerdponx 5y agoI believe you can also control what exactly is emitted with -w, which is nicer than trying to parse it later.