aboutsummaryrefslogtreecommitdiffstats
path: root/doc-src/anticache.html
diff options
context:
space:
mode:
authorAldo Cortesi <aldo@nullcube.com>2013-01-02 21:57:39 +1300
committerAldo Cortesi <aldo@nullcube.com>2013-01-02 21:57:39 +1300
commit8e6fabd69a124cc5b5ae763b58587ee6ee6ab3da (patch)
tree03fc66d5d94e5c82ddedd535c430cf9d71fd853a /doc-src/anticache.html
parent09f664cdeafae1d9923fe5ce2c4ab3acc7757a61 (diff)
downloadmitmproxy-8e6fabd69a124cc5b5ae763b58587ee6ee6ab3da.tar.gz
mitmproxy-8e6fabd69a124cc5b5ae763b58587ee6ee6ab3da.tar.bz2
mitmproxy-8e6fabd69a124cc5b5ae763b58587ee6ee6ab3da.zip
Docs - features.
Diffstat (limited to 'doc-src/anticache.html')
-rw-r--r--doc-src/anticache.html14
1 files changed, 11 insertions, 3 deletions
diff --git a/doc-src/anticache.html b/doc-src/anticache.html
index d97e9f5f..f42903e8 100644
--- a/doc-src/anticache.html
+++ b/doc-src/anticache.html
@@ -1,10 +1,18 @@
-- command-line: _--anticache_
-- mitmproxy shortcut: _o_, then _a_
-
When the __anticache__ option is passed to mitmproxy, it removes headers
(__if-none-match__ and __if-modified-since__) that might elicit a
304-not-modified response from the server. This is useful when you want to make
sure you capture an HTTP exchange in its totality. It's also often used during
[client replay](@!urlTo("clientreplay.html")!@), when you want to make sure the
server responds with complete data.
+
+<table class="table">
+ <tbody>
+ <tr>
+ <th width="20%">command-line</th> <td>--anticache</td>
+ </tr>
+ <tr>
+ <th>mitmproxy shortcut</th> <td><b>o</b> then <b>a</b></td>
+ </tr>
+ </tbody>
+</table>