Hide

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.

OpenID
or
Sign in Register

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

Hide

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:

Hide

News

2011-03-12 - Confoo 2011 presentation
Slides are available from the commandlinefu presentation at Confoo 2011: http://presentations.codeinthehole.com/confoo2011/
2011-01-04 - Moderation now required for new commands
To try and put and end to the spamming, new commands require moderation before they will appear on the site.
2010-12-27 - Apologies for not banning the trolls sooner
Have been away from the interwebs over Christmas. Will be more vigilant henceforth.
2010-09-24 - OAuth and pagination problems fixed
Apologies for the delay in getting Twitter's OAuth supported. Annoying pagination gremlin also fixed.
Hide

Tags

Hide

Functions

Hide

Credits

Site by David Winterbottom (user root).

One command line web server on port 80 using nc (netcat)

Terminal - One command line web server on port 80 using nc (netcat)
while true ; do nc -l 80 < index.html ; done
2011-08-31 15:17:33
User: ztank1013
Functions: true
9
Up
Down
One command line web server on port 80 using nc (netcat)

Very simple web server listening on port 80 will serve index.html file or whatever file you like pointing your browser at http://your-IP-address/index.html for example.

If your web server is down for maintenance and you'd like to inform your visitors about it, quickly and easily, you just have to put into the index.html file the right HTML code and you are done! Of course you need to be root to run the command using port 80.

Add to favourites | Report as malicious

Alternatives

There is 1 alternative - vote for the best!

Terminal - Alternatives

Know a better way?

If you can do better, submit your command here.

What others think

cool - or deliver contents directly from a string:

while true ; do nc -l 8888

Comment by bashrc 93 weeks and 3 days ago

ups mangeled comment - here it is again:

while true ; do nc -l 8888 <<<works ; done
Comment by bashrc 93 weeks and 3 days ago

Don't you need to prepend proper HTTP headers to the output?

Firefox, lynx and Chromium allow it to pass, but Midori/Webkit gives the bad-response-from-server error I expected. Does the HTTP spec allow for a zero-length header to the response message?

Comment by Mozai 92 weeks and 4 days ago

@Mozai Yes you are totally right! HTTP/1.1 version requires at least the status line in the response:

Status-Line = HTTP-Version SP Status-Code SP Reason-Phrase CRLF

hence there are a couple of way to fix the command:

[1] put this at the beginning of the index.html file:

HTTP/1.1 200 OK (followed by a CRLF carriage return and a line feed

[2] or you may want to fine tune the initial command to look like this:

while true; do { echo -e 'HTTP/1.1 200 OK\r\n'; cat index.html; } | nc -l 80; done

Not sure but additional '\r\n' might be necessary...

Comment by ztank1013 92 weeks and 4 days ago

Your point of view

You must be signed in to comment.

Related sites and podcasts