From 98a7aaca182ce6b879329bbaeb06efca284c6220 Mon Sep 17 00:00:00 2001 From: Aldo Cortesi Date: Fri, 5 Aug 2011 10:23:32 +1200 Subject: Documentation. --- doc-src/sticky.html | 22 ++++++++++++++++------ 1 file changed, 16 insertions(+), 6 deletions(-) (limited to 'doc-src/sticky.html') diff --git a/doc-src/sticky.html b/doc-src/sticky.html index b2636890..6208f658 100644 --- a/doc-src/sticky.html +++ b/doc-src/sticky.html @@ -1,5 +1,11 @@ -When the __stickycookie__ option is set, __mitmproxy__ will add the cookie most +## Sticky cookies + +- command-line: _-t_ (sticky cookies on all requests) +- command-line: _-T filt_ (sticky cookies on requests matching filt) +- mitmproxy shortcut: _t_ + +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 @@ -17,8 +23,12 @@ with the secured resources. ## Sticky auth -The __stickyauth__ option is analogous to the __stickycookie__ 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. +- command-line: _-u_ (sticky auth on all requests) +- command-line: _-U filt_ (sticky auth on requests matching filt) +- mitmproxy shortcut: _u_ + +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. -- cgit v1.2.3