Hi everyone,
Fiddler classic was working smoothly in the Memu play emulator application, but then the emulator crashed. I updated it. Now, the android certificate is in the system section, but Google is giving error that certifica is not trust, it was giving errors, and I was monitoring the https traffic of applications such as Telegram, Twitter, Clubhouse without any problems. While I can download on my own PC and Android, I can't right now. error. However, after closing fiddler, I start the download and open it again, the download continues. I deleted and reinstalled Memu 2 or 3 times and tried again, it still gives the same error. What do you think is the reason? Also, I haven't tried any other 2 or 3 emulators. I get the same error on them too. I have been using it for 1 month without any problems. I'd appreciate it if you could help. Thanks in advance
Hi
I am trying to decode https traffic with fiddler classic. I see error below in Log. I did reset all certificates, trust root cerficates with both MakeCert, CertEnroll engines. Please advice how to fix this issue. I used to decode https traffic with older version (before 2019) of fiddler which used to work without any error. Now i do not find the download link for older version of fiddler.
10:06:28:1870 HTTPSLint> Warning: ClientHello record was 1803 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance
10:06:28:2315 !SecureClientPipeDirect failed: System.Security.Authentication.AuthenticationException A call to SSPI failed, see inner exception. < An unknown error occurred while processing the certificate for pipe (CN=www.telerik.com, O=DO_NOT_TRUST, OU=Created by http://www.fiddler2.com).
My Https settings are as below. I see the same issue with both MakeCert, CertEnroll engines.
Both Edge and chrome Browsers give error below when i nagivate to https://www.telerik.com/fiddler/fiddler-classic.
I sned frequent requests between https://gym.whu.edu.cn/api/GSStadiums/GetAppointmentList?Version=2&SportsTypeId=21&AppointmentDate=2024-06-04 and https://gym.whu.edu.cn/api/GSStadiums/GetAppointmentList?Version=2&SportsTypeId=21&AppointmentDate=2024-06-05, I set up an auto-save to txt function,I can see the response in the fiddler, in the firtst two request ,i can see the response in the txt,but in the following request, the txt do not update,until over several times , i do it again ,it can be updated, I do want to know why this happen. Addly,if i do the request https://gym.whu.edu.cn/api/GSStadiums/GetAppointmentList?Version=2&SportsTypeId=21&AppointmentDate=2024-06-04 and https://gym.whu.edu.cn/api/GSStadiums/GetOftenList?Version=2 ,i can see the update in real time.
I want to add that I do the request by my manual click. In first way, i just click two buttons on the same interface. in the latter one, i keep opening the screen to return to the previous screen to do the request
Hey guys!
I noticed the Low-Level Capture Support for MacOS and I saw it planned for Windows as well.
So I am curious if there are already some details.
Out of curiosity, I think, we could look over to HTTP Debugger, which sadly was never updated anymore.
But HTTP Debugger captures every traffic on a Low-Level.
I think modifying outgoing Requests is not possible there, but you can modify responses, which can bypass some limitations.
(Like Cert verification on Fiddler)
So I am curious what the current plan could be.
I recently upgraded fiddler classic to the latest version, but after the upgrade, my extension file dll did not take effect. Its function is to decrypt traffic, which may be related to the upgrade of fiddler. I read the upgrade description and it seems to be a security-related issue. please help me.
I looked through the documentation and found nothing of value: https://docs.telerik.com/fiddler/extend-fiddler/extendwithdotnet
Fiddler classic the lastest version information:
5.0.20243.10853 [16/05/2024]
fixes:
Check for updates fails in the beta channel.
Update third party dependencies to mitigate potential security vulnerabilities.