Docs, minor cert tweaks.

1 files changed, 14 insertions, 0 deletions

diff --git a/doc-src/stickycookies.html b/doc-src/stickycookies.html
index b28b04f6..5aa5045c 100644
--- a/doc-src/stickycookies.html
+++ b/doc-src/stickycookies.html
@@ -1,3 +1,17 @@
 
+When the __stickycookie__ 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.