alessioalex

In August 2007 a hacker found a way to expose the PHP source code on facebook.com. He retrieved two files and then emailed them to me, and I wrote about the issue:

http://techcrunch.com/2007/08/11/facebook-source-code-leaked/

It became a big deal:

http://www.techmeme.com/070812/p1#a070812p1

The two files are index.php (the homepage) and search.php (the search page)

alessioalex

// data comes from here http://stat-computing.org/dataexpo/2009/the-data.html
// download 1994.csv.bz2 and unpack by running: cat 1994.csv.bz2 | bzip2 -d > 1994.csv
// 1994.csv should be ~5.2 million lines and 500MB
// importing all rows into leveldb took ~50 seconds on my machine

// there are two main techniques at work here:
// 1: never create JS objects, leave the data as binary the entire time (binary-split does this)
// 2: group lines into 16 MB batches, to take advantage of leveldbs batch API (byte-stream does this)

var level = require('level')

alessioalex

var lru = require('lru-cache')
  , couchwatch = require('couchwatch')
  , request = require('request')
  ;

function RegistryCache () {
  this.cache = lru()
  this.watch = couchwatch('http://isaacs.iriscouch.com/registry', -1)
  this.watch.on('row', function (change) {
    this.cache.del(change.id)

alessioalex

Playing with D3.js to get a drill down behavior for a hierarchical data collection represented in pie charts. See live example

alessioalex

var fs = require('fs');
var lame = require('lame');
var Speaker = require('speaker');

fs.createReadStream(process.argv[2])
  .pipe(new lame.Decoder())
  .on('format', function (format) {
    this.pipe(new Speaker(format));
  });

alessioalex

## The Problem

Standard practices say no non-root process gets to talk to the Internet on a port less than 1024.  How, then, could I get Node talking on port 80 on EC2?  (I wanted it to go as fast as possible and use the smallest possible share of my teeny tiny little micro-instance's resources, so proxying through nginx or Apache seemed suboptimal.)  

## The temptingly easy but ultimately wrong solution:

Alter the port the script talks to from 8000 to 80:

    }).listen(80);

alessioalex

:+1:
:-1:
:airplane:
:art:
:bear:
:beer:
:bike:
:bomb:
:book:
:bulb:

alessioalex

function hangups (req, res, next){
    var reqd = domain.create()
    reqd.add(req)
    reqd.add(res)
    reqd.on('error', function (error) {
        if (error.code !== 'ECONNRESET') console.error(error, req.url)
        reqd.dispose()
    })
    next()
}

alessioalex

var http = require('http');
var https = require('https');
var httpProxy = require('http-proxy');
var crypto = require('crypto');
var fs = require('fs');

/*
 * Server configurations
 */
var servers = {

alessioalex

//Thanks to:
//http://www.benjiegillam.com/2012/06/node-dot-js-ssl-certificate-chain/

//For the code to pass a CA bundle (multiple certs in one file) as an array 
//which fixes certificate errors on some browsers when doing https.createServer(options


//This is how you can fix that with nodejitsu's http-proxy when using SNI
// to have a server listening and returning multiple ssl certs