use proxy can not hot update

[beliefgp]

webpack: 1.10.x
webpack-dev-server: 1.15.x
OSX 10.x

// webpack-dev-server/lib/Server.js code
sockServer.installHandlers(this.listeningApp, {
     prefix: '/sockjs-node'
});

this prefix is unchangeable；
when i use browser proxy，request.url include hostname, it can not work.

example： local.com:2222/sockjs-node/info.js

not use proxy,it can matched an work
request.url = /sockjs-node/info.js

use proxy ,it can not matched
request.url = local.com:2222/sockjs-node/info.js

[SpaceK33z]

So what would your proposed fix be? I'm not sure I understand what you're trying to do here.

[beliefgp]

the sockServer prefix can configurable or auto match current host

thanks。

[SpaceK33z]

Is there an easy way to reproduce this behavior? I've never seen this before.

[beliefgp]

my local environment ： chrome install SwitchyOmega , config ： http 127.0.0.1 2222

then use webpack-dev-server

[SpaceK33z]

Could you check if webpack/webpack-dev-middleware#80 works for you? The quickest way to test this would be to go to node_modules/webpack-dev-middleware/middleware.js, and copy/paste the new code.

[beliefgp]

I am sorry that not this. The same reason，but not one problem, but Sockjs on this scheme can be used。

[SpaceK33z]

And is it not possible to exclude your dev domain from the proxy? SwitchyOmega seems to have an option for this:

[beliefgp]

It is my current solution。 I just want to make it more simple

[SpaceK33z]

I think this is the way it should work, the dev server should not be proxied like that.

[beliefgp]

I agree, but it is complex （ configuration host,proxy, and exclude dev server ） when use proxy。
For new user, it is easy to forget.

Thank you anyway。

[SpaceK33z]

Yeah I agree, the configuration of dev-server can be (too) complicated. We're working on that though, with stricter validation of the configuration.