2.2.8.0 Beta

[FiddlerMaddog]

Hi Eric,

Just downloaded the new version.
The Log tab is a great addition, I will certainly make use of it.

I noticed that I no longer see zip/exe files in Fiddler - is this a
new feature? Can it be turned off?

I saw in the release notes that the autoresponder is now "visible to
script", any documentation on that?

Thanks

[EricLaw]

<<I noticed that I no longer see zip/exe files in Fiddler - is this a
new feature? Can it be turned off? >>

I don't really know what you mean by that, but my default assumption
is that you've got a filter applied.

[EricLaw]

Vis-a-vis the AutoResponder, what's exposed isn't very powerful, but
(for folks who haven't written their own version <g>) it might be
useful.

The object is exposed as FiddlerApplication.oAutoResponder, and its
methods and properties are:

Fiddler.AutoResponder.AddRule(string sMatch, string sAction, bool
bEnabled)
Fiddler.AutoResponder.AddRule(string sMatch, Fiddler.Session
sessionWithResponseToReturn, string, bool bEnabled)
Fiddler.AutoResponder.ClearRules()
Fiddler.AutoResponder.ImportSAZ(string sFileName)
Fiddler.AutoResponder.ImportSessions(Fiddler.Session[]
sessionsToCreateRulesFor)
Fiddler.AutoResponder.LoadRules(string sFilename)
Fiddler.AutoResponder.SaveRules(string sFilename)
Fiddler.AutoResponder.ToString()

bool Fiddler.AutoResponder.IsEnabled
bool Fiddler.AutoResponder.PermitFallthrough

> > Thanks- Hide quoted text -
>
> - Show quoted text -

[FiddlerMaddog]

Glad to see the AutoResponder API come to life.
I always wanted to integrate a folder monitor that automatically adds/
removes rules (with a regex pattern, like dropping files from windows
explorer).
Looks like I'll have to wait a little more to be able to do that,
since there seems to be no way to remove rules.

> > <<I noticed that I no longer see zip/exe files in Fiddler - is this a
> > new feature? Can it be turned off? >>
>
> > I don't really know what you mean by that, but my default assumption
> > is that you've got a filter applied.

I downloaded two large files, with zip/exe extensions, they were
downloaded in Firefox (not showing up in Fidder at all) even though
Fiddler was attached and showing all other sessions.
I don't usually use filters, but it was the first thing I've checked
(mostly because filters were mentioned in the release notes).
Most software (i.e. browsers) will wait a very very long time for
Fiddler to buffer downloads, but some (like most update downloaders)
don't.
I've always wanted a feature that reads the content length and turns
on "streaming mode" dynamically for downloads >3MB, after all - the
huge files are rarely the target of the debug session.
I thought you implemented that :-)

Thanks!

[EricLaw]

The RemoveRule method was inadvertently marked as Internal. I'll get
that cleaned up.

> I downloaded two large files, with zip/exe extensions, they were
> downloaded in Firefox (not showing up in Fidder at all) even though
> Fiddler was attached and showing all other sessions.

"Other sessions" from Firefox, or from another process?

My default assumption is that either you had downloaded the files in
question previously and they were in the Firefox cache, or that you've
got some sort of downloader plugin in Firefox that doesn't respect
Firefox's proxy settings.

> Most software (i.e. browsers) will wait a very very long time for
> Fiddler to buffer downloads, but some (like most update downloaders)
> don't.

I haven't yet encountered an update downloader that doesn't "wait" for
Fiddler. Can you elaborate?

> I've always wanted a feature that reads the content length and turns
> on "streaming mode" dynamically for downloads >3MB, after all - the
> huge files are rarely the target of the debug session.
> I thought you implemented that :-)

Even if I had, I wouldn't hide the files. :-)

FWIW, autostreaming like this is possible via a Fiddler extension.
Fiddler raises the DoPeekAtResponseHeaders event when response headers
are available and the event handler could toggle the Session's
bBufferResponses value at that point. I was considering an "Autostream
responses over <size>" rule, but haven't gotten around to building it
yet.

One caveat is that the rule would only work if the headers indicate
the content-length; if the server used Connection: Close or Transfer-
Encoding: Chunked, the length would not be available at the time
DoPeekAtResponseHeaders is called.