Dump HTTP header using wget

wget --server-response --spider http://www.example.com/
Let me suggest using wget for obtaining the HTTP header only as the last resort because it generates considerable textual overhead. The first ellipsis of the sample output stands for Spider mode enabled. Check if remote file exists. --2009-03-31 20:42:46-- http://www.example.com/ Resolving www.example.com... 208.77.188.166 Connecting to www.example.com|208.77.188.166|:80... connected. HTTP request sent, awaiting response... and the second one looks for Length: 438 [text/html] Remote file exists and could contain further links, but recursion is disabled -- not retrieving.
Sample Output
…
  HTTP/1.1 200 OK
  Date: Tue, 31 Mar 2009 18:42:46 GMT
  Server: Apache/2.2.3 (CentOS)
  Last-Modified: Tue, 15 Nov 2005 13:24:10 GMT
  ETag: "b80f4-1b6-80bfd280"
  Accept-Ranges: bytes
  Content-Length: 438
  Connection: close
  Content-Type: text/html; charset=UTF-8
…

7
By: penpen
2009-03-31 18:49:14

What Others Think

slightly easier with curl tho: curl -I http://www.example.com
realgt · 458 weeks and 3 days ago
realgt, that issues a HEAD request though, which may not be supported by the server whereas what I really want is the GET request, but display only the headers.
sgornick · 423 weeks and 3 days ago
curl --head http://www.example.com
sgornick · 423 weeks and 3 days ago
curl is easer. in general curl is always simpler to use then any other like wget, lynx, etc
jonnys · 356 weeks and 6 days ago
Agreed curl is the best. I always do: curl -sv http://www.example.com > /dev/null to get just the client and server headers.
fancylad · 323 weeks and 3 days ago
This is a perfect command CURL uses more memory and resources than wget and is less commond on routers and minilinux.
alecuba16 · 312 weeks and 3 days ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands



Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for: