> >> Hello! >> >> (Cc'd nginx-devel@ as this is better list for this discussion.) >> >> On Wed, Feb 20, 2013 at 02:30:38PM +0100, Roberto De Ioris wrote: >> >>> Hi, the (tiny) attached patch enable support for new websockets >>> handling >>> when the uwsgi protocol is used instead of HTTP. >>> >>> I have tested it with various websocket libraries and with the api >>> available in uWSGI 1.9. >>> >>> From 1.9 sources (with nginx pointing to uwsgi port 3031): >>> >>> ./uwsgi -s :3031 -w tests.websockets_echo --gevent 10 >>> >>> >>> no additional configuration is needed for nginx >> >> Should we also do the same for SCGI? >> >> I personally think it is more or less the same for all CGI-based >> protocols, and the only problematic one is FastCGI, which probably >> still needs wrapping within FCGI_STDIN/FCGI_STDOUT records instead >> of real connection upgrade. >> >> > > AFAIK scgi body management works in the same way as the uwsgi one, so the > patch should be usable there too
Ok, i can confirm the same patch applied to the SCGI module in the same position works (at least with uWSGI 1.9 in SCGI mode) ./uwsgi --scgi-nph-socket :3031 -w tests.websockets_echo --gevent 10 remember to add scgi_param PATH_INFO $document_uri; to the nginx config to make it work -- Roberto De Ioris http://unbit.it _______________________________________________ nginx mailing list [email protected] http://mailman.nginx.org/mailman/listinfo/nginx
