Keywords: fiddler | traffic capture | filter settings | troubleshooting
Abstract: This article explores common reasons why Fiddler may stop capturing browser traffic, focusing on a subtle issue with the 'Use Filters' checkbox. Based on user experiences and best answers, step-by-step solutions and additional troubleshooting tips are provided to restore functionality and optimize debugging workflows.
Problem Description
Fiddler users often rely on it for monitoring HTTP and HTTPS traffic, but sudden failures can occur. For instance, with Chrome 29 and Fiddler v4.4.5.1, users may find that no traffic is captured despite all filters and rules being turned off. According to the best answer, this can be due to a hidden issue in filter settings.
Root Cause Analysis
In Fiddler's filters tab, the “Use Filters” checkbox might block all traffic even when all individual filter rules are disabled. This is a common defect; simply unchecking this box can restore normal capture.
Step-by-Step Resolution
- Open Fiddler and navigate to the Filters tab.
- Ensure the “Use Filters” checkbox is unchecked. If checked, uncheck it.
- Restart Fiddler or the browser and check if traffic is being captured.
Additional Troubleshooting Steps
Other factors may contribute:
- Browser Extensions: Extensions like Hola or Proxy SwitchySharp can override proxy settings. Try disabling or removing them.
- System Proxy Settings: Verify in WinINET Options that the proxy is set to 127.0.0.1:8888. Running Fiddler as Administrator may help.
- Firewall or Security Software: Ensure no software is blocking connections to Fiddler's port.
Conclusion
By understanding the interplay between Fiddler's filter settings and system configurations, users can quickly resolve capture issues and maintain effective debugging. If problems persist, refer to more detailed troubleshooting techniques.