Skip to content
New issue

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

400 BAD REQUEST when running from Node #269

Open
aronanda opened this issue Dec 1, 2018 · 2 comments
Open

400 BAD REQUEST when running from Node #269

aronanda opened this issue Dec 1, 2018 · 2 comments

Comments

@aronanda
Copy link

aronanda commented Dec 1, 2018

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' 
}
@alko89
Copy link

alko89 commented Dec 16, 2019

Just managed to finally be able to try 4.1 and got the same problem.

@Ayan-Ali
Copy link

having the same problem pls help

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants