NSURLSession WebSocket - where to turn off in Safari 17 - Sonoma

You here chose to use a cross-platform framework (Azure DevOps Server), and are having issues with that choice and that product.

The folks with the source code to that cross-platform tooling are Microsoft. Not Apple.

The folks that have the responsibility to keep that cross-platform tooling working across the supported web browsers are Microsoft. Not Apple.

The people that can pursue rendering issues with Safari are Microsoft. Not Apple.

While this might well be an Apple bug, the path to get that resolved with Apple is via Microsoft Azure, as Azure can reproduce this issue.

If Safari is listed as a supported browser with this Microsoft cross-platform tooling, and if you are running the most current DevOps Server (12-Sep-2023 or newer), then please check with Microsoft Azure Support.

And we’re not people that work for Apple, we’re other Apple users and some are other third-party developers. Azure DevOps Server just isn’t common discussion fodder around here.

Still nothing I guess... I asked on apple discussion forums - Possible issues with Websockets in… | Apple Developer Forums (and also linked your issue..)

Hi 👋!

Sorry but simple answer is

“You can’t turn off NSURLSession WebSocket” 🤷

But here is some information that could be useful for you to avoid problems caused by that option:

Environment:

• OS: macOS 14.0 Sonoma
• Browser: Safari 17.0
• TTYD: 1.7.4 (ARM Build)

Additional context

In earlier versions of Safari it was possible to turn off NSURLSession WebSockets but as of 17.0 it is no longer possible to disable as there is no Feature Flag for it. Chrome and Firefox load the session just fine.

Possible fix

Spent more time testing this between Safari versions on different configurations and found that Safari 17.x seems to only have issues connecting to an WebSocket session when there is a proxy being used between Safari and TTYD (whether it be SSL or just plain HTTP). On older Safari versions (15.x/16.x/17.x) in this proxy scenario, turning off NSURLSession WebSocket (under 'Experimental Features') allows TTYD to load as expected so there still seems to be some issue between this and LWS. However, since I can get Safari 17.x TTYD connections to work by removing the proxy from my scenario that will work until I can spend more time figuring out why NSURLSession WebSocket under Safari seems to break proxied/tunneled WebSocket sessions.

Check for updates to the Azure DevOps Server, check whether Tokens will work, and then contact Microsoft.

The following appears current: Azure DevOps Server 2022 Update 0.1 Patch 3 Release Date: September 12, 2023

Using tokens: https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate?view=azure-devops&tabs=Windows

If that fails, check with Microsoft Azure support.

mate100 wrote:

funny how chrome and firefox do not have that problem.

That is because Chrome and Firefox do not have the same level or privacy protections that Safari uses.

do you know how/where to disable this NSURLSession WebSocket in safari?

That was always just a hack that people did to avoid fixing the underlying problem, whatever that was.

right now Im working in chrome

That's your only option. Well, I guess you could probably use Firefox too. Maybe some other 3rd party browsers.

If you want to keep working in Safari, you'll have to use the developer features to explore why it isn't working properly. Maybe this is something you can fix on your side. But maybe it is a problem with the server.

Hi, did you get anywhere with this? We are possibly having issues with Websockets in Safari 17 in our software.

It's a pain that we don't seem to be able quickly rule out the usage of NSUrlSession Websockets as being the root cause of the issue. Is there a way to disable it using some JS api???

Thanks!

Please check my previous answer

NSURLSession WebSocket - where to turn of… - Apple Community

Earlier you said:

mate100 wrote:

I am working in Microsoft devops server on Safari

To be clear, this is your problem to solve. Fix your site.

As you clearly believe this is not a Microsoft issue and not a website issue, open a TSI with Apple, then.