In my testing, 'close' was fired. It happens at the end of the HTTP response. The Twitter API is responding with an HTML response body, a 401 status code, and ending the response.

Testing response codes in the initial response callback *is* a better way to do it, since you can make the decision regardless of the response body, but I wanted to minimize code structure changes in my PR so I chose to add it near the existing error handling code.

@ttezel, I'd be happy to update the PR if you'd like. Your review and feedback is appreciated!