-
Notifications
You must be signed in to change notification settings - Fork 5
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
use websocket branch that supports tls proxy #20
Conversation
🎉 Thanks for opening this pull request! We really appreciate contributors like you! 🙌 |
/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
|
/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
|
/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
|
/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
|
/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
|
/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
|
/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
|
/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
|
/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
|
/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
|
not needed |
Description
I forked the gorilla/websocket repo, and made changes to support use with an https proxy.
This PR uses that fork.
https://github.com/philipatl/websocket/tree/tls-proxy
gorilla/websocket#740
Motivation and Context
It is needed for enforcer to proxy websocket connections.
See CNS-3317
How Has This Been Tested?
Verified that enforcer correctly proxies websocket connections, using an https proxy.
Integration and functional tests of enforcer are in the works.
Types of changes
Checklist