You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can get a transaction commit to work fine when running from the browser, but, when I run the same code in Node.js I get this 400 bad request error. I've tried with both the test server and my local server and the results are the same. Is there something that's missing from the header of the js driver? Could it somehow be a CORS issue? This is a blocker for me, I want to encapsulate the Bigchain server from the outside world by passing the transaction signatures through a custom Node API and then on to the Bigchain server.
I should mention that CREATE transactions work fine, this problem is only with TRANSFER transactions in Node.js. (TRANSFER transactions work fine in the browser)
{
message: 'HTTP Error: Requested page not reachable',
status: '400 BAD REQUEST',
requestURI: 'http://localhost:9984/api/v1/transactions?mode=commit'
}
The text was updated successfully, but these errors were encountered:
I can get a transaction commit to work fine when running from the browser, but, when I run the same code in Node.js I get this 400 bad request error. I've tried with both the test server and my local server and the results are the same. Is there something that's missing from the header of the js driver? Could it somehow be a CORS issue? This is a blocker for me, I want to encapsulate the Bigchain server from the outside world by passing the transaction signatures through a custom Node API and then on to the Bigchain server.
I should mention that CREATE transactions work fine, this problem is only with TRANSFER transactions in Node.js. (TRANSFER transactions work fine in the browser)
The text was updated successfully, but these errors were encountered: