Closed mikkokotila closed 2 years ago
Websocket is not like http, for binance just has not implemented a 404 for path not found. This is an expected behavior.
One can check this behavior by connect to wss://stream.binance.com:9443/ws/nonsense_path
.
For users, it should be safe to use all the enums defined in this SDK instead of string or numeric literals.
Thanks for clarifying, I anticipated that this was due to the way in which Binance handles it (well in this case doesn't handle it).
Describe the bug If the
interval
argument is set wrong (e.g.1s
) then everything seems to run fine, but there is no data coming in.To Reproduce
Expected behavior Should throw an exception/error instead of failing silently.
Environment (please complete the following information):