You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 26, 2023. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The text was updated successfully, but these errors were encountered: