Andy Green 3a31c47fcd ws: setting default protocol index to an illegal index disables default ws binding ... On lwsws, incoming ws connections to the default vhost are not rejected by the dummy protocol handler and not really serviced either, leading to bots connecting to it to get immortal, idle ws connections with no timeout (since it's an established ws connection). Rejecting these connections by default by adding a handler for ESTABLISHED in the dummy handler will solve it nicely, but it will break an unknown number of dumb. protocol-less user implementations that rely on this behaviour by using break; from their own ESTABLISHED handler and calling through to the currently NOP dummy handler one. Add support to assertively disable the default protocol index used for subprotocol-less ws connections instead.		2019-03-10 08:02:02 +08:00
..
ext	Subject: [PATCH] Fix control messages are inflated	2019-01-13 07:32:11 +08:00
client-parser-ws.c	clean: general whitespace cleanup	2018-11-23 08:47:56 +08:00
client-ws.c	clean: general whitespace cleanup	2018-11-23 08:47:56 +08:00
ops-ws.c	role: raw-proxy	2018-12-01 11:05:59 +08:00
private.h	refactor: core code in lib/core and private-libwebsockets.h to core/private.h	2018-05-03 10:49:36 +08:00
server-ws.c	ws: setting default protocol index to an illegal index disables default ws binding	2019-03-10 08:02:02 +08:00