WebSocket does not work over SPDY proxy on HTTP/2 enabled site
Reported by
ser...@homenkow.ru,
Aug 12 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3183.0 Safari/537.36 Example URL: https://websocket-http20.xyz/ Steps to reproduce the problem: 1. Open https://websocket-http20.xyz/ w/o proxy. 2. Set SPDY proxy: “HTTPS websocket-spdy-proxy.xyz:64054” in SwitchyOmega extension or use ZenMate extension. 3. Re-check https://websocket-http20.xyz/ w proxy. What is the expected behavior? Check https://websocket-http20.xyz/ and https://websocket-http11.xyz/ in Chrome and Firefox with HTTPS “SPDY proxy”. Use “HTTPS websocket-spdy-proxy.xyz:64054” in SwitchyOmega extension in Chrome or use http://websocket-spdy-proxy.xyz/wpad.pac in Firefox. Firefox opens secondary HTTP/1.1 connection over SPDY proxy for WebSocket. Chrome version 60.0.3112.90 and 62.0.3183.0 rejects connection. What went wrong? A WebSocket over SPDY proxy on HTTP/2 enabled site returns error “VM185:161 WebSocket connection to 'wss://websocket-http20.xyz/echo' failed: ”Error in connection establishment: net::ERR_NOT_IMPLEMENTED”. Did this work before? No Chrome version: 62.0.3183.0 Channel: canary OS Version: OS X 10.12.6 Flash Version: Shockwave Flash 27.0 r0
,
Aug 14 2017
,
Sep 22 2017
Sorry for the delay. Could you provide a NetLog? https://dev.chromium.org/for-testers/providing-network-details
,
Oct 23 2017
No feedback was received in the last 30 days from reporter "sergey@homenkow.ru", so archiving this. Please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 12 2017
yhirano@chromium.org Please reopen |
||||
►
Sign in to add a comment |
||||
Comment 1 by jmukthavaram@chromium.org
, Aug 14 2017