3 commits

Author	SHA1	Message	Date
Simon Cruanes	3393c13c00	fix websocket: properly remember the offset in current frame ... not doing so means we always unmask from offset 0, which means we might use the wrong index in the mask if we do, say, `read()=3` followed by another read: the second one would start from mask[0] instead of mask[3], producing raw unfiltered garbage.	2024-04-05 13:21:54 -04:00
Simon Cruanes	dbd00259da	feat ws: a bit of cleanup, expose masking primitive	2024-04-04 15:54:55 -04:00
Simon Cruanes	78baf70126	add basic C stubs for unmasking client frames	2024-02-05 01:29:31 -05:00