We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi,
Is it normal that both text and binary opcode for websocket has the same value?
#define U_WEBSOCKET_OPCODE_TEXT 0x01 #define U_WEBSOCKET_OPCODE_BINARY 0x01
Best regards,
Michael
The text was updated successfully, but these errors were encountered:
Hello @mmardinian ,
No it's not normal, U_WEBSOCKET_OPCODE_BINARY sould be 0x02 and not 0x01, thanks for pointing out.
0x02
0x01
I'll fix this ASAP in the master branch.
Sorry, something went wrong.
Thank you
fix websocket opcode for binary #52
711d42f
The opcode bug has been fixed in the master branch and the new release 2.3.7.
I've made more tests with binary messages and it seems to work fine, but if you have other concerns about it, don't hesitate!
No branches or pull requests
Hi,
Is it normal that both text and binary opcode for websocket has the same value?
#define U_WEBSOCKET_OPCODE_TEXT 0x01 #define U_WEBSOCKET_OPCODE_BINARY 0x01
Best regards,
Michael
The text was updated successfully, but these errors were encountered: