Bugfixes:

• add disableHostCheck to schema

Security fix:

This version contains a security fix, which is also breaking change if you have an insecure configuration.
We are releasing this breaking change as patch version to protect you from attacks.
Sorry if this breaks your setup, but the fix is easy.

We added a check for the correct Host header to the webpack-dev-server.
This allowed evil websites to access your assets.

The Host header of the request have to match the listening adress or the host provided in the public option.
Make sure to provide correct values here.

The response will contain a note when using an incorrect Host header.

For usage behind a Proxy or similar setups we also added a disableHostCheck option to disable this check.
Only use it when you know what you do. Not recommended.

This version also includes this security fix for webpack-dev-middleware: https://github.com/webpack/webpack-dev-middleware/releases/tag/v1.10.2

Note: This only affect the development server and middleware. webpack and built bundles are not affected.

Credits to Ed Morley from Mozilla for reporting the issue.

Bugfixes:

• Requests are not blocked when Host doesn't match listening host or public option.
• Requests to localhost or 127.0.0.1 are not blocked.

Features:

• Added disableHostCheck option to disable the host check

Security fix:

This version contains a security fix, which is also breaking change if you have an insecure configuration.
We are releasing this breaking change as patch version to protect you from attacks.
Sorry if this breaks your setup, but the fix is easy.

We added a check for the correct Host header to the webpack-dev-server.
This allowed evil websites to access your assets.

The Host header of the request have to match the listening adress or the host provided in the public option.
Make sure to provide correct values here.

The response will contain a note when using an incorrect Host header.

For usage behind a Proxy or similar setups we also added a disableHostCheck option to disable this check.
Only use it when you know what you do. Not recommended.

This version also includes this security fix for webpack-dev-middleware: https://github.com/webpack/webpack-dev-middleware/releases/tag/v1.10.2

Note: This only affect the development server and middleware. webpack and built bundles are not affected.

Credits to Ed Morley from Mozilla for reporting the issue.

Bugfixes:

• Requests are not blocked when Host doesn't match listening host or public option.
• Requests to localhost or 127.0.0.1 are not blocked.

Features:

• Added disableHostCheck option to disable the host check

• Properly close CLI when SIGINT or SIGTERM is called. This should fix some Docker issues (#787).
• Fix for entry not working when it was a function (#802).
• Fix for exception when using webpack-dev-server in a webworker (#813).
• Fix refresh loop that could happen on Firefox (#841).
• contentBase as an array did not work when used via CLI (#832).
• Proxy options were mutated, so this could lead to problems when re-using them (#836).

• After fixing a warning/error, the overlay was not always cleared correctly (3cb79bd).

• contentBase: false in combination with the historyApiFallback option threw an error (#791).
• Separate logic of adding entry points to the webpack config; this allows alternative implementations like the webpack grunt plugin to use this instead of copying the code (#782).
• Update SockJS dependency to fix issue with FireFox constantly refreshing the page (#762).
• Show clear error message when --open fails to open the browser (#780).
• Allow overlay option to also show compiler warnings (off by default) (#790):

overlay: {
  errors: true,
  warnings: true
}

• Add new fancy error overlay in-browser, which shows up when there are compilation errors. Disabled by default, add overlay: true to enable (#764)!
• If you use --open and options.public, the browser will now open the same URL as you have defined in public (#749).
• options.port now allows strings to be passed in, previously only integers were accepted (#766).

Probably the last release in the v1.x range:

• Backport support for webpack config as a Promise.

First webpack-dev-server 2 release

Following the webpack 2 release.
It's equal to the last RC.

If you're curious about the highlights, read this fancy Medium post.

• Allow latest webpack 2.2.0-rc.0 as peer dependency (#714).