diff options
| author | Aldo Cortesi <aldo@nullcube.com> | 2010-02-16 17:09:07 +1300 |
|---|---|---|
| committer | Aldo Cortesi <aldo@nullcube.com> | 2010-02-16 17:09:07 +1300 |
| commit | cb0e3287090786fad566feb67ac07b8ef361b2c3 (patch) | |
| tree | 0cce85760f1811bc3bbd00245764142621fa9d16 /doc-src/faq.html | |
| download | mitmproxy-cb0e3287090786fad566feb67ac07b8ef361b2c3.tar.gz mitmproxy-cb0e3287090786fad566feb67ac07b8ef361b2c3.tar.bz2 mitmproxy-cb0e3287090786fad566feb67ac07b8ef361b2c3.zip | |
Initial checkin.
Diffstat (limited to 'doc-src/faq.html')
| -rw-r--r-- | doc-src/faq.html | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/doc-src/faq.html b/doc-src/faq.html new file mode 100644 index 00000000..8b0a3ff5 --- /dev/null +++ b/doc-src/faq.html @@ -0,0 +1,17 @@ + +<div class="faq"> + + <p class="question">On some sites I see a lot of "Connection from.." + entries that never complete.</p> + + <p> This is probably because the page requests resources from SSL-protected + domains. These requests are intercepted by mitmproxy, but because we're + using a bogus certificate, the browser-side of the connection hangs. The + browser doesn't prompt you to add a certificate trust exception for remote + page components, only for the primary domain being visited. </p> + + <p> To solve this, use something like FireBug to find out which page + components are hanging. Visit the relevant domains using your browser, and + add a certificate trust exception for each one. </p> + +</div> |