You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our 1DS C++ SDK provides a "Classic" Fiddler inspector. Unfortunately the "Classic" Fiddler is a .NET Framework app that runs nicely on Windows.. But barely runs on Mac, esp. since it uses Mono, AND it used to use 32-bit Mono - Fiddler app doesn't work too well on Catalina (as in Mr Stark, I don't feel so good...) , that now supports 64-bit apps only. This is a bit of an issue. Even when Fiddler worked on Mac, the experience was rather glitchy.
Now there's a new initiative - "Fiddler Everywhere", https://docs.telerik.com/fiddler-everywhere/user-guide/live-traffic/inspector-types , which does not seem to be like a C# app, but more like a Javascript (Electron?) app. Due to unrelated circumstances I did some prior work on writing a WebAsembly (thus, Node and Javascript)-compatible protocol decoder in this PR: #336
Proposal:
take the prior art and transform it into ready-to-use node.js and javascript module / library
plug-in that library as "Fiddler Everywhere" inspector
Benefit is that we may enable engineers running on Mac and Linux to use an outside generic traffic inspection tool, with an opensource decoder implementation available in our repo.
The text was updated successfully, but these errors were encountered:
Our 1DS C++ SDK provides a "Classic" Fiddler inspector. Unfortunately the "Classic" Fiddler is a .NET Framework app that runs nicely on Windows.. But barely runs on Mac, esp. since it uses Mono, AND it used to use 32-bit Mono - Fiddler app doesn't work
too well
on Catalina (as inMr Stark, I don't feel so good...
) , that now supports 64-bit apps only. This is a bit of an issue. Even when Fiddler worked on Mac, the experience was rather glitchy.Now there's a new initiative - "Fiddler Everywhere", https://docs.telerik.com/fiddler-everywhere/user-guide/live-traffic/inspector-types , which does not seem to be like a C# app, but more like a Javascript (Electron?) app. Due to unrelated circumstances I did some prior work on writing a WebAsembly (thus, Node and Javascript)-compatible protocol decoder in this PR: #336
Proposal:
Benefit is that we may enable engineers running on Mac and Linux to use an outside generic traffic inspection tool, with an opensource decoder implementation available in our repo.
The text was updated successfully, but these errors were encountered: