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 Apr 3, 2023. It is now read-only.
In the docs you mention that HTTP is disabled for security reasons, which makes sense for most users/situations, but there are other cases where you may want to send via HTTP anyway, such as sending slates between multiple clients on a local machine, on trusted network, via a VPN, etc.
Strictly enforcing HTTPS is burdensome for people who want to implement their own network layer security (or don't care because they're just testing).
I understand the need to enforce good defaults, but it seems overkill to completely disable it when there are legit reasons to use HTTP. Maybe enable it if a flag is passed?
In the docs you mention that HTTP is disabled for security reasons, which makes sense for most users/situations, but there are other cases where you may want to send via HTTP anyway, such as sending slates between multiple clients on a local machine, on trusted network, via a VPN, etc.
Strictly enforcing HTTPS is burdensome for people who want to implement their own network layer security (or don't care because they're just testing).
I understand the need to enforce good defaults, but it seems overkill to completely disable it when there are legit reasons to use HTTP. Maybe enable it if a flag is passed?
mimblewimble/grin-wallet#66
The text was updated successfully, but these errors were encountered: