telerik/fiddler-everywhere-docs

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

Fiddler Public Documentation

Welcome to the GitHub repo for Fiddler Documentation. This repository contains the source content--written in Markdown--that we use to power the Fiddler Everywhere Documentation at www.fiddler2.com/docs. If you've arrived here wanting to search and peruse our docs, you'd be better served heading over to www.fiddler2.com/docs where our content is prettified and searchable.

We believe that the documentation for a product is at its best when the content is a collaboration between the builders and consumers of that product. As such, this documentation is both public, and open sourced. That means you can clone this repository, read the docs off line, or even load the entire thing to an Apple Newton, if that's your thing.

It also means that you can play a role in making our docs better for everyone, and if helping us make the Fiddler Everywhere docs better sounds interesting to you, read on.

Contributing

You can contribute to the public Fiddler Everywhere documentation in the following ways: either create an issue in this repository, or fork the repo, make the change and send us a pull request!

• Create an issue - If you find an issue with our docs that needs to be addressed, the best way to let us know about it is by creating an issue in this repository. When creating an issue, provide a descriptive title, be as specific as possible and link to the document in question (If you can provide a link to the closest anchor to the issue, all the better). Here's an example:

  Title: foo/bar/setting-things-up.md is missing an image
  Description: The image for setting up the the foobar handler is missing. https://github.com/telerik/fiddler-everywhere-docs/issues?state=open
  

Note: When creating issues, please don't modify the assignee or milestone fields. Also, please create one issue per fix or change. "Bundled" entries will be deleted.

• Send us a pull request - Creating an issue is great--and we certainly appreciate them--but what we really 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! If you're just getting started with open source, Git, and GitHub, we suggest you first read up on forking repos and sending pull requests, both great articles from the GitHub bootcamp.

  Once you've read these--or you've already memorized them--you're ready to contribute to the Fiddler Everywhere docs. Start by creating a local clone of our repo either using GitHub for Windows, GitHub for Mac or your friendly command-line:

  git clone [email protected]:telerik/fiddler-everywhere-docs.git
  

  Then, open up the fiddler-everywhere-docs folder in your favorite text editor and contribute away! Of course, as you work with the docs, we do ask that you follow a couple of ground rules:

  • Fixing grammar, punctuation, and other general errors is always appreciated. So are changes that expand on key ideas or correct errors in logic phrasing or otherwise. If your ambitions are greater, however, and you want to add completely new content to the site--like a new tutorial on using Fiddler Everywhere with an Atari 2600, for instance--we suggest you contact a member of the team first (or enter an issue!) to vet your idea. We will all be happy to hear your idea and offer advice.

  • Each document in this repo contains a section of YAML Front Matter at the very top. This content, which looks like the text below, is used by our auto-import tool when content is processed for the www.fiddler2.com/docs site. Please don't edit the content in this section of a document.

    ---

    title: Add stuff to Fiddler Everywhere

    slug: howto-add-stuff

    tags: How-To

    publish: true

    ---

  • When adding content or making changes, please use only standard Markdown syntax, and make sure to preview your additions or changes before sending us a pull request.

  Once you've made your changes, commit, pull, merge, push, and send us a pull request! We--and Fiddler Everywhere users everywhere--thank you for making our docs better!

fiddler-everywhere-docs's Issues

Unable to get macOS Mojave capture

When i start Fiddler on macOS Mojave 10.14.3 i do not see any results. "Capturing..." is displayed and i've enabled HTTPS decryption and imported the certificate (and trusted it) in Keychain Access. I've tried browsing on Chrome, Firefox, and Safari, but do not see anything get captured. It's just showing "No records available". Am i missing a step? I do have a system proxy configured that uses a PAC file if that matters.

Thanks

Why does the website show a table of contents of only <h2>?

The documents use <h3>, <h4>, etc. but the actual website just seems to ignore them, and only treats <h2> in the automated table of contents.

For example:
https://docs.telerik.com/fiddler-everywhere/knowledge-base/how-to-mock-responses

VS
https://github.com/telerik/fiddler-everywhere-docs/blob/master/knowledge-base/how-to-mock-responses.md

Can you please make all table of contents present all <hX>s? It will help navigation so much more helpful, easier and quicker.

body Coding error

like this

Fiddler certificate should be provided in PEM format for Linux

