Tools: About Fiddler

The Fiddler Web Debugging Proxy is a free tool that works with any browser, system or platform. Use Fiddler to monitor HTTP/HTTPs traffic from a browser, inspect and then debug traffic from a client and then manipulate and edit web sessions.

Download

Download the Fiddler installation file from: http://www.telerik.com/download/fiddler

Install

1. Click the installation file or choose Run depending on your browser.
2. Review the license agreement and click I Agree.
3. Click Install to accept the default destination folder or Browse to another folder.
4. A confirmation box appears when the installation is complete. Click Close.

Configure

To configure Fiddler for your environment, see the documentation at: http://docs.telerik.com/fiddler/Configure-Fiddler/Tasks/ConfigureFiddler

Viewing Traffic

When you launch Fiddler, all traffic appears in the left pane. You can search this list, example: search for the Bootstrap.js file:

1. Click Find or CTRL + F to see the search dialog.
2. Enter nexus in the Find input box and click Find Sessions.
3. Click the Inspectors tab in the right pane.
4. Click Text View in the lower pane.

Blocking Traffic (Blacklisting)

To use Fiddler to block content from URLs you must download and install the Content Blocking Add-on as follows:

1. Navigate to http://www.telerik.com/fiddler/add-ons
2. Scroll until you find Content Blocking and click Download
3. Follow the instructions in the Readme_ContentBlocker.txt file for your environment.
4. Launch Fiddler. Select the new Content Block option on menu bar the following options are available:
   1. Click to select Enabled when you wish to use ContentBlock. A checkmark appears next to Enabled. Other options become active when ContentBlock is enabled. Click again to remove the checkmark and disable.
   2. Block Paths - controls whether Fiddler will block requests whose URL path component contains /ad/, /ads/, or /advert.
   3. Edit Blocked Hosts - allows you to modify the list of hostnames to which all requests are blocked.
   4. Always Block Flash - block all requests issued by Flash plugin.
   5. Block X-Domain Flash - block download of .SWF files when the SWF file is hosted by a domain other than the requestors RefererHTTP header.
   6. Short-Circuit Redirects - Fiddler attempts to detect URLs that might be used only for logging purposes. For example, http://example.com/logger.php?goto=http://targetsite.com/page123.htm). When Fiddler sees this request, it strips off the front of the URL and returns a HTTP/307 redirection to the target site, causing the request to bypass the logging page.
   7. Hide Blocked Sessions - controls whether Fiddler hides blocked requests from the Session list. If not set, the blocked requests are listed using a strikethrough font.

Blocking (Blacklisting) Ensighten for Testing

Stop the Ensighten script from loading on web pages without Ensighten tagging.

1. Select Content Block.
2. Choose Block Paths.
3. Enter the Bootstrap path to block:
   1. DEV: //nexus.ensighten.com/accountname/dev/Bootstrap.js
   2. STAGE: //nexus.ensighten.com/accountname/stage/Bootstrap.js
   3. PROD: //nexus.ensighten.com/accountname/prod/Bootstrap.js OR //nexus.ensighten.com/accountname/Bootstrap.js (depending on how your company implemented the Bootstrap)
4. Click OK.

Local Code Rewrite

Rewrite allows you to modify, that is, rewrite the Bootstrap of the site to a different version.

1. Launch Fiddler
2. Click Rules and then choose Customize Rules or (CTRL + R)
3. Locate the OnBeforeRequest function.
4. Insert the following code:

   if (oSession.uriContains("nexus.ensighten.com")) {      oSession.host = "nexus-test.ensighten.com"; }

5. Save the file.

The site will now use the local copy of the code. Close Fiddler or remove the added code when you are ready to revert to the production or existing Bootstrap version.