Conflict when webpage also uses Socket.io
See original GitHub issueBrowser-sync v0.5.7 works perfectly if I proxy the PHP server. But when using with my nodejs server from the command line (browser-sync --proxy "localhost:5000" --files "public/asset/css/*.css"
, where my NodeJS site runs under localhost:5000
), the webpage looks as following:
Issue Analytics
- State:
- Created 10 years ago
- Comments:14 (9 by maintainers)
Top Results From Across the Web
Troubleshooting connection issues | Socket.IO
You are trying to reach a plain WebSocket server; The server is not reachable; The client is not compatible with the version of...
Read more >How to fix browser-sync & socket.io conflict? - Stack Overflow
I mainly use Gulp with browser-sync inside an Aurelia CLI project, while the backend is NodeJS with Koa . The version of socket.io@1.6.0...
Read more >Web Sockets - A brief explanation | by Jacob Friesen | Medium
There is a lot of details like conflict resolution, efficiency (in ... We use Socket.io which also has server side extensions though that...
Read more >Avoiding WebSockets conflicts - Node.js Web Development
Avoiding WebSockets conflicts An error, Cannot find context with specified id undefined, can be thrown by Puppeteer. According to an issue in the...
Read more >409 Conflict - HTTP - MDN Web Docs
The HTTP 409 Conflict response status code indicates a request conflict with the current state of the target resource.
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
Submitted some pull requests from my personal account.
BrowserSync has not yet been tested to work with web-sockets.
If you disable
options.ghostMode.links
then it will work for you until this gets fixed