[uWSGI] Routing to websocket using a named unix socket

[Jacob Rief]

Unfortunately I'am unable to get uWSGI's router, proxying my websocket
request to a uWSGI instance listening on a named unix socket.

In my configuration I have an emperor spawning two vassals. One vassal
serves normal Django requests, while the other vassal serves Websockets
requests. They both own a separate named Unix socket.

Currently nginx forwards requests to these two sockets and this works fine.
The nginx configuration inside a server section looks like this:

server {
    ....

    location / {
        include /opt/local/etc/nginx/uwsgi_params;
        uwsgi_pass unix:/var/tmp/django.socket;
    }

    location /ws/ {
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        proxy_pass http://unix:/var/tmp/web.socket;
    }
}

Now I wanted to replace nginx by uWSGI itself and use its own routing
mechanism. For normal web requests this works fine and inside my
configuration I have

[uwsgi]emperor = vassals

http-socket = :9090

#no-orphans = true

#threads = 1

#die-on-term = true

http-websockets = true

route = ^/ws http:unix:/var/tmp/web.socket

route = ^/ uwsgi:/var/tmp/django.socket,0,0

_______________________________________________
uWSGI mailing list
uWSGI@lists.unbit.it
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi