Docs builder

configure-fiddler/advanced-options/_meta.yml

@@ -0,0 +1,2 @@
+title: Advanced Capturing Options
+position: 200

configure-fiddler/advanced-options/authenticatewithcbt.md

@@ -0,0 +1,49 @@
+---
+title: Authentication to CBT-Protected Server
+description: Configure Fiddler Classic to Authenticate to CBT-Protected Server
+slug: AuthenticateWithCBT
+publish: true
+position: 21
+previous_url: /configure-fiddler/tasks/authenticatewithcbt
+---
+
+# Configure Fiddler Classic to Authenticate to CBT-Protected Server
+
+1. Click **Rules > Customize Rules**.
+2. Scroll to the **OnPeekAtResponseHeaders** function.
+3. Add the following code:
+	```c#
+	static function OnPeekAtResponseHeaders(oSession: Session) 
+	{         
+		// To avoid problems with Channel-Binding-Tokens, this block allows Fiddler Classic 
+		// itself to respond to Authentication challenges from HTTPS Intranet sites. 
+		if (oSession.isHTTPS && 
+			(oSession.responseCode == 401) && 
+			// Only permit auto-auth for local apps (e.g. not devices or remote PCs) 
+			(oSession.LocalProcessID > 0) && 
+			// Only permit auth to sites we trust 
+			(Utilities.isPlainHostName(oSession.hostname) 
+			// Replace telerik.com with whatever servers Fiddler Classic should release credentials to.
+			|| oSession.host.EndsWith("telerik.com"))  
+			) 
+		{ 
+			// To use creds other than your Windows login credentials, 
+			// set X-AutoAuth to "domain\\username:password" 
+			// Replace default with specific credentials in this format:
+			// domain\\username:password. 
+			oSession["X-AutoAuth"] = "(default)";    
+			oSession["ui-backcolor"] = "pink"; 
+		} 
+
+	//... function continues
+	```
+
+	* Replace "telerik.com" with whatever servers Fiddler Classic should release credentials to. By default, Fiddler Classic will release credentials to any intranet sites (sites without a dot in the hostname).
+
+	* Replace "default" with specific credentials in this format:
+
+		```txt
+		domain\\username:password
+		```	 
+
+	* If you specify "(default)", Fiddler Classic will attempt to use the login credentials of whatever user-account that it is running under.

configure-fiddler/tasks/bypassupstreamproxy.md → configure-fiddler/advanced-options/bypassupstreamproxy.md

@@ -4,16 +4,16 @@ description: Configuration code to bypass the upstream proxy for all requests to
 slug: BypassUpstreamProxy
 publish: true
 position: 23
+previous_url: /configure-fiddler/tasks/bypassupstreamproxy
 ---
 
-Bypass the Upstream Proxy
-=========================
+# Bypass the Upstream Proxy
 
