Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
WebSocket should default to strict receive #543
The two methods
I think the reason to keep the default non-strict was that browsers didn't even properly implement the binary message type at the time WebSocket support was implemented and also the standard still wasn't finished. It would be interesting to see how the latest versions of each browser vendor behave today. But considering that the RFC is now finished and most browsers should behave correctly, I agree that it makes more sense to have a strict default.