Host checking breaks multi-host proxy

[AdamMcCormick]

I think this is a feature gap caused by a bug fix so make of it what you will. With the introduction of 2.4.3 (https://github.com/webpack/webpack-dev-server/releases/tag/v2.4.3), host headers are now explicitly being checked for all calls. That seems sane, but where before I could specify several hosts to proxy calls to:

devServer: {
    ...
    proxy: {
        '/**': {
            router: {
                'local.site1.com:8080': site1.com,
                'local.site2.com:8080': site2.com,
                ...
            },
        },
    },
    ...
}

I now have to add:

devServer: {
    ...
    disableHostCheck: true,
    ...
}

Or i get an invalid host message like seen in #882. I would expect that there would be a mechanism that would let me specify more than one public path since there is a means of specifying more than one public proxy. Perhaps make public take an array of paths?

[smitpsanghavi]

I have setup a local website in IIS and requests are routed to the webpack-dev-server on localhost:3000.

I have a mult-tenant SaaS app on which each tenant resides on a subdomain.
I cannot use *.mylocalsite.com in the devserver.public key of the config.
I have to hard-code subdomain.mylocalsite.com in the config and because of this I cannot access webpack-dev-server at subdomain1.mylocalsite.com

[shellscape]

Fairly certain that #1012 and #899 resolve this issue. Please try upgrading and giving that a shot.