What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again.

Delete that bloated snippets file you've been using and share your personal repository with the world. 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.

If you have a new feature suggestion or find a bug, please get in touch via http://commandlinefu.uservoice.com/

Get involved!

You can sign-in using OpenID credentials, or register a traditional username and password.

First-time OpenID users will be automatically assigned a username which can be changed after signing in.

Universal configuration monitoring and system of record for IT.

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:



May 19, 2015 - A Look At The New Commandlinefu
I've put together a short writeup on what kind of newness you can expect from the next iteration of clfu. Check it out here.
March 2, 2015 - New Management
I'm Jon, I'll be maintaining and improving clfu. Thanks to David for building such a great resource!

Top Tags



Dump HTTP header using wget

Terminal - Dump HTTP header using wget
wget --server-response --spider http://www.example.com/
2009-03-31 18:49:14
User: penpen
Functions: wget
Dump HTTP header using wget

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...

Connecting to www.example.com||: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.


There are 9 alternatives - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

slightly easier with curl tho:

curl -I http://www.example.com
Comment by realgt 341 weeks and 5 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.

Comment by sgornick 306 weeks and 4 days ago

curl --head http://www.example.com

Comment by sgornick 306 weeks and 4 days ago

curl is easer. in general curl is always simpler to use then any other like wget, lynx, etc

Comment by jonnys 240 weeks 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.

Comment by fancylad 206 weeks and 5 days ago

This is a perfect command CURL uses more memory and resources than wget and is less commond on routers and minilinux.

Comment by alecuba16 195 weeks and 4 days ago

Your point of view

You must be signed in to comment.