(This is more rightfully an issue that should target Fiddler Everywhere than the docs; please point me to the appropriate GitHub issues/JIRA tracker where I can file it if you have a public bug tracker. 😄 We could also resolve it by updating the docs though, so it's not entirely off-topic.)

While trying to get Fiddler Everywhere working on Linux, I realized that the way we currently export the FiddlerRootCertificate.crt format is not really optimal for getting applications to trust it. My particular example was Docker, but I also remember having to add it manually to the Firefox trusted certificate store to get it working, so it might be a general problem with this certificate on Debian Buster.

What I did to resolve it was exporting it from Firefox in PEM format (after having imported the .crt file provided by Fiddler Everywhere), then replacing the /usr/share/ca-certificates/extra/FiddlerRootCertificate.crt file with its content instead of the binary version. Then I followed the steps described in https://docs.telerik.com/fiddler-everywhere/get-started/configuration#configure-on-linux, to update the system certificate store. That way, I could get Docker to trust the Fiddler certificate which was helpful for me in debugging an issue with a private Docker registry etc. (Thanks for a nice product! 👍)

---

For convenience, here is the PEM version of the Fiddler root certificate as it looks right now; maybe this can help others until the issue is properly resolved upstream.

-----BEGIN CERTIFICATE-----
MIIDozCCAougAwIBAgIQAJeyjzkHgkQr5NcGvQ+ACTANBgkqhkiG9w0BAQsFADBq
MSswKQYDVQQLDCJDcmVhdGVkIGJ5IGh0dHA6Ly93d3cuZmlkZGxlcjIuY29tMRgw
FgYDVQQKDA9ET19OT1RfVFJVU1RfQkMxITAfBgNVBAMMGERPX05PVF9UUlVTVF9G
aWRkbGVyUm9vdDAeFw0yMDA5MDkwMDAwMDBaFw0zMDA5MTYxNjE2NTVaMGoxKzAp
BgNVBAsMIkNyZWF0ZWQgYnkgaHR0cDovL3d3dy5maWRkbGVyMi5jb20xGDAWBgNV
BAoMD0RPX05PVF9UUlVTVF9CQzEhMB8GA1UEAwwYRE9fTk9UX1RSVVNUX0ZpZGRs
ZXJSb290MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAm798LGRWPDQZ
U0P85V9FJx20QmqXbbi9IzqpLidRd94t+YKWo/aQxlq0pT8jo+P+Z2MPyKMIO7nZ
1N8v5XeTRWRemlvN2IDxsSYbK0Ta2rqf2svDGIR2FhKc/alEpwXwXVhUtdgV5HZh
nBhUNIsfjfjN88w0+yA1wwQlS4bGvh3xoZlgd+7OjuXGgBbH2gAufJ13MUSuZC3k
j0DD9ZwXzUWHpva59nejC5Wz4+tdpntXuyTx3gtyOxjkWfE2HU2clVKGeCtf3uof
06AHSzwUKv11iPNuEJtTMZJMV8BJnFbm0KHzj2w7C4qI7VfgdJUn+QjsOhd//5rF
yRbQdbCCUwIDAQABo0UwQzASBgNVHRMBAf8ECDAGAQH/AgEAMA4GA1UdDwEB/wQE
AwICBDAdBgNVHQ4EFgQUSaKduzG85wOAJiDJqN21En/VGCIwDQYJKoZIhvcNAQEL
BQADggEBAHmUVYDYE5Ezdw6sdfzA5siLD1XFY6Dzcao5Ei1uEqMdHB7RiGMSo1Zp
a3+ApDDjKMnoIG0DYhU92a/o/wlHWwmiJkMta8Or2nsG1vUZf/xv2tJmcAe++tBE
xTV1sOvjo4NhKztFyjYz0RSMB+3GFmxy5Yhr59jbOlKZRVEfRBuHBs+yFdzKcN2t
s0iSxct0hQRmrma4kiYIoU1s27G+WT0a3+J55V1i0Ujeirpj0llxzwXqhQzgzLai
kejvDvecP0UYPJTvzlDDpEqJ1+/qfBYOHsJZQcYG/Jt04Gn5uaMM/ijYZLURyktL
v9ILD4iYtLnkw52m8QUu+szxxLLD6oY=
-----END CERTIFICATE-----

Can't select my VPN connection

In the normal Fiddler program, I can select my VPN connection that I setup in Windows 10, but in the new Fiddler, there is no option in the settings to do that. and because of this, no connection is shown.

Deleting fiddler certificate

Hi

According to the post https://stackoverflow.com/questions/16827901/how-do-you-remove-the-root-ca-certificate-that-fiddler-installs the fiddler certificate can be removed . In Fiddler everywhere I do not see this option. When I try the certmgr.msc I see that I cannot find the fiddler certificate. How do I delete the fiddler certificate ?

[Tracking] Fiddler Everywhere Docs revamp

The Fiddler Everywhere documentation is in progress and the tracking issue is meant to track the overall progress of listing all features and functionalities. The documentation will require screenshots for the UI which should be taken on the MAC client.

Note: The screenshots used in the revamp branch are not fina and will be updated after the new release is ready.

Below is an example of the base navigation tree in the early stages. Ping me for any comments (e.g. about the structure or unlisted features).

The working branch will be deployed via a test Jenkins job and the current state can be seen here (live after a successfully Jenkins build)

• Introduction

  • Introduciton page

• Getting Started,

  • Requirments - list reqs for Windows, Mac, Linux
  • Installation - Installation procedure (download, install, login instructions)
    1. Windows (done)
    2. Mac OS
    3. Linux
  • Configuration
    • [ x] Capture Traffic
  • Inspect Traffic
  • Edit Traffic
  • Mock Server Response
  • Create API request
  • Collaboration
  • PRO vs Free version comparision

• User Guide

  • Fiddler's Main Menu

    • File
      - Load Archive OK
      - Save Archive OK
      - Import Sessions OK
      - Export Sessions OK
    • Help
      - Check for updates OK

  • Settings

    • HTTPS (In Progress)
      - Decrypt Secure traffic option (will this option be available )
      - Add trust certificate option
      - Export root certificate option
      - New option to enable HTTPS via the Web Sessions List "PROTOCOL" warning (see changes made by Nischal)
    • Connections
      - "Allow remote connection" option
    • Gateway
    • Privacy

  • Saved Sessions

    • Saved Sessions List
    • Share Sessions
    • Quotas (paid vs free)

  • Live Traffic

    • Web Sessions List
      - [x] Web Sessions context menu
      - [x] Web Sessions toolbar
      - [x] Live Traffic (capture switch)
      - [x] Stream
      - [x] Decode
      - [x] Pause
      - [x] Find
      - [x] Filter
      - [x] Share
      - [x] Save
      - [x] Remove
    • Inspectors tab
      - [x] Request Inspector (top)
      - [x] Response Inspector (bottom)
    • Auto Responder tab
      - [x] rules editor (left)
      - [x] create rule
      - [x] match
      - [x] actions
      - [x] queue viewer (right)
      - [x] grouping
      - [x] enabling
      - [x] import
      - [x] export
      - [x] pass-through
      - [x] options
      - [ ] quotas (paid vs free)

  • Composer

    • API methods
    • Testing APIs
      - Select API method
      - Enter URL
      - Under Headers, enter Authorization Key followed by the request body
      - Click on Execute
      - See the Response

  • Seeing quota for shared sessions (difference between paid and free version

• Use Cases

  • TODO: List articles for specific use stories here

• Copyright

  • Copyright page

• License

  • License page

• Knowledge Base

  • Update content

add support for drag and drop request

One of most used feature in old version is drag and drop request to composer and update the request field.
which is missing can you please add this in new version other i will keep on using old one.

How can I run this project locally?

How to reinstall Fiddler Everywhere on Ubuntu

When I first tried Fiddler Everywhere on my Ubuntu machine, I downloaded it to ~/Download
and ran it from there, accidentally agreeing to update the Applications folder etc.
This was to confirm that Fiddler Everywhere would run on Ubuntu.

Now knowing better, I wanted to move the AppImage to ~/programs and re-generate the Application links etc.
I can still run the AppImage directly but the Applications folder is no longer correct.

How do I reinstall Fiddler Everywhere and still trigger the updates to Application links?

Secure Protocol: Tls12

Encrypted HTTPS traffic flows through this CONNECT tunnel. HTTPS Decryption is enabled in Fiddler, so decrypted sessions running in this tunnel will be shown in the Web Sessions list.

Secure Protocol: Tls12
Cipher: Aes128 128bits
Hash Algorithm: None ?bits
Key Exchange: DiffieHellman 0bits

Crash on mac os 10.11

I am unable to launch Fiddler everywhere on mac os v10.11: it crashes systematically.

How to filter url in capturing list with fiddler-everywhere?

macOS Catalina
Succeed capturing, but I would like to show only specific sites.

Assumes path to Desktop is static

Hi.

When exporting ssl certificate fiddler assumes that the path is something like:
"C:\Users'username'\desktop"

The following error shows:
"Could not find part of the path"

However I use a different location for my desktop and no option is available to choose a specific destination to save the certificate.

Fiddler Root Certificate NOT trusted successfully

OS: Mac OS Big Sur 11.0.1
Fiddler Everywhere version: 1.2.1

I already followed the article https://docs.telerik.com/fiddler-everywhere/knowledge-base/how-to-install-fiddler-root-certificate-on-mac-os, but it still got fail "Fiddler Root Certificate NOT trusted successfully". I checked the cert in keychain, it's trusted.