Fiddler Everywhere provides several different ways to save, share, export, and import captured traffic. You could try the Save option and share your captured session via the Sessions list. To save as SAZ, you will need to select the desired sessions, open the context menu, and select Export to SAZ.
Please do let us know if you are still experiencing the issue with the latest version of Fiddler Everywhere and provide as much as possible information about the customer's PC configuration so we could investigate your case further.
Thank you for your reply.
Our customer's PC was
1.Installed latest version of Fiddler.
2.Using Fixed IP.
3.Exclude Proxy Server.
4.Single Sign-On was Off
These are part of the configuration of our customer's PC.
We still need a lot more information about the issue you are facing and about the environment specifics. Please provide more details to the following questions:
1. How is the problem manifesting? Is exporting to SAZ (refer to this article on how to use the context menu to export) not working for all sessions or only for a specific set of sessions? If the latter, please let us know what the captured traffic looks like (and if possible, please share the endpoints that are generating the traffic).
2. By the latest version of Fiddler, we assume that we are talking about Fiddler Everywhere. Please let us know if that is correct or using the classic Fiddler instead (this forum focuses on the new Fiddler Everywhere).
3. Could you clarify what you mean by Exclude Proxy Server (3rd point), and Single Sign-On was Off (4th point)?
4. Have you enabled secure traffic capturing (HTTPS) by installing and trusting the Fiddler Everywhere root certificate
Where should I ask about fiddlerCap?
I will describe this method just in case,
How to got the log this time.
Indeed, this forum is focused on FIddler Everywhere, but we are also assisting with any Fiddler-related products as a part of the Fiddler family.
That said, I've tested the steps you are describing, and the snapshot functionality is working as expected on my side. The screenshot generated from the snapshot is present in the exported SAZ file. It is usually a session with a URL that looks like this: http://localhost/Screenshot_11-23-31.jpg. Tested with Windows 10 with Google Chrome or Brave browser and the latest version of FiddlerCap. You could also try to open the generated SAZ file in Fiddler Everywhere (or in the classic Fiddler) and check if the screenshot exists in the session logs.
Let me know if I am missing a step or another important details so that I could reproduce the issue.
As a side note, the team is currently working on a new product called Fiddler Jam. The product is still in beta but you could sign up for the Pilot program which is about to start.
I didn't have enough explanation,
The problem only occurred in the customer's PC configuration, not when we investigated it in-house.
To be honest, this problem is difficult to solve. Have you ever had a record of similar cases?
The method I told you is a runbook for the work, there are no steps skipped.
I can't recall dealing with a similar issue. Perhaps you could ask the customer for more details about his environment and the exact steps needed to reproduce this one. You could also ask him to try installing and enabling Fiddler Everywhere (to verify that he can set the Fiddler proxy as FiddlerCap would do).
Sorry for not replying,
Because I was asking Oracle about this issue.
The customer's project uses OracleServiceCloud and
I needed to solve a screen freeze problem that occurred during the customer's business.
In order to clarify when the screen freeze occurs, Oracle has instructed us to use a tool that can automatically take screenshots of the screen.
That was Fiddler Cap.
However, the screenshots didn't work, so I couldn't pinpoint where the problem occurred.
What I want to emphasize is
HTTP confirmation has already been acquired by FiddlerCap, so it is not necessary to use only the HTTP monitoring function.
So I'd like to ask, is FidllerEveryWhere able to take screenshots automatically when there is a processing problem?
Fiddler Everywhere does not have the functionality for capturing screenshots (at least for now).
However, the team is currently working on a product called Fiddler Jam. It still in beta phase but you could signup for the pilot program. Hint - Fiddler Jam could take screenshots (alongside the captured logs) from your current browser tab.
We were considering using Fiddler EveryWhere for a while,
However, due to the lack of snapshot function, it seems that Oracle cannot investigate the cause of the error.
Therefore, we are considering using Fiddler Jam instead of Fiddler Cap.
Can you tell us the official release date of Fiddler Jam?
Fiddler Jam is feature complete but still in the early access program. We are boarding new clients to the pilot program to make sure it solves their needs properly. In the this program, you will be able to use it with your end-users.
We could organize a private call to discuss your needs and what you would like to see in the upcoming Fiddler Jam and next versions of Fiddler Everywhere. If you are interested, please email me at nikolay.iliev at progress.com to arrange the meeting.
Thank you, we will consider it.
However, if the reason why snapshots cannot be taken is outside the product, I think that using a new product will not be a structural solution.
The subject goes back, is there a record of what happens when FiddlerCap snapshots don't work?
If there are any security software or settings that interfere, please let me know.
The customer told me to reconfirm, so I contacted you.
Is there any security software that could interfere with Fiddler products?
There are few things you could check and verify.
- Is your client pressing the Snapshot button or expecting from FiddlerCap to create automatic snapshots? You are saying, "So I'd like to ask, is FidllerEveryWhere able to take screenshots automatically when there is a processing problem?" which indicates that you are expecting FiddlerCap to take the screenshot on some event, but FiddlerCap does not support this.
- Another thing to verify is that the user is pressing the snapshot button on the proper screen. FiddlerCap will take screenshots only for the active window, which must be considered when a popup window appears (or following a link to an entirely new window/tab). Once a screenshot is successfully taken, the new screenshot should almost immediately appear in the session list (listed as a localhost/Screenshot_....jpg session).
- Regarding the screen freeze. This could be the real problem - if the whole browser/PC is freezing and can't recover, this may be the reason why FiddlerCap is unable to take a screenshot at this very moment. You could confirm that the user can take a screenshot with FiddlerCap before the freeze screen issue appears (e.g., opening a trivial link like https://example.com).
I used Fiddler for research before bug fixes . But Fiddler doesn't work in Customer's PC.On details We could not save the snap shot.
WE check the SAZ file. But snapshot Log didn't exist in a SAZ.
1 person has this question