-To bypass the upstream proxy for all requests to a specific domain (for example, to emulate the IE Proxy bypass list), [add a rule to Fiddler][1] to the **OnBeforeRequest** function as follows:
+To bypass the upstream proxy for all requests to a specific domain (for example, to emulate the IE Proxy bypass list), [add a rule to Fiddler](slug://AddRules) to the **OnBeforeRequest** function as follows:
 
-		if (oSession.HostnameIs("www.example.com")){
-		oSession.bypassGateway = true;
-		}
-
-[1]: ../../Extend-Fiddler/AddRules
+```c#
+if (oSession.HostnameIs("www.example.com")){
+oSession.bypassGateway = true;
+}
+```
 

configure-fiddler/tasks/capturetrafficfromadifferentaccount.md → configure-fiddler/advanced-options/capturetrafficfromadifferentaccount.md

@@ -4,19 +4,14 @@ description: Use Fiddler Classic to capture Traffic from an ASP.NET on IIS or fr
 slug: CaptureTrafficFromDifferentAccount
 publish: true
 position: 14
+previous_url: /configure-fiddler/tasks/capturetrafficfromadifferentaccount
 ---
 
-Capture Traffic from a Different Account
-========================================
+# Capture Traffic from a Different Account
 
 To capture traffic from accounts other than the current user (for example, ASP.NET on IIS or a Windows Service), configure that process to use the Fiddler Classic proxy.
 
-For Example
-----------------
+For example:
 
-[Configure .NET Applications][1]
-
-[Configure WinHTTP Applications][2]
-
-[1]: ./ConfigureDotNETApp
-[2]: ./ConfigureWinHTTPApp
+[Configure .NET Applications](slug://DotNETConfig)
+[Configure WinHTTP Applications](slug://ConfigureWinHTTPApp)

configure-fiddler/tasks/chaintoupstreamproxy.md → configure-fiddler/advanced-options/chaintoupstreamproxy.md

@@ -4,31 +4,18 @@ description: Configure Fiddler Classic to send and receive web traffic to and fr
 slug: ChainToUpstreamProxy
 publish: true
 position: 12
+previous_url: /configure-fiddler/tasks/chaintoupstreamproxy
 ---
 
-Chain Fiddler Classic to an Upstream Proxy
-==================================
+# Chain Fiddler Classic to an Upstream Proxy
 
 To configure Fiddler Classic to send and receive web traffic to and from another proxy between Fiddler Classic and the destination server:
 
 1. Close Fiddler Classic application.
-
 2. Open **Internet Explorer** > **Options** > **Internet Options** > **Connections** > **LAN Settings**.
-
 3. Click the check box by **Use a proxy server for your LAN**.
-
- ![Set proxy address][1]
-
+ ![Set proxy address](./images/SetProxyAddress.jpg)
 4. Type the address and port number for the upstream proxy.
-
 5. Restart Fiddler Classic application.
 
 You should now see the upstream proxy listed in the Fiddler Classic **About** dialog.
-
-See Also
---------
-
-+ [Understanding the Fiddler Classic Proxy][2]
-
-[1]: ../../images/ChainToUpstreamProxy/SetProxyAddress.jpg
-[2]: ../../KnowledgeBase/Proxy

configure-fiddler/tasks/fiddler-logging.md → configure-fiddler/advanced-options/fiddler-logging.md

@@ -4,6 +4,7 @@ description: Configure Fiddler Classic to log specific data with FiddlerScript
 slug: fiddler-logging-fiddlerscript
 publish: true
 position: 35
+previous_url: /configure-fiddler/tasks/fiddler-logging
 ---
 
 # Logging in Fiddler Classic
@@ -16,14 +17,12 @@ From FiddlerScript, you can do this:
 FiddlerObject.log("Your message here");
 ```
 
-
 From a Fiddler extension, do this:
 ```c#
 FiddlerApplication.Log.LogString("Your message here");
 ```
 
 If you want to get copies of log messages, write the following code in your extension:
-
 ```c#
    FiddlerApplication.Log.OnLogString += new EventHandler<LogEventArgs>(YourEventHandler);
 ```

configure-fiddler/tasks/fiddler-preferences.md → configure-fiddler/advanced-options/fiddler-preferences.md

@@ -4,6 +4,7 @@ description: List of Fiddler CLassic configurable preferences
 slug: fiddler-classic-preferences
 publish: true
 position: 30
+previous_url: /configure-fiddler/tasks/fiddler-preferences
 ---
 
 # Preferences in Fiddler Classic
@@ -23,7 +24,7 @@ fiddler.debug.extensions.verbose = "True"
 ```
 
 Controls whether the Fiddler Toolbar is visible:
-```
+```bash
 fiddler.ui.toolbar.visible = "True"
 ```
 
@@ -68,7 +69,6 @@ Set to "True" to cause Fiddler to abort a download if streaming the response to
 fiddler.network.streaming.abortifclientaborts = "False"
 ```
 
-
 Set to "True" to cause Fiddler to "forget" received bytes if they are streamed to the client. Similar to the SessionFlag 
 log-drop-response-body, but forgetting occurs during streaming rather than upon response completion:
 ```bash
@@ -90,27 +90,23 @@ Number of milliseconds Fiddler should keep a DNS cache entry in its cache:
 fiddler.network.timeouts.dnscache = 150000
 ```
 
-
 When CTRL+X is hit, keep sessions that are either in progress, or marked (at a breakpoint, or with a comment, or with a mark color set)
 ```bash
 fiddler.ui.CtrlX.KeepMarked = True
 ```
 
-
 Force Fiddler to always use the RAW request inspector when double-clicking or hitting ENTER on a session:
 ```bash
 fiddler.ui.inspectors.request.alwaysuse = "Raw"
 ```
 
-
 Force Fiddler to always use the SyntaxView response inspector when double-clicking or hitting ENTER on a session:
 ```bash
 fiddler.ui.inspectors.response.alwaysuse = "SyntaxView"
 ```
 
 ** FULL LIST of all preferences in Fiddler Classic**
 
-
 ```bash
 addons.ericlaw.hosts.enabled
 addons.ImageBloat.EmbedAsText

configure-fiddler/tasks/monitordialupandvpn.md → configure-fiddler/advanced-options/monitordialupandvpn.md

@@ -4,23 +4,19 @@ description: "Instructions for monitoring traffic via dial-up and VPN in Fiddler
 slug: MonitorDialupAndVPN
 publish: true
 position: 10
+previous_url: /configure-fiddler/tasks/monitordialupandvpn
 ---
 
-Monitor RAS, VPN or Dialup Connections
-======================================
+# Monitor RAS, VPN or Dialup Connections
 
 To monitor a dialup or VPN connection, open **Tools -> Options...** and click **Monitor all connections**.
 
-![Monitor all connections][1]
+![Monitor all connections](./images/MonitorAllConnections.png)
 
-Or, set [the "Use automatic configuration script" option][2] in your browser.
+Or, set [the "Use automatic configuration script" option](slug://ConfigureBrowsers) in your browser.
 
 To monitor a VPN or dialup connection that is always active (instead of a LAN connection), set the **HookConnectionNamed** registry value to the name of the connection from **Internet Options**. 
 
-![Connection Name][3]
+![Connection Name](./images/ConnectionName.png)
 
-Note: IE will always use the proxy settings from any active VPN connection, whether or not that VPN connects to the Internet.
-
-[1]: ../../images/MonitorDialupAndVPN/MonitorAllConnections.png
-[2]: ./ConfigureBrowsers
-[3]: ../../images/MonitorDialupAndVPN/ConnectionName.png
+Note: IE will always use the proxy settings from any active VPN connection, whether or not that VPN connects to the Internet.

configure-fiddler/tasks/monitorpocketpc.md → configure-fiddler/advanced-options/monitorpocketpc.md

@@ -4,33 +4,22 @@ description: Configuration for setting Fiddler Classic on PocketPC
 slug: MonitorPocketPC
 publish: true
 position: 20
+previous_url: /configure-fiddler/tasks/monitorpocketpc
 ---
 
-Monitor PocketPC
-================
+# Monitor PocketPC
 
-Configure Fiddler Classic
------------------
-
-1. On the Fiddler Classic server (the machine where Fiddler Classic is installed), [open port 8888 in Windows Firewall][1].
+## Configure Fiddler Classic
 
+1. On the Fiddler Classic server (the machine where Fiddler Classic is installed), open port **8888** in Windows Firewall.
 2. Open **ActiveSync > Connection Settings...**. 
-
 3. Under **This Computer is connected to:**, click **Work Network**.
-
 4. Start Fiddler.
-
 5. Click **Tools > Options...**.
-
 6. Ensure "Allow remote clients to connect" is checked. 
-
 7. If you need to click the checkbox, restart Fiddler.
 
-Configure PocketPC
-------------------
+## Configure PocketPC
 
 1. On the PocketPC, set the HTTP proxy to be **FIDDLERSERVER:8888**, where FIDDLERSERVER is the machine name for the machine with Fiddler Classic installed.
-
 2. Connect the PocketPC to ActiveSync.
-
-[1]: http://windows.microsoft.com/en-us/windows7/open-a-port-in-windows-firewall

configure-fiddler/tasks/monitorwindowsphone7.md → configure-fiddler/advanced-options/monitorwindowsphone7.md

@@ -3,90 +3,55 @@ title: Monitor Windows Phone
 slug: MonitorWindowsPhone7
 publish: true
 position: 19
+previous_url: /configure-fiddler/tasks/monitorwindowsphone7
 ---
 
-Monitor Windows Phone
-=====================
+# Monitor Windows Phone
 
-Configure Fiddler
------------------
+## Configure Fiddler
 
 1. Start Fiddler Classic on the Fiddler server (the machine that will capture the traffic).
-
 2. Click **Tools > Options**. Click **Allow remote clients to connect**. 
-
- ![Allow remote clients to connect][1]
-
+ ![Allow remote clients to connect](./images/AllowRemoteComputersToConnect.png)
 3. Restart Fiddler.
-
 4. In the Windows Security Alert dialog, check all three checkboxes and click the **Allow Access** button.
-
- ![Windows Security Alert][2]
+ ![Windows Security Alert](./images/WindowsSecurityAlert.png)
 
 To verify this configuration, enable your Windows Phone WiFi connection and visit **http://FIDDLERSERVER:8888**, where FIDDLERSERVER is the machine name for the machine running Fiddler. This should display the **Fiddler Echo Service** web site.
 
-Configure Windows Phone
------------------------
+## Configure Windows Phone
 
 1. Tap **Settings > WiFi**.
-
- ![Settings][3]
-
+ ![Settings](./images/Settings.png)
 2. Tap the active WiFi connection.
-
- ![WiFi][4]
-
+ ![WiFi](./images/Wifi.png)
 3. Slide the **Proxy Slider** to **On**.
-
 4. In the **Server/URL** field, type the machine name for the Fiddler server.
-
 5. In the **Port** field, type **8888**.
-
- ![EditNetwork.png][5]
-
+ ![EditNetwork.png](./images/EditNetwork.png)
 6. Tap the checkmark icon.
 
-Decrypt HTTPS Traffic
----------------------
-1. [Configure Fiddler Classic to decrypt HTTPS traffic][6].
+## Decrypt HTTPS Traffic
 
+1. [Configure Fiddler Classic to decrypt HTTPS traffic](slug://DecryptHTTPS).
 2. On the Windows Phone, use Mobile IE to request an HTTPS protocol URL.
-
-3. Go to **http://FIDDLERSERVER:8888/FiddlerRoot.cer**.
-
+3. Go to `http://FIDDLERSERVER:8888/FiddlerRoot.cer`.
 4. Tap the icon labeled **Tap to open the file fiddlerroot.cer**.
-
- ![Open Certificate][8]
-
+ ![Open Certificate](./images/OpenCertificate.png)
 5. Tap **install**.
-
- ![Install Certificate][9]
+ ![Install Certificate](./images/InstallCertificate.png)
 
 Note: There is no known resource containing steps to remove security certificates from a Windows Phone. This may prevent connecting to a different Fiddler proxy, which will use a different security certificate.
 
-Disable Monitoring
-------------------
+## Disable Monitoring
+
 After Fiddler Classic monitoring is complete:
 
 1. Tap **Settings > WiFi**.
-
 2. Tap the active WiFi connection.
-
 3. Slide the **Proxy Slider** to **Off**.
 
+## See Also
 
+[No Windows Phone 7 traffic](slug://NoWindowsPhone7Traffic)
 
-See Also
---------
-[No Windows Phone 7 traffic][10]
-
-[1]: ../../images/MonitorWindowsPhone7/AllowRemoteComputersToConnect.png
-[2]: ../../images/MonitorWindowsPhone7/WindowsSecurityAlert.png
-[3]: ../../images/MonitorWindowsPhone7/Settings.png
-[4]: ../../images/MonitorWindowsPhone7/Wifi.png
-[5]: ../../images/MonitorWindowsPhone7/EditNetwork.png
-[6]: ./DecryptHTTPS
-[7]: ../../images/MonitorWindowsPhone7/CertificateWarning.png
-[8]: ../../images/MonitorWindowsPhone7/OpenCertificate.png
-[9]: ../../images/MonitorWindowsPhone7/InstallCertificate.png
-[10]: ../Troubleshooting/NoWindowsPhone7Traffic