Translated from the Chinese original.

Today I was testing Memo’s translation service and found that it kept failing, so I wanted to capture the traffic to see why.

I naturally opened Fiddler on my computer, but, unexpectedly, I couldn’t capture any HTTP requests from Memo at all… (HTTPS capture was enabled, and other software tested fine.)

I searched around and found that it might be because of Electron.

So, following Packet Capture Tips (1) - Zhihu, I tried capturing with Wireshark. Unfortunately, Wireshark showed far too much information, and even after filtering by IP and protocol there were still a huge number of requests… so I gave up.

Later I found the article Capturing Traffic from an Electron App - CSDN Blog.

code.exe --args --proxy-server=localhost:8888 --ignore-certificate-errors

I tested it with Fiddler and found that I could capture Memo’s update-check request, but still couldn’t capture the translation request…

Next, following the approach in Capturing Traffic from an Electron App - CSDN Blog, I debugged the Electron app in Chrome.

Memo.exe -remote-debugging-port=9222

Then I opened chrome://inspect/#devices in Chrome.

Output appears in the Console, but not in the Network tab
Output appears in the Console, but not in the Network tab

Awkwardly, I could see the translation records logged in the Console, but I couldn’t find any HTTP requests in the Network tab…

Finally, I searched in English and ended up finding a solution.

Download HTTP Toolkit for Windows

HTTP Toolkit capturing an Electron app
HTTP Toolkit capturing an Electron app

The free version is enough.