You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 12, 2024. It is now read-only.
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!
The text was updated successfully, but these errors were encountered:
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 thehost-rules
url (i.e. switching to xip.io). Thanks for all your help!The text was updated successfully, but these errors were encountered: