First draft at implementing websocket proxy #107
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In particular allow request with credentials which are not allowed when only "Access-Control-Allow-Origin: *" is specified. Custom response headers must be crafted for each request depending on the Origin request header. Also, enable preflight responses to Access-Control-Request-Headers.
git-subtree-dir: websocketproxy git-subtree-split: 7ed82d81a28c9ba1ed6fd1157ce714760f214c98
First implementation of a websocket proxy
Owner
|
This looks like a promising direction. Are you still hacking on it? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a first draft that implements websocket proxying. I'm not sure it works very well, but it's a first try.