-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
gulp proxy does not work with websockets #1639
Comments
could these be related? |
For PR #1508, I added /websocket/tracker to the URL to be proxied by gulp but this worked only for http not ws. |
@gmarziou did you check after latest release? |
browser-sync is not a big win for me at least on Windows, sinc it was introduced I cannot just do server-less development I must run mvn spring-boot:run even if I don't use the backend. It also locks files. I have started to use gulp on a mobile project because it's the default build tool for Ionic framework and frankly I would not mind switching to gulp also in JHipster if gulp was not using brower sync. |
It should be tested again since PR #1847 because it upgraded gulp proxy. |
For me this doesn't work with BrowserSync, with Grunt, and I even documented here. Shouldn't we add this to the documentation and close this? If BrowserSync doesn't support WebSockets, we can't do much about this. |
Looks like it has been fixed in BS 2.8.1 BrowserSync/browser-sync#625 |
Nice find @gmarziou Last night I had found BrowserSync/browser-sync#611 which seemed to suggest it had worked with BrowserSync 2.6.0 and 2.7.1. Glad they have fixed it again. |
And the issue still exists with Grunt, so if you solve this with Gulp.js that would be a huge advantage for using Gulp.js!! cc @PeterEltgroth @amr |
updated to 2.9.1 and tested on MacOSX with Safari, FireFox, and Chrome Fix jhipster#1639
First time, I use gulp and websockets and I got this error in Firefox console:
So it would seem that gulp proxy cannot proxy ws protocol or maybe there is something to configure, I did not dig further.
The text was updated successfully, but these errors were encountered: