-
-
Notifications
You must be signed in to change notification settings - Fork 201
Invalid Host/Origin header errors showing up in the JS console #488
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
Comments
Try to run
It should help you to resolve the problem |
Hi, @Quberik From what I read on the Since Encore already asks for Using it in combination with This issue doesn't seem to be one of those situations and can most likely be solved by doing something like |
It's a workaround, not a solution. The solution is to upgrade webpack-dev-server to 3.1.14. The bug is already fixed there: webpack/webpack-dev-server#1608 |
Closing this one since it shouldn't be an issue anymore. |
I use Webpack Encore to build assets for my non-Symfony app. Let's say that the app root URL is
http://my-app.dev
.My app has a parser for the
manifest.json
file so it's able to load assets fromhttp://my-app.dev/dist/
or fromhttp://127.0.0.1:8080/
- depending on the dev/production mode.The problem is that if the assets are server from Webpack dev server URL (
http://127.0.0.1:8080/
) thenInvalid Host/Origin header
errors keep on showing up in the JS console.The errors are caused by Webpack dev server. Here's the bug report.
The text was updated successfully, but these errors were encountered: