Skip to content

Latest commit

 

History

History
86 lines (56 loc) · 5.25 KB

introduction.md

File metadata and controls

86 lines (56 loc) · 5.25 KB
Raw
title slug tags publish position
Introduction
introduction
introduction
true
0

Welcome to Fiddler Everywhere!

Fiddler Everywhere is a high performance, cross-platform web debugging proxy for any browser, system or platform. It is a web debugging tool which logs all HTTP(S) traffic between your computer and the Internet, inspect and edit traffic, issue requets, and fiddle with incoming and outgoing data.

HTTP(S) traffic Inspection & Analysis

Fiddler Everywhere logs all HTTP(S) traffic between your computer and the internet. It captures traffic from virtually any application that supports a system proxy.

Request and Response Mocking

Fiddler support mocking or modifying request and responses on any application. It’s a quick and easy way to change HTTP(S) requests and responses without changes in the code.

API Composing

Use Fiddler API Composer to quickly test APIs by creating and sending requests. Useful while developing new APIs or when testing existing APIs.

Fiddler Everywhere main screen

Key Features

  • Compatible with MacOS, Windows, and Linux.
  • Inspect web traffic (HTTP & HTTPS).
  • Decrypt secure traffic (HTTPS).
  • Save, share, and receive captured traffic with collaborators.
  • Mock requests and respones
  • Modify response
  • Compose API requests
  • Save composed API requests
  • Fiddler Everywhere Pro features with extended sharing and collaboration options.

Fiddler Everywhere Pro

All Fiddler Everywhere features are available in both the Free and the Pro version. However, the Fiddler Everywhere Pro version extends the free version's sharing and collaboration options. The free version has some limitations related to sharing quotas. Refer to the table below for a detailed comparison of the Free versus Pro versions.

Features Free Pro
Capture and Inspect Traffic Unlimited Unlimited
Creating Composer Requests Unlimited Unlimited
Using Auto Responder Rules Up to 5 enabled rules Unlimited
Creating Saved Sessions entries * Up to 5 sessions Unlimited
Sharing Saved Sessions Up to 5 session (with up to one user) 1000 session
Shared Session Size Max 5 MB Max 50 MB
Email Support - Unlimited*

*subject to fair usage policy. Learn more about the support offering [here]({%slug support-page%}).

tip A Session in Fiddler Everywhere is a term that describes an entry that holds single or multiple requests and responses (captured traffic). Saved session entries are listed in [the Sessions list]({%slug saved-sessions-tab%}) and can also be exported as [SAZ archive]({%slug file-menu%}).

Release history

To learn more about the release history, visit Release History Page

Installation

Download the latest Fiddler Everywhere. To learn how to install Fiddler Everywhere, visit the [Installation]({% slug installation %}) section.

Documentation

Official Fiddler Everywhere documentation

We believe documentation is at its best when the content is a product of collaboration between the builders and consumers of that product. Everybody can play a role in making our documentation better, and we encourage you to help us with that task in the way that you choose:

  • Send Feedback Use the Was this article helpful? functionality to give us feedback and ideas on how we can improve the documentation. Alternatively, you could request a feture or report a bug using the Fiddler Everywhere Feedback Portal.

  • Create an Issue If you find an issue with our docs that needs addressing, the best way to let us know is by creating an issue in our Github repository. When creating an issue, please provide a descriptive title, be as specific as possible, and link to the documentation article in question. If you can provide a link to the closest anchor to the issue, that is even better.

  • Send a Pull Request Creating an issue is great, but what we love are pull requests. So, if you find an issue in the docs, or even feel like creating new content, we’d be happy to have your contributions!

    In order to do this, you must fork our documentation and submit a pull request. That way, you may contribute an update exactly where you found the error. After that, our technical writing team will need to approve your change request. Please use only standard markdown. For more detailed instructions, please follow the contribution instructions published in GitHub. You could directly initiate a pull request by using the Improve this article functionality.

License

Licensing agreement and detailed information about the different licenses and which one you should acquire is available in the Licensing section.