Skip to content
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

WiFiServer::close() does not close properly #1431

Closed
mytrain opened this issue Jan 15, 2016 · 3 comments
Closed

WiFiServer::close() does not close properly #1431

mytrain opened this issue Jan 15, 2016 · 3 comments

Comments

@mytrain
Copy link

mytrain commented Jan 15, 2016

When closing a tcp server connection with WiFiServer::close() then reopening it later with WiFiServer::begin() the tcp_bind failed with error code -13.

This is occuring only if some client connections were style alive when server was close.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@nouser2013
Copy link
Contributor

Close the connections individually on each client object as workaround for the time being, if you want to shutdown the server.

@mytrain
Copy link
Author

mytrain commented Jan 20, 2016

Unfortunately I'm not owner of client application (websocket).
In fact when client is:
-chrome on IOS via SAP it's closing correctly
-chrome on Windows 10 via STA it's NOT closing correctly

I'll run extra test Windows on SAP and IOS on STA to detect if issue is due to client of STA engine of ESP.

Keep in touch

@igrr
Copy link
Member

igrr commented Jun 13, 2016

Fixed in #2140

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

No branches or pull requests

3 participants