-
Notifications
You must be signed in to change notification settings - Fork 176
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
WS to HTTP redirection doesn't seem to be handle correctly #638
Comments
Thanks for reviewing this @niklasad1 If |
Ok got it. Cargo file should specify it like |
The redirection is still an issue but I don't think there is anything we can do besides print a better error message in the ws client.
good catch, it's a bug the ws-client crate should expose that feature but you can solve it like that too :) |
@paulormart
please open an issue in
jsonrpsee
but the issue is that you got a HTTP redirection there... to a HTTP endpointThus, meanwhile use
wss://rpc.polkadot.io:443
if that's alright for you.Originally posted by @niklasad1 in paritytech/subxt#384 (comment)
The text was updated successfully, but these errors were encountered: