Hi, I have the following scenario:
Open Chrome browser in proxy using Selenium WebDriver (Selenium 3.9.1, Latest versions of Chrome and ChromeDriver).
Navigate to the page https://www.playbuzz.com/termsofuse
Navigate to the page https://www.playbuzz.com/stephanganev10/which-old-school-dating-show-would-you-have-totally-won
When I navigate to the second page, FiddlerCore doesn't capture any HTTP traffic. If I open Fiddler application, I also don't see any HTTP traffic captured.
However, when I open this page without proxy, I can see all the HTTP traffic.
Can anyone please help me?
Thanks
Hi
When i test our domain URLs with Fiddler I get a 502 error for the pages. Although the pages do exist. If i then test them in Screaming Frog i get the correct status code 200. Has anyone any idea why this could be happening?
Could it be something to do with Akamai and the Bot Manager blocking Fiddler?
Thanks
Mark
HI,
I have been trying to get fiddler to broadcast request coming from visual studio.i have been through many forum post etc over the past few days.
1 - is fiddler suppose to broadcast all GET's before IIS logs get this info?
2 - what is the process of launching a visual studio 2017 debug request, how/where it finds/looks for the Local IIS website virtual directory and where/how does fiddler get this data to show all of the GET's.
Sorry, I know this might be a lot, but i have been at this for days and have not found a link that explains this/these processes.
I am just trying to learn the when, what and how of how visual studio using Local IIS, IIS and fiddler all work together.
thanks for your time, advice and any help
Hey guys, i need a help.
fiddler.network.https> HTTPS handshake to api.imvu.com (for #20) failed. System.Security.Cryptography.CryptographicException Errore non specificato.
this problem is present with any asite/application
i use win10, fiddler version v5.0.20181.14337
Best reguards
After Updating the Fiddle it shows this message and Fiddle Won;t Start.
how to Solve this issue or i have to uninstall and install it again ?
Starting Android N (7.0) and up, Google has chosen only to allow leaf certificates that expire within 39 months.
First mentioned for chrome in 2015: https://bugs.chromium.org/p/chromium/issues/detail?id=475745
Could you please consider either reducing the lifetime of the root CA to <39months AND / OR allow us to import our own CA like competitors already offer.
We like working with Fiddler but the inability to supply custom CAs easily and not adhering to the above requirement set by Google in Android 7.0 + forces us and many others to having to avoid using Fiddler.