-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Getting LWS_CALLBACK_CLOSED_CLIENT_HTTP all of a sudden #3107
Comments
There are nice verbose logs in lws that tell you all about what it's doing... just enable them as the examples do. |
Thank you, @lws-team for a quick response. Could you explain what does |
It means lws understands the server you're talking to overflowed the max window size possible. Some servers don't keep track well. There's a context creation info.option flag h2 means http/2. alpn is an early indication of what protocol you want to talk on tls. |
Hey guys,
I've been trying to connect to a websocket as a client for a day now. I know this sounds desperate but cold you please help me figure out what's wrong and explain what am I doing at all.
So, my goal is to connect to a certain websocket and send custom HTTP headers. Based on the minimal examples I arrived to the following code
First of all, how do I make sure it connects to
wss://myaddress.com
and nothttps://myaddress.com
. Because Chrome shows that it connects towss
.Since I couldn't find documentation except the example applications, I do not understand some parts oof this code:
callback_http
with variousreason
s. However, it always ends with LWS_CALLBACK_CLOSED_CLIENT_HTTPA typical order would be
Depending on how long I stay in the debugger (or maybe something else) I might receive
LWS_CALLBACK_CLIENT_HTTP_WRITEABLE
. No matter what I write there (or skip) the next step is p.18.I am most certainly doing something wrong but I cannot figure out what exactly.
I stripped the original code keeping only the relevant parts (the rest is logging, logging, logging...) so it might not compile but you'll still get the point.
The text was updated successfully, but these errors were encountered: