Getting 400: Bad request connection error

[AndrewJDR]

Hello,

I tried the subscribe_to_markets.js example, but it returns a 400 Bad request error from bittrex.

To repro:

• Add some error and disconnection handlers to the subscribe_to_markets.js file like so:

    client.on('terminated', function(data){                                                                                                                                                                                                  
      console.error("signalr client terminated, error data:", data);                                                                                                                                                                         
      throw new Error("signalr client terminated, error data:" + data);                                                                                                                                                                      
    });                                                                                                                                                                                                                                      
  
    client.on('disconnected', function(data){                                                                                                                                                                                                
      console.error("signalr client disconnected, error data:", data);                                                                                                                                                                       
      throw new Error("signalr client disconnected, error data:" + data);                                                                                                                                                                    
    });                                                                                                                                                                                                                                      
  
    client.on('connectionError', function(data){                                                                                                                                                                                             
      console.error("signalr client got connection error, error data:", data);                                                                                                                                                               
      throw new Error("signalr client got connection error, error data:" + data);                                                                                                                                                            
    });                                                          

• Run node subscribe_to_markets.js. Observe the 400 error:

  === Subscribing to 'USDT-BTC' pair
  connErr { step: 'start',
  attempts: 1,
  error: 
  { origin: 'remote',
   error: { code: 400, message: 'Bad Request' } } }

[AndrewJDR]

This fixed it for me:

diff --git a/lib/connection.js b/lib/connection.js
index 0c8b306..8791704 100644
--- a/lib/connection.js
+++ b/lib/connection.js
@@ -622,7 +622,7 @@ _start(connection, retryCount)
              url:util.format('%s/start', BASE_HTTPS_URL),
              qs:{
                  clientProtocol:CLIENT_PROTOCOL_VERSION,
-                 transport:'serverSentEvents',
+                 transport:'webSockets',
                  connectionToken:connection.ConnectionToken,
                  connectionData:JSON.stringify(HUBS)
              }

[aloysius-pgast]

Hi. Thanks for noticing this. Bittrex did some changes yesterday which cause start step to fail when using this transport. I'll publish a new npm soon

[aloysius-pgast]

Fixed in version 1.0.3 of npm package. Tickers subscriptions should also work again (a new call to method SubscribeToSummaryDeltas was needed after the changes they did yesterday)

[AndrewJDR]

@aloysius-pgast Thanks!

Just curious, do you happen to know know if bittrex issued any kind of public warning about this change before they did it?

[aloysius-pgast]

The only information they provided was on their Slack, from what I saw in issue https://github.com/dparlevliet/node.bittrex.api/issues/67