I had the logic backwards.

If the status is truthy (ie. 200, 201, 400, 500, etc), then we want everything possible.  If the status is falsy (undefined, 0, empty string), then something is severely wrong and we can't assume anything is really there or anything is really correct.
Merge pull request #7 from fidian/master

I had the logic backwards with checking this.status