title: How can I fix these SockJS ssl errors?
body: <p>With vue-cli 3, I've got a vue app whirring away in development mode. I call npm run serve, and I see...</p>
  
  <pre><code>DONE  Compiled successfully in 431ms                                                                                                                                                                   
  16:26:43
  App running at:
  - Local:   http://localhost:8080/mobileapp/v/
  - Network: http://172.18.55.202:8080/mobileapp/v/
  </code></pre>
  
  <p>(The path <code>/mobileapp/v/</code> comes from a baseUrl config variable. The domain notilusdev.dimosoftware.com/mobileapp points to a vdir in iis, and requests to /mobileapp/v/ are reverse proxied to webpack-dev-server)</p>
  
  <p>In the browser, the app fires up no problem. Then it starts firing off requests to <code>https://172.18.55.202:8080/sockjs-node/info?t=1529072806971</code>. These requests fail, because there's no ssl on that port. I don't even want the ip as the public address of the site. How does Webpack (or sockjs) construct this url? Why does it think there's ssl on this port when it's just given me a straight http link? If it's basing the protocol on the address-bar protocol, why is it ignoring the address-bar host-name. What can I configure to get these requests to succeed?</p>
  
  <p><a href="https://i.stack.imgur.com/ws3GL.png" rel="noreferrer"><img src="https://i.stack.imgur.com/ws3GL.png" alt="enter image description here"></a></p>