HTTP Request is undefined in WebSockets

[stewartmcgown]

This bit of code expects there to be an express request object always present on the context. For long lived websocket connections, this isn't always the case. We should be able to fall back to the Websocket's original connecting IP and handle the rate limiting that way.

[onur-ozkan]

thanks for letting me know, I will work on it soon. @stewartmcgown

[stewartmcgown]

I'm not even sure if its possible to get access to the original request object at this point. If not, we may have to add an extra setup step for the websocket connection that stores the connecting IP somewhere

[smiley-uriux]

This is essentially the same error I hit when reporting #41