Skip to content

Cannot understand frame header exception when receiving messages from Javascript #139

New issue

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

Open
ahychu84 opened this issue Aug 30, 2019 · 5 comments

Comments

@ahychu84
Copy link

ahychu84 commented Aug 30, 2019

This exception is getting thrown from WebSocketConnectionRfc6455 when trying to parse the header of a message that is being sent from a wss connection from javascript. The code associated is super simple and all I'm sending is an string which is in the following format: "AUTHENTICATE:{token}". I have had this app running with a very old version of this websocketlistener and this only happened after upgrading. I have tested through IE, Edge and Chrome and all yield the same exception. Any help would be appreciated.

Upon further research, this issue seems to only be an issue when using wss to connect and sending a message after the connection is made. If wss works if I'm just receiving data from the server

@vtortola
Copy link
Owner

vtortola commented Sep 2, 2019

Hi,

That's odd. Have you tried to create a small prof of concept and narrow down the problem?

@ahychu84
Copy link
Author

ahychu84 commented Sep 3, 2019

yep I found it weird too. I tried running this in dotnet and mono and they both yield the same error. From what I'm seeing the error gets thrown in the WebSocketListener class. I'm gonna try using another websocket lib to test to see if I receive the same error

I've determined this bug was introduced after version 2.2.2

@vtortola
Copy link
Owner

vtortola commented Sep 4, 2019

I will try to put together a small repro project.

@ahychu84
Copy link
Author

Our in house environment is all linux (CentOS 7) so I have tested this using mono and dotnet

@ahychu84
Copy link
Author

@vtortola any luck ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants