Not working with HTTP/1.0, f.e. when proxied

[jitash]

hi, i have this error when use quick-node in rust: error: JSON-RPC error: transport error: HTTP response started with HTTP/1.0 ; expected HTTP/1.1 .
anyone can help?

[stevenroose]

Hmm, that's interesting, I don't actually know why we enforce HTTP/1.1 being used..

But what is "quick-node"? You're not using bitcoin core?

[stevenroose]

Oh, is that https://www.quicknode.com/chains/btc? Interesting. So they use some HTTP proxy probably that is using HTTP/1.0.

[jitash]

So, how can I set compatibility with HTTP/1.0?

[gdnathan]

Same issue here

[chinyuchan]

Same issue

[TheBlueMatt]

Uhhh, HTTP/1.1 is from 1997, this is a bug in whatever software is requiring almost 30 year old protocols, not a bug in this library.

[apoelstra]

FWIW, though, it should be fixed upstream by the minreq backend. We had an issue here #259 (see also #276 and #330) which appear to be stalled out. But in principle it should be easy for this library to update their jsonrpc dep.

[scolear]

Same issue on v0.19.

Not sure why quicknode is using HTTP/1.0, alas we can't use it. We are trying to use it as a backup provider for when our bitcoin node is under maintenance. Instead we will spin up another one for the time being.

[adamflush]

You have this backwards, bitcoincore-rpc is using HTTP 1.0 and QuickNode enforces HTTP 1.1+.

Is there a way to force use of a new version of jsonrpc?

[apoelstra]

jsonrpc has never in its history used HTTP 1.0.

You might be able to force a different version using [patch] lines in your Cargo.toml.

And this project is unmaintained.

[adamflush]

rust-bitcoincore-rpc is using HTTP 1.0. What is the fix for that?

It had appeared you had blamed it on a dependency above, but then I misunderstand. How does rust-bitcoincore-rpc get fixed to use HTTP 1.1 or later?

[adamflush]

For what it's worth, just use an HTTP library like reqwest against QuickNode (or other SaSS node providers) and forget about this library. There are so many methods not supported by Node SaSS and often additional and alternative methods not supported by bitcoin RPC.

Example, QuickNode and NowNodes do not support scantxoutset but do support bb_getUTXOs (BTC Book APIs).

[apoelstra]

rust-bitcoincore-rpc is using HTTP 1.0. What is the fix for that?

It is not and never has been.

For what it's worth, just use an HTTP library like reqwest against QuickNode (or other SaSS node providers) and forget about this library.

Who are you talking to?

[adamflush]

Thanks, I stand corrected, the HTTP 1.0 error is just obscuring an HTTP 400 response from QuickNode and the request was indeed HTTP 1.1.

To individuals that may want to use rust-bitcoincore-rpc against QuickNode, you cannot, just use an HTTPS library.