WebSocket and host-rules Switch
jhleath opened this issue · 0 comments
I am grateful for you adding support for the --host-rules
command line switch; however, the addition of this tag seems to have introduced errors involving the resolution of websockets (ws://
) domains.
It appears as though when the host rules switch is active for a domain, websockets requests to that domain never complete (they stay pending
forever, without contacting the server). I have concluded that they cannot successfully resolve the name.
I have experimented with Atom-Shell and Chrome proper, and Chrome will correctly handle the websockets request with the host-rules
flag, while Atom-Shell will only load the websocket if it doesn't include the host-rules
url (i.e. switching to xip.io). Thanks for all your help!