My windows DPI scaling is set to 200%, as my resolutions to 2000x3000.
If I load fiddler normally, I see the following blurry text.
So i saw this bug report, https://feedback.telerik.com/fiddler/1361354-hope-the-fiddler-can-support-the-high-dpi-screen which suggested to load up fiddler with -dpiaware, and now some text is better, but most of the tabs and buttons are incorrect sizes in the composer. In my opinion its more usable with the blurry text. I also tried to change the Fiddler.exe.config - EnableWindowsFormsHighDpiAutoResizing from true to false, but the only affect this had was to change the size of the mouse cursor.
Any ideas on something else to try, or is this a limitation of Fiddler / .Net WinForms.
Fiddler's "Web Browsers" filter does not include msedge.exe as a web browser. This is the executable name of the new Chromium-based version of Edge that Microsoft is now working on.
This should be a one-line fix and very much appreciated by the many thousands of Fiddler+Edge users.
I find myself applying the same filters again and again on each launch of Fiddler (I mean the filters listed below the list of requests). I think it would be really great if you could allow the restoration of previously applied filters (e.g. by having a save/load filters option). Also, allowing to filter out by "Request Method" would be great too. Congratulations on this tool, by the way. It is really great. :)
I want to capture traffic from a Chrome Incognito window only.
When I click the 'pick target' button on the toolbar and point it at the Chrome window it picks up some particular process from chrome, but that does not seem to be the one from where network requests are sent from.
Looking at Chrome's Task Manager and comparing with what Fiddler shows, Fiddler is picking up the "Browser" process, while requests are coming from the "Utility: Network Service" process, thus the difference.
An acceptable solution for this would be if we could enter the process ID manually in the UI, instead of using the target picker.
Websocket monitoring is such a cool feature in fiddler. What i´m missing is the possibility to export all messages sent and received via the websocket.
In Wireshark i would associate that functionality with "Follow TCP stream".
The reason behind:
I want to search within the websocket communication for certain id´s patterns etc. This is currently not possible as every message is handled separately in fiddler.
What i would expect:
Beeing able to export selected or all messages in the WebSocket pane. (one could think of adding "received","sent" and a timestamp between the messages with a certain beginning to be able to filter those messages later.)
I would call the fact that:
- "Save" - "Selected Sessions" "as Text or ZIP" is only saving the websocket HTTP upgrade request together with the response but without the websockets payload
Or i am missing something. Comments welcome...
This is a copy of Fiddler's new Feedback Portal not working properly submitted to the Fiddler groups forum:
I have submitted probably a dozen or two bugs to the Fiddler Feedback portal https://fiddler.ideas.aha.io/ideas . Fiddler recently changed the feedback portal software and attempted to import all existing bugs. The import was not done properly. Every bug I reported the old links do not redirect to the imported reports. If I search for a report by title only arbitrary comments of the reports are included. There are no screenshots or attachments. Also I cannot login to the portal with my yahoo account, it says "Oh, no! Something's not right, but we're sorting it out." I was able to salvage some of what I reported from screenshots of the old site but I don't remember all of what I reported. Please retry the import so what users reported remains open for discussion and fixing. One particular bug is really a nuisance and hasn't been fixed when I have one session open raw in inspector and I click on another session I have to wait a long time. I don't remember what bug I filed over it but I know I filed something.
(Since the original post I have been able to login with my yahoo account. It does not show any bugs for my e-mail and they're still broken missing content and comments as "Imported User")
I would like a way to block all transfers made internally by Fiddler unrelated to what is being proxied because it disrupts my tests. I am using Fiddler in test cases where I need the data to be limited to what I'm sending through Fiddler. Every time Fiddler is started it makes one or more connections to fiddler2.com. For example http://fiddler2.com/Banners/BannerVersion.txt and also there's a survey connection sometimes as well. Those requests are redirected most of the time to a cloud server. I have to use various VM images to run some of the tests and I see it a lot in the packet captures. The update check I have blocked in the registry where I set BlockUpdateCheck to True. I could ignore fiddler2.com I suppose. Regardless I don't like it there is SSL traffic I can't account for or decrypt, and even if I could it would still be noise disrupting the data I need to check.
I found a preference fiddler.banners.showdefault and fiddler.telemetry.AskPermission but I'm not sure if they relate.
On a somewhat related point consider an option to disable telemetry, refer to Fiddler Script Editor disable internet access
My Fiddler log is usually filled with thousands of ClientHello warnings. It's a burden for me to read through the log with all those messages. For example:
23:42:42:4843 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance 23:42:42:4863 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance 23:42:42:4863 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance 23:42:42:4863 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance 23:42:42:4983 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance 23:42:42:4983 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance 23:42:42:5113 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance 23:42:42:5123 HTTPSLint> Warning: ClientHello record was 508 bytes long. Some servers have problems with ClientHello's greater than 255 bytes. https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance
I discussed this with Eric Lawrence in the Fiddler Groups thread HTTPSLint> Warning: ClientHello record was xxx bytes long and he had a few suggestions:
Since I installed Fiddler on my machine, I am not able to connect to Team Foundation Server in Visual Studio (Version: 2013 Professional) if Fiddler is not running. I need to start the Fiddler first in order to connect to Team Foundation Server. I have tried various options that I found online. I even uninstalled Fiddler but still no luck.
Thanks in advance.
PS: I was not finding any other medium through which I should have communicated this, So, I've chosen to report it as a bug.
Fiddler analyse websocket session incorrect. Incorrect text is in the websocket session.
For examble, websession https://wsapi.skype.com/?platform=1418/184.108.40.206&cloud=apis&clientInfo=os%3DWindows%3B%20osVer%3D7%3B%20proc%3Dx86%3B%20lcid%3Dru-RU%3B%20deviceType%3D1%3B%20country%3DRU%3B%20clientName%3Dskype4life%3B%20clientVer%3D1418%2F220.127.116.11%2F%2Fskype4life%3B%20timezone%3DEurope%2FMoscow in the web skype.
make windows have 2 languages for keyboard, e.g. en-us, and ru-ru;
make key shortcut to switch langs: alt+shift as usual;
select current lang: eng
run fiddler until it accumulates some traces;
select one of the trace records, click on request panel, click on response panel, notice: lang has switched to RU now.
"Target Any Process" feature no longer working with Chrome. It used to work but no longer works specifically with Chrome. Still works with other processes. Capturing still works with Chrome as long as I am not using the "Target Any Process" feature.
Currently by listening to FiddlerApplication.OnWebSocketMessage it's possible to modify the incoming & outgoing messages but it's not possible to send independent direct messages in or out. Adding the ability to send direct messages will give more freedom on injecting custom messages in both directions, repeating server response messages etc. Currently if you need to inject an outgoing message you need to wait for the client to generate a message and only then intercept, modify and forward it. Sometimes the client may wait longer times to respond and a direct message mechanism would be quite useful to generate quicker responses. From: How to send a new web socket message instead of modifying an existing one? (https://groups.google.com/forum/#!topic/httpfiddler/CC5XxiWfpuI) Related to: Add properties to WebSocket object (https://fiddler.ideas.aha.io/ideas/FID-I-146)
The HTTP2 protocol has specific requirements about the characters that are valid in header names. If a server attempts to use one of these over a HTTP2 connection, the client will complain of a ERR_SPDY_PROTOCOL_ERROR.
This is particularly problematic because the problem will magically "disappear" when Fiddler is in use because Fiddler doesn't support HTTP2, and thus the problem characters are silently allowed by the browser using HTTP/1.1. https://twitter.com/ericlaw/status/1100175636595965957
Therefore, Fiddler's HTTP Protocol Violation feature should warn if a HTTPS response contains an illegal character in a HTTP header name or value.
Legal characters for names: abcdefghijklmnopqrstuvwxyz0123456789!#$%&'*+-.^_`|~
Legal characters for values '\t', ' ', 0x21 to 0x7E, and 0x80 to 0xFF.