-
Notifications
You must be signed in to change notification settings - Fork 51
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
getInitialHeaders and getInitialQuery returns null #29
Comments
This issue has been noted. I'll notify here when I release a version with the fix. |
@trinopoty would you please tell us when this fix will be available . |
I had a look at it and this issue doesn't seem to effect any public facing api. Since the socket is already fully initialized when it's reported via the |
Ok. I figured out the issue. Expect to see a new version on maven in a few hours. |
@trinopoty many thanks |
When an
EngineIoSocket
gets created from a web request, The socket gets initialize before the transport runsonRequest
. Which means themInitialQuery
andmInitialHeaders
are null are they get pulled from the transport which doesn't have those values yetThe text was updated successfully, but these errors were encountered: