404 error for sockjs-node when using publicPath options

[fullykubed]

Do you want to request a feature or report a bug?
Bug

What is the current behavior?

Produces a client-side 404 error when looking for http://localhost:3000/test/sockjs-node/iframe.html

Note that there is no error when not using the publicPath options

If the current behavior is a bug, please provide the steps to reproduce.

Relevant options in config file (note: using a TypeScript config format)

entry: [
        "webpack-dev-server/client?http://localhost:3000/",
        path.join(__dirname, "/client/main.tsx"),
    ],

output: {
        path: path.resolve(__dirname, 'dist'),
        filename: 'bundle.js',
        publicPath: '/test/'
  },
...
devServer: {
        contentBase: path.resolve(__dirname, '/dist/'),
        host: 'localhost',
        compress: true,
        noInfo: true,
        port: 3000,
        publicPath: '/test/',
        historyApiFallback: {index: '/test/'}
 }

What is the expected behavior?

Should not produce the error

Please mention your webpack and Operating System version.
webpack-dev-server - 2.7.0
webpack - 3.5.1
os - Ubuntu 17.04

[fullykubed]

Smacking my head because this was addressed by you all yesterday with the rollout of 2.7.1. Thanks for your hard work.