WebSocket connections made by Resonite don't use the proxy configured in Config.json.
Regular HTTP(S) requests and WebSocket traffic outside of Resonite are proxied as expected.
To Reproduce
Set up a proxy that allows for inspecting WebSocket traffic (I used Fiddler Classic but mitmproxy should work too)
Test if the proxy works and intercepts WebSocket traffic by opening https://echo.websocket.org/.ws in a browser and checking if the proxy logs messages
Create a Config.json file to make the game use the proxy. In my case, I enable autoDetect to use the system proxy, like so:
{
"proxy": {
"autoDetect": true
}
}
Launch the game and spawn any item that connects to a WebSocket server outside of the local network. I quickly cobbled together an item that connects to wss://echo.websocket.org for testing purposes.
Check the proxy's log - the WebSocket traffic won't be there
Expected behavior
I expected the WebSocket traffic to pass through the proxy and get logged
Describe the bug?
WebSocket connections made by Resonite don't use the proxy configured in
Config.json. Regular HTTP(S) requests and WebSocket traffic outside of Resonite are proxied as expected.To Reproduce
Config.jsonfile to make the game use the proxy. In my case, I enable autoDetect to use the system proxy, like so:Expected behavior
I expected the WebSocket traffic to pass through the proxy and get logged
Screenshots
No response
Resonite Version Number
2024.10.29.1229
What Platforms does this occur on?
Windows
What headset if any do you use?
No response
Log Files
FLIESENTISCH - 2024.10.29.1229 - 2024-11-06 21_23_05.log
Additional Context
No response
Reporters
m1nt_ (Resonite) / @the_crescent_moon (Discord)