proxyTable doesn't work for websocket connections
See original GitHub issueWhile regular http connections works fine, ws connection still proxies to target
options:
proxyTable: {
'dev:2992' : 'http://localhost:3000',
}
version: 0.9.0
Issue Analytics
- State:
- Created 8 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Node http proxy with proxytable and websockets
But it doesn't seem to work. A quick check to see whether websockets work shows I get Unexpected response code: 400 from Chrome...
Read more >Websocket connection behind HTTP proxy does not work
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:71.0) Gecko/20100101 Firefox/71.0. Steps to reproduce: I'm trying to use a website that uses ...
Read more >DevServer - webpack
This option allows specifying URL to web socket server (useful when you're proxying dev server and client script does not always know where...
Read more >ionic/node_modules/http-proxy/CHANGELOG.md ... - GitLab
Provide a "proxyReq" event also for websocket connections. a05fc2d ... [fix] ensure path works on windows because path.join doesnt like URLs ed73f06 ...
Read more >http-proxy - npm
is invoked on the object, this does not create a webserver. ... open : This event is emitted once the proxy websocket was...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@chimurai
Awesome. Thanks for reporting and testing! 👍
Going publish the final version after some more testing.