-
Notifications
You must be signed in to change notification settings - Fork 4
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
Websockets and HTTP Upgrade #9
Comments
Currently weave supports arbitrary tcp proxying (which would work with WebSockets and anything else) but doesn't support proper routing of WebSockets! I'd be keen on supporting WebSockets though; that's something I've needed myself in a proxy and I can see how it would be useful. I had a quick read about HTTP connect and I'm less inclined towards it offhand; weave can already forward specific tcp connections, but from my readong HTTP CONNECT would allow users to connect to arbitrary endpoints through weave? In general it feels out of the scope of what weave is intended for and probably a good indicator that its time to "upgrade" to something like nginx. |
Does Weave support HTTP Upgrade? Can it forward Websockets or HTTP CONNECT to other server?
Can I emulate nginx's
proxy_pass ...; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade";
with Weave?The text was updated successfully, but these errors were encountered: