Debug Node: move ws endpoint to not clash with activation endpoints
See original GitHub issueThe Debug node uses /debug
as the endpoint for its WebSocket connection.
It also uses /debug/12345/[enable|disable]
to toggle the activate state of a debug node.
Having the websocket endpoint beneath the activation endpoints is not ideal, particular when you need to set up a websocket proxy (see discussion in #58 )
We should move the websocket endpoint to /debug/ws
to separate it out.
Issue Analytics
- State:
- Created 10 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
How To Debug Node.js with the Built-In Debugger and ...
js debugger on a program, we include inspect before the file name. In your terminal, run the node command with this debugger option...
Read more >Running and debugging Node.js | WebStorm Documentation
WebStorm helps you run and debug your Node.js applications. You can debug applications that are started from WebStorm as well as attach to ......
Read more >config | npm Docs
Any environment configurations that are not given a value will be given the value of true . Config values are case-insensitive, so NPM_CONFIG_FOO=bar...
Read more >Understanding and Troubleshooting HSRP Problems ... - Cisco
This state indicates that HSRP does not run. This state is entered through a configuration change or when an interface first becomes available....
Read more >43 OSB-75050 to OSB-2032402 - Oracle Help Center
OSB-380008: Provider with ID {0} does not support proxy service endpoints ... OSB-381404: One or more endpoint URLs in this WS transport business...
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
And the equivalent for nginx proxy_set_header Request_method $request_method; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection “upgrade”; proxy_set_header Host $http_host; proxy_set_header X-Real-IP $remote_addr; proxy_pass http://127.0.0.1:50000;
Working with the following updated Apache configuration, thanks: