Hi
i have followed the guide to run Fiddler as a service and it works OK. However my customrules.js is not being used.
I have added in proxy authentication rules which auto login to my external gateway and this works fine if running in the console. But running as a service Fiddler still works but external gateway authentication happens.

Has anyone used Fiddler as a service alongside a customrules.js file?

thanks

Gus

Hello.
I want to understand the logic of "Capture Traffic" button in the bottom left corner of Fiddler window.
My first thought was that Fiddler would capture traffic (I mean, show sessions in Sessions list) only when this button is pressed.
But later I've noticed that Fiddler is always capturing sessions, no matter is this button pressed or not. All filters on my "Filters" tab are disabled; "Troubleshoot filters" menu item is unchecked too.
I have a feeling that I've misunderstood the purpose of "Capture Traffic" button. Where can I read more about it?
Thanks.

hello
after removal of the fiddler me some sites in google chrome will not load and you receive such a message ERR_EMPTY_RESPONSE
how to solve this problem?

As the title says,How to route traffic from Fiddler to  all devices?

I have an saz file that works in the autoresponder if I drag all the packets there from the left side.  However, if I restart Fiddler (after having done that) or export the autoresponder packets as an farx and import it again, The page fails to display.  The browser makes a request for the main page.  Then it makes about 26 requests for referenced resources.  There are more to be made but it never gets sent and the page just spins after that.  It's not consistent either.  Sometimes it's after 25 requests, etc and it's not always the same packet that was last requested.  I'm not sure if it's something in the application logic or a bug in Fiddler.  What could cause IE to fail to display the page if I imported the farx rather than add them from the left side (the saz packets)?

For privacy issues, I can't post the saz file publicly.  I can provide one on request.

Hello,

I'm using Fiddler 4.4.9.6 and I'm trying to make the autoresponder use a file as a response with a regex rule.
The regex part is ok but it sends back a 403 error when using full URLs and local files.
The only way I can make it work is by using a relative URL and that's because it automatically adds a forward slash (/) to the response.

So:

- http://www.example.com doesn't work
- C:/mystuff/stuff.json doesn't work
- relativeurl/stuff.json does work

Any ideas?
Thanks!

Hi all,
I'm debugging a WCF Odata server on localhost.
I created a simple console tester end connected by the url http://localhost.fiddler:XXXX/MYAPI.svc/ to local server
Fiddler trace only GET session, none of PUT or POST or DELETE is traced.
If I connect console tester to a remote server, fiddler can trace everything.
Thank you for help
Diego

Hi Gurus,



I am a new one to this fiddler tools, but I have an interesting question,

After setting up one evironment, the connection is not working between
client/server. Then I used fiddler as troublershooting tools, but I
found when I enabled the tracing, my connection is back, then I disabled
the tracing my connection is lost again.



Could I know how fiddler made such kind of effect



Thanks very much



Tom

Hi,

I've been searching around but haven't been able to find something that fixes my issue.
I'm trying to debug an issue on a production server. I had no trouble on windows 7 but on the new windows 8 laptop I'm not having any success.

The error that comes up is:
The Same Origin Policy disallows reading the remote resource.

This is in chrome and firefox.

The file I'm trying to respond with is on my desktop. You can see the settings I'm using in the attached fiddler.png.

Anyone have any ideas on what the issue could be?

Hello.
When specified upstream proxy becomes unavailable, Fiddler is showing this messages in "Tools > Fiddler Options > Gateway > Show Current Gateway Info" window:
---
WARNING: HTTP Gateway specified was unreachable and is being ignored.
WARNING: HTTPS Gateway specified was unreachable and is being ignored.
WARNING: FTP Gateway specified was unreachable and is being ignored.
---
As I understand, Fiddler is just skipping specified proxy and using system proxy instead.
Is there a way to make Fiddler drop outgoing requests in case of invalid upstream proxy instead of forvarding 'em through the system proxy?