HI,

We've been using FiddlerCore 5.0.0 for a while, but recently found that we can't open any SAZ files we generate. When we try to open any in Fiddler Classic we get a popup with the message: The selected file is not a Fiddler-generated .SAZ archive of Web Sessions.

Here are the things I've tried:

• When renaming the saz to zip the contents look correct.
• After using the repair option when opening the saz in FiddlerClassic the saz then opens.
• Renaming the repaired saz to zip and comparing the contents the the original saz as zip - contents compare identical.
• We use a custom saz writer that hasn't been changed since we originally integrated FiddlerCore, but I'm seeing the same error in each Session object we cache for list passed to Utilities.WriteSessionArchive : "Session #error CS0103: The name 'm_requestID' does not exist in the current context, error CS0103: The name 'm_state' does not exist in the current context". This is not coming from our code. 
• I tried not using a custom writer, but just call Utilities.WriteSessionArchive, the call fails but I can't determine the reason why.
• Attached is a sample saz file we generate that causes the issues described.

Thanks for any assistance.

please!

Hello Telerik Team,

Could you please let me know with which version of Fiddler core library HTTP/2 will be supported.

Many thanks, Sven

Hello,

Could you please let me know why the Fiddler core library is not supporting HTTP/2 yet. It is standard since a while and it shouldn't be a hard deal to get it implemented. If you want to be state of the art you should invest here.

Many thanks, Sven

Hello.

I would like to be able  to export a WebTest directly from FiddlerCore using oSession.

Thank you.

 

Albert Zakhia

albertzakhia@hotmail.com

I want to use PAC file. http://127.0.0.1:8888/proxy.pac, this way, if my proxy accidently quits without remove the proxy setting, the browser will be able to continue to work since it can't find the pac file, thus consider it "No proxy".

 

But When I set the flags, if I don't include: "RegisterAsSystemProxy", the PAC file will not registered.

If I DO include "RegisterAsSystemProxy", the PAC file is registered, but also the proxy servers, 127.0.0.1 8888 for http and https. What's the point to have both registered, and it negate my purpose.

Anyway to hook up PAC file only?

 

Also, how to  modify the PAC file content, for GOD's sake?

Describe the bug
In case of an HTTPS session, FiddlerApplication.BeforeRequest event returns Session object which have wrong values for Session.fullUrl and Session.PathAndQuery properties, e.g. values are missing the URL parameters and ends with '443'.

To Reproduce
Steps to reproduce the behavior:

1. Subscribe to FiddlerApplication.BeforeRequest
2. Browse an URL of the type 'https://xxx.yyyyyyy.com/zzz?aa=1&b=2'
3. The event is raised, and the passed Session.fullUrl has the value of 'http://www.yyyyyyy.com:443'.

Expected behavior
Session.fullUrl has the value of 'https://xxx.yyyyyyy.com/zzz?aa=1&b=2'.