[Webkit-unassigned] [Bug 233943] New: NSURLSession WebSocket does not use the configured proxy

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=233943

            Bug ID: 233943
           Summary: NSURLSession WebSocket does not use the configured
                    proxy
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Mac (Intel)
               URL: https://ws.ifelse.io/.ws
                OS: macOS 12
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Page Loading
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: smudge_docents.0z at icloud.com
                CC: beidson at apple.com

Created attachment 446214

  --> https://bugs.webkit.org/attachment.cgi?id=446214&action=review

WebSocket connection timeout errors in the JavaScript Console.

– Overview:
On macOS Monterey systems with configured Automatic Proxy Configuration (.pac) file or HTTP/HTTPS proxy servers, Safari doesn't use the proxy when establishing WebSocket connections if the experimental feature "NSURLSession WebSocket" is enabled (that is the default setting on Monterey).

– Steps to Reproduce:
1) Set a PAC file or HTTP/HTTPS proxy in System Preferences --> Network.
2) Go to https://ws.ifelse.io/.ws (that server is running https://github.com/jmalloc/echo-server according to this Stack Overflow question https://stackoverflow.com/questions/4092591/websocket-live-server).

– Actual Results:
On networks where Internet access is allowed only using the network proxy, the connection will not succeed and JavaScript Console will yield:
WebSocket connection to 'wss://ws.ifelse.io/' failed: The request timed out.

– Expected Results:
Safari should use the system proxy.

– Build Date & Hardware:
I've tested this issue on macOS Monterey 12.0.1 (21A559) with the following Safari builds:
• Safari 15.1 (17612.2.9.1.20) <-- current version on Monterey
• Safari Technology Preview release 135 (Safari 15.4, WebKit 17613.1.7.3)
• WebKit build archive r286598 <-- it actually threw a bunch of errors on startup and I was unable to test by disabling "NSURLSession WebSocket" because when I tried to open its Preferences to enable the Development menu, it crashed… so I'm not 100% sure about this test

– Additional Information:
If I disable the "NSURLSession WebSocket" experimental feature, system proxy is used and connections succeed.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20211207/cc9d5d8c/attachment.htm>