Closed Groovin-Dev closed 3 months ago
Thank you for taking the time to provide feedback. I was able to reproduce the issue easily with what you provided.
There is a fix available for Fluxzy.Core in the latest alpha version on nuget.org (currently validating 1.26.2-alpha). This will likely be merged into the next main version after further testing.
If you wish to have the fix early in Fluxzy Desktop, you can overwrite the Fluxzy.Core DLL in the application data; it's currently using the stock version.
Describe the bug Any use of Fluxzy as a proxy seems to break some WebSocket connections.
Describe the tool and the environment I have had the issue with
Fluxzy.Core
andFluxzy.Desktop
To Reproduce Steps to reproduce the behavior:
Fluxzy.Desktop
orFluxzy.Core
(with nothing custom)https://echo.websocket.org/.ws
Screenshot Seems like it's not marking the connection as WS even though it is.
Expected behavior WebSockets should just work like they usually do and the information should be captured. With Fiddler (The desktop version and FiddlerCore) everything works
Additional context Probably related to https://github.com/haga-rak/fluxzy.core/issues/221