gevent-socketio not using my @app.route endpoint for socketio

Question

I am using Flask together with gevent-socketio: ``` $ cat requirements.txt Flask==0.10.1 Jinja2==2.7.1 MarkupSafe==0.18 Werkzeug==0.9.3 argparse==1.2.1 gevent==0.13.8 gevent-socketio==0.3.5-rc2 gevent-websocket==0.3.6 greenlet==0.4.1 itsdangerous==0.23 wsgiref==0.1.2 ``` I'm using a pretty standard setup to start the server: ``` #Called from __main__ def run_dev_server(): app.debug = True port = 5000 dapp = werkzeug.debug.DebuggedApplication(app, evalex = True) SocketIOServer(('', port), dapp, resource="socket.io").serve_forever() ``` And a pretty standard hook for my SocketIO namespace: ``` @app.route('/socket.io/<path:rest>') def push_stream(rest): print 'ws connect', rest try: socketio.socketio_manage(request.environ, {'/join_notification': JoinsNamespace}, request) except Exception as e: app.logger.error("Exception while handling socketio connection", exc_info=True) return flask.Response() ``` However, I'm having problems where 'connect' events aren't being fired on the client. Af…

Accepted Answer

The weird behavior is because of this line:

```
dapp = werkzeug.debug.DebuggedApplication(app, evalex = True)
```

Socketio and the werkzeug debugger don't work together. There is already an open issue about this see: https://github.com/abourget/gevent-socketio/issues/114

But you can work around it by making a custom debugger class.

```
from werkzeug.debug import DebuggedApplication
class MyDebuggedApplication(DebuggedApplication):
    def __call__(self, environ, start_response):
        # check if websocket call
        if "wsgi.websocket" in environ and not environ["wsgi.websocket"] is None:
            # a websocket call, no debugger ;)
            return self.app(environ, start_response)
        # else go on with debugger
        return DebuggedApplication.__call__(self, environ, start_response)

# remember to call the overwritten debugger in your run_dev_server() function
dapp = MyDebuggedApplication(app, evalex = True)
```

The patch relies on the environment-key wsgi.websocket, which only seems to be present in websocket calls. Be careful, I haven't put much thought into that, there are might be other issues.

gevent-socketio not using my @app.route endpoint for socketio

Solution

Problem