Skip to content
This repository has been archived by the owner on Sep 26, 2023. It is now read-only.

Don't use HTTP(s) scheme when specifying a lightwalletd server #217

Open
AArnott opened this issue Dec 18, 2022 · 0 comments
Open

Don't use HTTP(s) scheme when specifying a lightwalletd server #217

AArnott opened this issue Dec 18, 2022 · 0 comments

Comments

@AArnott
Copy link

AArnott commented Dec 18, 2022

I'm not certain of this, but it certainly appears that the lightwalletd protocol used between the lite wallet and server is not in fact HTTP at all. If that's the case, we should not be representing the built-in lightwalletd servers or accepting custom ones as user input with a HTTP or HTTP scheme in the front as that's extremely misleading. A simple host name and port number (and a checkbox indicating whether TLS is in use perhaps) would suffice if no scheme has been defined for it.

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

No branches or pull requests

1 participant