-
Notifications
You must be signed in to change notification settings - Fork 84
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
websocket-client recognized as 0.0.0.0 during first connect #304
Comments
I know about it, but due very little time available for free software at the moment I haven't had the time to look at this. I will eventually get at it, but I would also accept any merge requests for this issue ;). |
I just want to kindly ask if you please could find the time to solve these 2 issues:
Thank you very much! Thomas |
Can you provide some example code to reproduce the 0.0.0.0 issue @Thomas12 ? |
Yes, sure, see below:
(Tried putting the code in `` for nicer layout, but that's not recognized). Server: local socks = {} local WSExHandler = class("WSExHandler", turbo.websocket.WebSocketHandler) function WSExHandler:open(msg) function WSExHandler:on_close() function WSExHandler:on_error(msg) AppHandler = class("AppHandler", turbo.web.RequestHandler) function AppHandler:get(url) turbo.web.Application({{"^/ws$", WSExHandler}, {"^/$", AppHandler} }):listen(80) j=0 for _, sock in pairs(socks) do function get() io_loop:add_callback(get) function turbo.log.error(str) io_loop:start() Client: _G.TURBO_SSL = true -- SSL must be enabled for WebSocket support! turbo.ioloop.instance():add_callback(function() |
When a websocket client connects the first time to a turbo websocket server, the server recognizes the client IP as 0.0.0.0.
I posted this problem in issue #289, but I think it got overlooked as it does not match the original topic and is a separate issue.
The text was updated successfully, but these errors were encountered: