Closed jhen0409 closed 8 years ago
I've changed the injectpage to use http on my fork, but this causes issues when you try to inject on all URLs, no matter the protocol.
I think the best solution is to run webpack-dev-server on HTTP, and then have a HTTPS proxy (SSL termination), such that both protocols work.
@tommedema I tried using httpolyglot
and webpack-dev(hot)-middleware
to create server, it works very well. Maybe I'll release it today.
@jhen0409 would be great if you could; I spend another 4 hours on it today and I cannot get it all to work. Sometimes HTTP works, sometimes HTTPS, sometimes both, but then not WSS (but only WS, or the other way around).
@jhen0409 does it also work for websockets?
@jhen0409 any news on this?
@tommedema, I created webpack-httpolyglot-server and created this branch for that, you can try first.
Also, the webpack-hot-middleware
isn't use Websockets, it just use Server Sent Events.
Finally we use webpack-httpolyglot-server
#37, so this issue will not do.
The original
injectpage
is detect visiting GitHub and start, it will cause some problems, so I have plan to move it to thelocalhost
and GitHub page.I has three reasons:
1. Theinjectpage
include redux-devtools, it will affect developers read on GitHub.2. Thewebpack-dev-server
will no longer use https.3. Theinjectpage
E2E test run on localhost of CI build, everything will work well.