-
Notifications
You must be signed in to change notification settings - Fork 71
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
Accept plain old http[s] scheme #12
Comments
Agreed. The upgrade from http to ws would be useful in many cases. Connecting to an http server with Attempting to use |
brian-brazil
added a commit
to brian-brazil/ws
that referenced
this issue
Dec 22, 2019
Fixes hashrocket#12 Signed-off-by: Brian Brazil <[email protected]>
brian-brazil
added a commit
to brian-brazil/ws
that referenced
this issue
Dec 22, 2019
Fixes hashrocket#12 Signed-off-by: Brian Brazil <[email protected]>
brian-brazil
added a commit
to brian-brazil/ws
that referenced
this issue
Dec 22, 2019
Fixes hashrocket#12 Also picked up a few unrelated gofmt changes. Signed-off-by: Brian Brazil <[email protected]>
brian-brazil
added a commit
to brian-brazil/ws
that referenced
this issue
Dec 22, 2019
Fixes hashrocket#12 Also picked up a few unrelated gofmt changes. Signed-off-by: Brian Brazil <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please let users input WebSocket URL's as
http
/https
, since that's how WebSocket addresses are actually served and used.The text was updated successfully, but these errors were encountered: