aboutsummaryrefslogtreecommitdiffstats
path: root/doc-src/features/sticky.html
diff options
context:
space:
mode:
authorMaximilian Hils <git@maximilianhils.com>2015-07-30 10:47:12 +0200
committerMaximilian Hils <git@maximilianhils.com>2015-07-30 10:47:12 +0200
commitcdc84f52d213cb2b2b2a06a17378ebe757908865 (patch)
tree9e5b6b0d10a166ccf2b1867fe567b75704fd563d /doc-src/features/sticky.html
parentd2ae6b630e7924479aefbb9f0193fdfcbae8fea6 (diff)
parent3346daa65aa95db0b81c35827da037fbc3c87af7 (diff)
downloadmitmproxy-cdc84f52d213cb2b2b2a06a17378ebe757908865.tar.gz
mitmproxy-cdc84f52d213cb2b2b2a06a17378ebe757908865.tar.bz2
mitmproxy-cdc84f52d213cb2b2b2a06a17378ebe757908865.zip
Merge pull request #699 from onlywade/bugfix/docs_update_shortcut_keys
Update docs to reflect current shortcut keys for features which have …
Diffstat (limited to 'doc-src/features/sticky.html')
-rw-r--r--doc-src/features/sticky.html8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc-src/features/sticky.html b/doc-src/features/sticky.html
index 59116067..18e6a4c5 100644
--- a/doc-src/features/sticky.html
+++ b/doc-src/features/sticky.html
@@ -9,7 +9,7 @@ using a browser. After authentication, you can request authenticated resources
through mitmproxy as if they were unauthenticated, because mitmproxy will
automatically add the session tracking cookie to requests. Among other things,
this lets you script interactions with authenticated resources (using tools
-like wget or curl) without having to worry about authentication.
+like wget or curl) without having to worry about authentication.
Sticky cookies are especially powerful when used in conjunction with [client
replay](@!urlTo("clientreplay.html")!@) - you can record the authentication
@@ -27,7 +27,7 @@ with the secured resources.
</td>
</tr>
<tr>
- <th>mitmproxy shortcut</th> <td><b>t</b></td>
+ <th>mitmproxy shortcut</th> <td><b>o</b> then <b>t</b></td>
</tr>
</tbody>
</table>
@@ -39,7 +39,7 @@ The sticky auth option is analogous to the sticky cookie option, in that HTTP
__Authorization__ headers are simply replayed to the server once they have been
seen. This is enough to allow you to access a server resource using HTTP Basic
authentication through the proxy. Note that __mitmproxy__ doesn't (yet) support
-replay of HTTP Digest authentication.
+replay of HTTP Digest authentication.
<table class="table">
<tbody>
@@ -52,7 +52,7 @@ replay of HTTP Digest authentication.
</td>
</tr>
<tr>
- <th>mitmproxy shortcut</th> <td><b>u</b></td>
+ <th>mitmproxy shortcut</th> <td><b>o</b> then <b>A</b></td>
</tr>
</tbody>
</table>