40c0f03153
When creating the http server, we need to provide a TLS configuration. After a config reload, the new TLS config would not be reflected. We had the same issue with Websocket and was fixed with the use of tls.Config.GetConfigForClient API, which makes the TLS handshake to ask for a TLS config. That fix for websocket was simply not applied to the HTTPs monitoring case. I have also fixed some flappers due to the use of localhost instead of 127.0.0.1 (connections possibly would resolve to some IPv6 address that the server would not accept, etc..) Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
NATS is a simple, secure and performant communications system for digital systems, services and devices. NATS is part of the Cloud Native Computing Foundation (CNCF). NATS has over 40 client language implementations, and its server can run on-premise, in the cloud, at the edge, and even on a Raspberry Pi. NATS can secure and simplify design and operation of modern distributed systems.
Documentation
- Official documentation
- FAQ
- Watch a video overview of NATS to learn more about its origin story and design philosophy.
Contact
- Twitter: Follow us on Twitter!
- Google Groups: Where you can ask questions
- Slack: Click here to join. You can ask question to our maintainers and to the rich and active community.
Contributing
If you are interested in contributing to NATS, read about our...
Security
Security Audit
A third party security audit was performed by Cure53, you can see the full report here.
Reporting Security Vulnerabilities
If you've found a vulnerability or a potential vulnerability in the NATS server, please let us know at nats-security.
License
Unless otherwise noted, the NATS source files are distributed under the Apache Version 2.0 license found in the LICENSE file.