Headless Chromium ping WebSocket support

[Dario Kondratiuk]

I'm having a few issues trying to keep my WebSocket connection alive in Puppeteer-Sharp.

I'm opening a headless browser instance with these arguments:

--disable-background-networking

--disable-background-timer-throttling

--disable-client-side-phishing-detection

--disable-default-apps

--disable-extensions

--disable-hang-monitor

--disable-popup-blocking

--disable-prompt-on-repost

--disable-sync

--disable-translate

--metrics-recording-only

--no-first-run

--remote-debugging-port=0

--safebrowsing-disable-auto-update

--enable-automation

--password-store=basic

--use-mock-keychain

--user-data-dir="<somefolder>" 

--headless

--disable-gpu 

--hide-scrollbars

--mute-audio

When the WebSocket client sends a ping message to chromium, it closes the connection. I opened Fiddler I can see that after the Ping the connection closes.

Any idea what might be happening here?

I tested it using revision 574897

Thanks

Dario

[Eric Seckler]

+headless-dev

--
--
Chromium Discussion mailing list: chromium...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-discuss

[Adam Rice]

Yes, the server implementation is non-compliant and doesn't support ping:

https://cs.chromium.org/chromium/src/net/server/web_socket_encoder.cc?type=cs&q=file:web_socket_encoder.cc+kOpCodePing&g=0&l=87

Could you file an issue at crbug.com?

[Dario Kondratiuk]

Done https://bugs.chromium.org/p/chromium/issues/detail?id=865002

Thanks!