-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
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
webpack: Disable host check for webpack-dev-server. #9205
Conversation
Ahh, OK, this is the issue that you thought was expose-loader being broken. Makes sense. I think for security reasons, we don't want to disable this unconditionally; instead, we should disable this only in the remote dev environment case (effectively, when See webpack/webpack-dev-server#887 for details on the security issue. |
Yeah, we can pass disable the option only when the the interface flag is |
Right, but someone could open a connection directly to the webpack port of 9994, not going through |
We can also pass in a list of domains to whitelist ie |
I'm less excited about a domain whitelist than just having this setting be controlled by an option passed from |
Webpack dev server by default does host checking for requests. so in dev enviorment if the the request came for zulipdev.com it would not send js files which caused dev envoirment to not work.
@timabbott i updated this PR so that the This is flag is flipped on if |
Yes, we do. I think the right solution is to make the option conditional on the final value of |
This works for me, but I think we also need to let people who have droplets confirm this. |
Great; can you post in the original thread with @shubhamdhama that inspired this PR to make sure other folks test this? |
Webpack dev server by default does host checking for requests. so
in dev environment, if the request came for zulipdev.com it would not
send js files which caused dev environment to not work.