When you initally run siege you will see the following in the console:
TypeError: Cannot read property 'length' of undefined
at Cached.<anonymous> (/Users/ccowan/Desktop/cache_slam/node_modules/jaws/index.js:386:55)
at Cached.EventEmitter.emit (events.js:99:17)
at /Users/ccowan/Desktop/cache_slam/node_modules/jaws/index.js:163:37
at next (/Users/ccowan/Desktop/cache_slam/node_modules/jaws/index.js:151:11)
at Route.verify (/Users/ccowan/Desktop/cache_slam/node_modules/jaws/index.js:226:5)
at getRoute (/Users/ccowan/Desktop/cache_slam/node_modules/jaws/index.js:155:11)
at /Users/ccowan/Desktop/cache_slam/node_modules/jaws/index.js:162:9
at Domain.bind.b (domain.js:201:18)
at Domain.run (domain.js:141:23)
at Application.<anonymous> (/Users/ccowan/Desktop/cache_slam/node_modules/jaws/index.js:50:7)
Which will eventually fix it's self once the first cache item writes. Leave siege running... Then when you hit http://localhost:4444/clear-cache you will see the errors show up again as all the requests are trying to fill the cache at the same time. If you run siege on the clear-cache
endpoint it will eventually blow up.