-
-
Notifications
You must be signed in to change notification settings - Fork 27k
Fixed not working websocket proxy (fix: #5280) #5841
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
Conversation
Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need the corporate CLA signed. If you have received this in error or have any questions, please contact us at [email protected]. Thanks! |
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks! |
This fix worked for me, would be great to see this get adopted. |
Can you update the comment to explain what |
We probably shouldn't proxy all upgrade requests, right? |
Yes good catch, I've reworked the logic, maybe the What do you think about it? |
cc @Timer any updates? |
This pull request has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs. |
cc @iansu |
This pull request has been automatically closed because it has not had any recent activity. If you have a question or comment, please open a new issue. Thank you for your contribution! |
Hello
this PR fixes that websockets, e.g. via Socket.io won't be proxied through the HTTP proxy.
For more information check out issue: #5280 there are also some users who tested it successfully.
Best regards
Max.