Have a look at gatling <a href="http://www.fefe.de/gatling/" rel="nofollow">http://www.fefe.de/gatling/</a> it's a http/ftp/smb server based on libowfat (-lowfat ;0) with ssl support. Contains basically everything you need to share a file. It is also quite scalable, see <a href="http://bulk.fefe.de/scalability/" rel="nofollow">http://bulk.fefe.de/scalability/</a> for an old benchmark.<p>One neat feature is that gatling disables the autoindex links for sorting the listing if wget is used to download/mirror a directory.<p>Gatling has a pretty good default configuration like automatically try to bound port 80 and if not available use port 8000 instead, automatically sharing the current directory etc. For a list of command-line configuration options have a look at <a href="http://paste.pocoo.org/show/409206/" rel="nofollow">http://paste.pocoo.org/show/409206/</a>
I built a simple zero-configuration FTP server that runs in a browser some time ago (<a href="http://ezyftpserver.com/" rel="nofollow">http://ezyftpserver.com/</a>). Been wondering if I should do the same with a HTTP server?
Looks nice, I was looking for something similar the other day, easily sharing a directory over HTTP from command line. I ended up writing a couple of very simple bash functions that added/removed the current directory to ~/Sites (I'm on a Mac). Apache did the rest.
<i>sigh</i><p>Not another "Download this shell script over insecure HTTP and pipe it to sh" gimmick. Really? While <a href="http://news.ycombinator.com/item?id=2661209" rel="nofollow">http://news.ycombinator.com/item?id=2661209</a> is <i>directly</i> above this item on the front page?<p>Have we learned nothing?