Fixed bug causing wrong application to be called for websocket requests

Issue #56 updated in noppo/gevent-websocket

Jeffrey Gelens ·

Test cases are passing as "Non-strict"

Issue #43 updated in noppo/gevent-websocket

Jeffrey Gelens ·

Exceptions thrown on client disconnect

Issue #51 updated in noppo/gevent-websocket

Jeffrey Gelens ·

Pyramid support and example

Issue #62 updated in noppo/gevent-websocket

Jeffrey Gelens ·

The socket.timeout exception is not handled

Issue #59 updated in noppo/gevent-websocket

Jeffrey Gelens ·

WAMP v2 support?

Issue #57 updated in noppo/gevent-websocket

Jeffrey Gelens ·

sub-protocol negotiation function should also be passed request headers as argument

Issue #61 updated in noppo/gevent-websocket

Jeffrey Gelens ·

How to correctly manage WebSocketError: Socket is dead ?

Issue #78 updated in noppo/gevent-websocket

Jeffrey Gelens ·

socket.receive always returns None

Issue #77 updated in noppo/gevent-websocket

Jeffrey Gelens ·

Would a non blocking receive make sense?

Issue #75 updated in noppo/gevent-websocket

Jeffrey Gelens ·

Exception: No apps defined

Issue #73 updated in noppo/gevent-websocket

Jeffrey Gelens ·

WebSocket.close() keeping file descriptors in CLOSE_WAIT

Issue #69 updated in noppo/gevent-websocket

Jeffrey Gelens ·

In PyPy 4.0 and gevent connections are reset

Issue #70 updated in noppo/gevent-websocket

Jeffrey Gelens ·

Adding custom headers

Issue #65 updated in noppo/gevent-websocket

Jeffrey Gelens ·

single websocket frame maximum size limit

Issue #64 updated in noppo/gevent-websocket

Jeffrey Gelens ·

Non Blocking ws.receive

Issue #63 updated in noppo/gevent-websocket

Jeffrey Gelens ·