Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[Bug] "Invalid Host Header" using ng serve --host 0.0.0.0
See original GitHub issueDo you want to request a feature or report a bug?
Bug (cascaded from angular-cli 1.0.1 [webpack-dev-server])
Bug Report
See here: https://github.com/webpack/webpack-dev-server/issues/882
Due to a security fix in webpack, running Covalent source app via proxy results in “Invalid Host Header” printed in the browser. This affects angular-cli 1.0.1
What is the expected behavior?
Covalent source app runs normally.
What is the motivation / use case for changing the behavior?
Working on the Covalent source app for IE11 support using a windows VM for IE11/Edge. I deploy the app on my Mac using ng serve --host 0.0.0.0 to expose it the VM.
Which version of Angular and Material, and which browser and OS does this issue affect?
Affects angular-cli 1.0.1 (See here: https://github.com/angular/angular-cli/issues/6070)
Did this work in previous versions of Angular / Material?
Works in angular-cli 1.0.0
Other information
Rolling back the angular-cli version to previous version restores functionality
ng serve --host 0.0.0.0
I can put in a PR for this breaking dependency.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:10
- Comments:9 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
btw workaround for this is running:
Yeah, the latest
1.1.0-beta.1has that flag. Supposed to be for that specific case.