-
-
Notifications
You must be signed in to change notification settings - Fork 1.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
Allow http: connection to 127.0.0.1 #2302
Closed
1 of 2 tasks
nougad opened this issue
Nov 3, 2019
· 1 comment
· Fixed by #2303, alfill/qr-code-scanner#6 or CollageLabs/collagelabs.org#60 · May be fixed by saurabharch/react-ecommerce#5 or raindigi/eShopOnContainers#2
Closed
1 of 2 tasks
Allow http: connection to 127.0.0.1 #2302
nougad opened this issue
Nov 3, 2019
· 1 comment
· Fixed by #2303, alfill/qr-code-scanner#6 or CollageLabs/collagelabs.org#60 · May be fixed by saurabharch/react-ecommerce#5 or raindigi/eShopOnContainers#2
Comments
nougad
added a commit
to nougad/webpack-dev-server
that referenced
this issue
Nov 5, 2019
Chrome and Firefox accept `http://`/`ws://` mixed-content connection to `127.0.0.1` even when the actual website is loaded via `https://`. Fixes webpack#2302
6 tasks
nougad
added a commit
to nougad/webpack-dev-server
that referenced
this issue
Nov 10, 2019
Chrome and Firefox accept `http://`/`ws://` mixed-content connection to `127.0.0.1` even when the actual website is loaded via `https://`. Fixes webpack#2302
nougad
added a commit
to nougad/webpack-dev-server
that referenced
this issue
Nov 25, 2019
Chrome and Firefox accept `http://`/`ws://` mixed-content connection to `127.0.0.1` even when the actual website is loaded via `https://`. Fixes webpack#2302
This was referenced Feb 22, 2020
Hi, I have a few questions about this:
Regards, |
This was referenced Mar 13, 2020
This was referenced Apr 4, 2020
This was referenced May 5, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Code
Expected Behavior
Site is loaded via
https://
, dev-server is running onhttp://127.0.0.1:3333
. I expect I can connect with Chrome and Firefox becausehttp://
should be allowed for127.0.0.1
without errors.Actual Behavior
Webpack overrides the protocol with
https:
: https://github.com/webpack/webpack-dev-server/blob/master/client-src/default/utils/createSocketUrl.js#L47-L56Which results in wrong protocol error.
For Features; What is the motivation and/or use-case for the feature?
Chrome and Firefox accept
http://
connection to127.0.0.1
even when the actual website is loaded viahttps://
:But webpack-dev-server forces
https
: https://github.com/webpack/webpack-dev-server/blob/master/client-src/default/utils/createSocketUrl.js#L47-L56I assume the check should be:
slightly related:
transportMode
withsockjs
is used this will block the request: Is it possible to allow 127.0.0.1 when accessed under secure domain? sockjs/sockjs-client#486transportMode
withws
is used it works in Chrome but FF request at least version 70: https://bugzilla.mozilla.org/show_bug.cgi?id=1376309The text was updated successfully, but these errors were encountered: