-
Notifications
You must be signed in to change notification settings - Fork 259
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
Not working with HTTP/1.0, f.e. when proxied #303
Comments
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? |
Oh, is that https://www.quicknode.com/chains/btc? Interesting. So they use some HTTP proxy probably that is using HTTP/1.0. |
So, how can I set compatibility with HTTP/1.0? |
Same issue here |
Same issue |
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. |
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. |
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?
The text was updated successfully, but these errors were encountered: