-
Notifications
You must be signed in to change notification settings - Fork 263
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
JSON-RPC error: transport error: unexpected HTTP code: 400 #323
Comments
Is it an HTTPS URL? |
Yes
…On Thu, Dec 14, 2023, 2:47 PM Andrew Poelstra ***@***.***> wrote:
Is it an HTTPS URL?
—
Reply to this email directly, view it on GitHub
<#323 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD5WNRXQPNCDURZ2G6H6XH3YJL7OZAVCNFSM6AAAAABAUMPC7OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJVHA4DINZYG4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Unfortunately this library doesn't support HTTPS right now because the underlying JSONRPC library (rust-jsonrpc) has only been recently updated to support a HTTPS-supporting backend (minreq). We need to update our copy of |
@apoelstra is it something you need help with? |
Hello, do you have any updates on this ticket? It's weird that rust-bitcoincore-rpc can't work with HTTPS |
Bitcoin Core doesn't use HTTPS.. But anyway yes, now rust-jsonrpc has a minreq backend which supports HTTPS. |
I checked the code and saw that the minreq feature is activated for jsonrpc, |
It might be sufficient to add an explicit |
I keep getting this error when making RPC calls with this library.
Error:
JSON-RPC error: transport error: unexpected HTTP code: 400
PS: My RPC URL does not have a username and password. The URL contains a token for auth
The text was updated successfully, but these errors were encountered: