[chromium-discuss] Headless Chromium ping WebSocket support

Discussion:

Dario Kondratiuk

2018-07-15 00:17:17 UTC

I'm having a few issues trying to keep my WebSocket connection alive in
Puppeteer-Sharp <https://github.com/kblok/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.

<Loading Image...

>

Any idea what might be happening here?

I tested it using revision 574897

Thanks

Dario

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

---
You received this message because you are subscribed to the Google Groups "Chromium-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-discuss+***@chromium.org.

Eric Seckler

2018-07-16 06:19:30 UTC

Permalink

+headless-dev

Post by Dario Kondratiuk
I'm having a few issues trying to keep my WebSocket connection alive in
Puppeteer-Sharp <https://github.com/kblok/puppeteer-sharp/>.
--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.
<https://lh3.googleusercontent.com/-HN0dazl87uA/W0qQHGTspLI/AAAAAAAAcwQ/1ImEC4vJBnU-z-XiOw1oG3mt-uodoPXmgCLcBGAs/s1600/Screen%2BShot%2B2018-07-14%2Bat%2B8.59.50%2BPM.png>
Any idea what might be happening here?
I tested it using revision 574897
Thanks
Dario
--
--
http://groups.google.com/a/chromium.org/group/chromium-discuss

Adam Rice

2018-07-18 02:33:45 UTC

Permalink

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?

Post by Eric Seckler
+headless-dev

--
http://groups.google.com/a/chromium.org/group/chromium-discuss

Dario Kondratiuk

2018-07-18 13:39:32 UTC

Permalink

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

Thanks!

Post by Adam Rice
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?

Post by Eric Seckler
+headless-dev

Post by Dario Kondratiuk
I'm having a few issues trying to keep my WebSocket connection alive in
Puppeteer-Sharp <https://github.com/kblok/puppeteer-sharp/>.
--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.
<https://lh3.googleusercontent.com/-HN0dazl87uA/W0qQHGTspLI/AAAAAAAAcwQ/1ImEC4vJBnU-z-XiOw1oG3mt-uodoPXmgCLcBGAs/s1600/Screen%2BShot%2B2018-07-14%2Bat%2B8.59.50%2BPM.png>
Any idea what might be happening here?
I tested it using revision 574897
Thanks
Dario
--
--
http://groups.google.com/a/chromium.org/group/chromium-discuss
--

--
http://groups.google.com/a/chromium.org/group/chromium-discuss