diff options
author | Aldo Cortesi <aldo@nullcube.com> | 2014-01-27 14:16:23 +1300 |
---|---|---|
committer | Aldo Cortesi <aldo@nullcube.com> | 2014-01-27 14:16:23 +1300 |
commit | f47d89ff4e710f6d2df755fe526e91a5cf236cfa (patch) | |
tree | 61c35a397e569619ae7022fb006279d86a0d88eb /doc-src/features/sticky.html | |
parent | 47c7e37723b416605f232cd85818f41d865a9f85 (diff) | |
download | mitmproxy-f47d89ff4e710f6d2df755fe526e91a5cf236cfa.tar.gz mitmproxy-f47d89ff4e710f6d2df755fe526e91a5cf236cfa.tar.bz2 mitmproxy-f47d89ff4e710f6d2df755fe526e91a5cf236cfa.zip |
Revert "Move the doc tree out into its own repo."
This reverts commit 8f88fcedd601c0033b4469b66626a83011879baf.
Diffstat (limited to 'doc-src/features/sticky.html')
-rw-r--r-- | doc-src/features/sticky.html | 60 |
1 files changed, 60 insertions, 0 deletions
diff --git a/doc-src/features/sticky.html b/doc-src/features/sticky.html new file mode 100644 index 00000000..59116067 --- /dev/null +++ b/doc-src/features/sticky.html @@ -0,0 +1,60 @@ + +## Sticky cookies + +When the sticky cookie option is set, __mitmproxy__ will add the cookie most +recently set by the server to any cookie-less request. Consider a service that +sets a cookie to track the session after authentication. Using sticky cookies, +you can fire up mitmproxy, and authenticate to a service as you usually would +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. + +Sticky cookies are especially powerful when used in conjunction with [client +replay](@!urlTo("clientreplay.html")!@) - you can record the authentication +process once, and simply replay it on startup every time you need to interact +with the secured resources. + +<table class="table"> + <tbody> + <tr> + <th width="20%">command-line</th> + <td> + <ul> + <li>-t FILTER</li> + </ul> + </td> + </tr> + <tr> + <th>mitmproxy shortcut</th> <td><b>t</b></td> + </tr> + </tbody> +</table> + + +## Sticky auth + +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. + +<table class="table"> + <tbody> + <tr> + <th width="20%">command-line</th> + <td> + <ul> + <li>-u FILTER</li> + </ul> + </td> + </tr> + <tr> + <th>mitmproxy shortcut</th> <td><b>u</b></td> + </tr> + </tbody> +</table> + + |