We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
设备固定ip,http服务设置此IP启动成功后,通过拔网线的方式,设备的固定ip丢失,但是http服务没有异常或停止回调,此时状态还是running状态,客户端已经没法访问此服务了。
The text was updated successfully, but these errors were encountered:
怎么才能确保 http服务实际停止与回调和runing状态保持一致,这样才能在停止后立即重新启动服务
Sorry, something went wrong.
无论是指定IP或者不指定IP,只要启动server不主动停止,其实一直是开启的,无论ip是否发生变化。服务器只是绑定该IP,如果不是该IP,则服务器无法监听连接该IP的请求,但是它还是在监听对指定IP的连接请求,我理解在技术层面这是正确的。
对于你的要求,目前框架没有这种策略,对大多数业务场景的建议是使用不指定ip的方式,这样即便IP发生变化服务也能保持正常运行,只要客户端请求的IP正确。当然,最好的方式是IP有域名的映射,客户端访问域名即可,不用关心IP的变化,根据自己的实际场景来。
No branches or pull requests
设备固定ip,http服务设置此IP启动成功后,通过拔网线的方式,设备的固定ip丢失,但是http服务没有异常或停止回调,此时状态还是running状态,客户端已经没法访问此服务了。
The text was updated successfully, but these errors were encountered: