Tweak and version bump to fix pip installation issues due to new Urwid.

.appveyor.yml

@@ -1,77 +0,0 @@
-version: '{build}'
-build: off  # Not a C# project
-
-environment:
-  CI_DEPS: codecov>=2.0.5
-  CI_COMMANDS: codecov
-  matrix:
-    - PYTHON: "C:\\Python35"
-      TOXENV: "py35"
-    # TODO: ENABLE WHEN AVAILABLE
-    # - PYTHON: "C:\\Python36"
-    #   TOXENV: "py36"
-
-  SNAPSHOT_HOST:
-    secure: NeTo57s2rJhCd/mjKHetXVxCFd3uhr8txnjnAXD1tUI=
-  SNAPSHOT_PORT:
-    secure: TiJPtg60/edYTH8RnoBErg==
-  SNAPSHOT_USER:
-    secure: 6yBwmO5gv4vAwoFYII8qjQ==
-  SNAPSHOT_PASS:
-    secure: LPjrtFrWxYhOVGXzfPRV1GjtZE/wHoKq9m/PI6hSalfysUK5p2DxTG9uHlb4Q9qV
-  RTOOL_KEY:
-    secure: 0a+UUNbA+JjquyAbda4fd0JmiwL06AdG6torRPdCvbPDbKHnaW/BHHp1nRPytOKM
-
-install:
-  - "SET PATH=%PYTHON%;%PYTHON%\\Scripts;%PATH%"
-  - "python -m pip install --disable-pip-version-check -U pip"
-  - "pip install -U tox"
-
-test_script:
-  - ps: "tox -- --verbose --cov-report=term"
-  - ps: |
-      $Env:VERSION = $(python mitmproxy/version.py)
-      $Env:SKIP_MITMPROXY = "python -c `"print('skip mitmproxy')`""
-      tox -e wheel
-      tox -e rtool -- bdist
-
-  - ps: |
-      if(
-        ($Env:TOXENV -match "py35") -and !$Env:APPVEYOR_PULL_REQUEST_NUMBER -and
-        (($Env:APPVEYOR_REPO_BRANCH -In ("master", "pyinstaller")) -or ($Env:APPVEYOR_REPO_TAG -match "true"))
-      ) {
-        tox -e rtool -- decrypt release\installbuilder\license.xml.enc release\installbuilder\license.xml
-        if (!(Test-Path "C:\projects\mitmproxy\release\installbuilder-installer.exe")) {
-          "Download InstallBuilder..."
-          (New-Object System.Net.WebClient).DownloadFile(
-            "https://installbuilder.bitrock.com/installbuilder-enterprise-17.1.0-windows-installer.exe",
-            "C:\projects\mitmproxy\release\installbuilder-installer.exe"
-          )
-        }
-        Start-Process "C:\projects\mitmproxy\release\installbuilder-installer.exe" "--mode unattended --unattendedmodeui none" -Wait
-        & 'C:\Program Files (x86)\BitRock InstallBuilder Enterprise 17.1.0\bin\builder-cli.exe' `
-          build `
-          .\release\installbuilder\mitmproxy.xml `
-          windows `
-          --license .\release\installbuilder\license.xml `
-          --setvars project.version=$Env:VERSION `
-          --verbose
-      }
-
-deploy_script:
-  # we build binaries on every run, but we only upload them for master snapshots or tags.
-  ps: |
-    if(
-      ($Env:TOXENV -match "py35") -and
-      (($Env:APPVEYOR_REPO_BRANCH -In ("master", "pyinstaller")) -or ($Env:APPVEYOR_REPO_TAG -match "true"))
-    ) {
-      tox -e rtool -- upload-snapshot --bdist --wheel --installer
-    }
-
-cache:
-  - C:\projects\mitmproxy\release\installbuilder-installer.exe -> .appveyor.yml
-  - C:\Users\appveyor\AppData\Local\pip\cache
-
-notifications:
-  - provider: Slack
-    incoming_webhook: https://hooks.slack.com/services/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

.codecov.yml

@@ -1 +0,0 @@
-comment: off

.gitattributes

@@ -1,2 +0,0 @@
-mitmproxy/tools/web/static/**/* -diff linguist-vendored
-web/src/js/filt/filt.js -diff

.gitignore

@@ -1,23 +1,12 @@
-.DS_Store
 MANIFEST
-**/tmp
-/venv*
+/build
+/dist
+/tmp
+/doc
 *.py[cdo]
 *.swp
 *.swo
-*.egg-info/
-.coverage*
-.idea
-.cache/
-.tox*/
-build/
-
-# UI
-
-node_modules
-bower_components
-*.map
-sslkeylogfile.log
-.tox/
-.python-version
-coverage.xml
+mitmproxyc
+mitmdumpc
+mitmplaybackc
+mitmrecordc

.landscape.yml

@@ -1,20 +0,0 @@
-ignore-paths:
-  - docs
-  - examples
-  - mitmproxy/contrib
-  - web
-max-line-length: 140
-pylint:
-  options:
-    dummy-variables-rgx: _$|.+_$|dummy_.+
-  disable:
-    - missing-docstring
-    - protected-access
-    - too-few-public-methods
-    - too-many-arguments
-    - too-many-instance-attributes
-    - too-many-locals
-    - too-many-public-methods
-    - too-many-return-statements
-    - too-many-statements
-    - unpacking-non-sequence

.travis.yml

@@ -1,94 +0,0 @@
-sudo: false
-language: python
-
-env:
-  global:
-    - CI_DEPS=codecov>=2.0.5
-    - CI_COMMANDS=codecov
-git:
-  depth: 10000
-
-matrix:
-  fast_finish: true
-  include:
-    - python: 3.5
-      env: TOXENV=lint
-    - os: osx
-      osx_image: xcode7.3
-      language: generic
-      env: TOXENV=py35 BDIST=1
-    - python: 3.5
-      env: TOXENV=py35 OPENSSL_OLD
-      addons:
-        apt:
-          packages:
-            - libssl-dev
-    - python: 3.5
-      env: TOXENV=py35 BDIST=1 OPENSSL_ALPN
-      addons:
-        apt:
-          sources:
-            # Debian sid currently holds OpenSSL 1.1.0
-            # change this with future releases!
-            - debian-sid
-          packages:
-            - libssl-dev
-    - python: 3.6
-      env: TOXENV=py36 OPENSSL_ALPN
-      addons:
-        apt:
-          sources:
-            # Debian sid currently holds OpenSSL 1.1.0
-            # change this with future releases!
-            - debian-sid
-          packages:
-            - libssl-dev
-    - python: 3.5
-      env: TOXENV=individual_coverage
-    - python: 3.5
-      env: TOXENV=docs
-
-install:
-  - |
-    if [[ $TRAVIS_OS_NAME == "osx" ]]
-    then
-      brew update || brew update
-      brew outdated pyenv || brew upgrade pyenv
-      eval "$(pyenv init -)"
-      env PYTHON_CONFIGURE_OPTS="--enable-framework" pyenv install --skip-existing 3.5.2
-      pyenv global 3.5.2
-      pyenv shell 3.5.2
-      pip install -U pip setuptools wheel virtualenv
-    fi
-  - pip install tox
-
-script:
-  - tox -- --verbose --cov-report=term
-  - |
-    if [[ $BDIST == "1" ]]
-    then
-        git fetch --unshallow --tags
-        tox -e rtool -- bdist
-    fi
-
-after_success:
-  # we build binaries on every run, but we only upload them for master snapshots or tags.
-  - |
-    if [[ $BDIST == "1" && $TRAVIS_PULL_REQUEST == "false" && ($TRAVIS_BRANCH == "pyinstaller" || $TRAVIS_BRANCH == "master" || -n $TRAVIS_TAG) ]]
-    then
-        tox -e rtool -- upload-snapshot --bdist
-    fi
-
-notifications:
-  slack:
-      -rooms:
-          mitmproxy:YaDGC9Gt9TEM7o8zkC2OLNsu
-      on_success: change
-      on_failure: change
-      on_start: never
-
-cache:
-  directories:
-    - $HOME/.pyenv
-    - $HOME/.cache/pip
-    # - $HOME/build/mitmproxy/mitmproxy/.tox

CHANGELOG

@@ -1,566 +1,3 @@
-28 April 2017: mitmproxy 2.0.2
-
-    * Fix mitmweb's Content-Security-Policy to work with Chrome 58+
-
-    * HTTP/2: actually use header normalization from hyper-h2
-
-
-15 March 2017: mitmproxy 2.0.1
-
-    * bump cryptography dependency
-
-    * bump pyparsing dependency
-
-    * HTTP/2: use header normalization from hyper-h2
-
-
-21 February 2017: mitmproxy 2.0
-
-    * HTTP/2 is now enabled by default.
-
-    * Image ContentView: Parse images with Kaitai Struct (kaitai.io) instead of Pillow. 
-      This simplifies installation, reduces binary size, and allows parsing in pure Python.
-
-    * Web: Add missing flow filters.
-
-    * Add transparent proxy support for OpenBSD.
-
-    * Check the mitmproxy CA for expiration and warn the user to regenerate it if necessary.
-
-    * Testing: Tremendous improvements, enforced 100% coverage for large parts of the 
-      codebase, increased overall coverage.
-
-    * Enforce individual coverage: one source file -> one test file with 100% coverage.
-
-    * A myriad of other small improvements throughout the project.
-
-    * Numerous bugfixes.
-
-
-26 December 2016: mitmproxy 1.0
-
-    * All mitmproxy tools are now Python 3 only! We plan to support Python 3.5 and higher.
-
-    * Web-Based User Interface: Mitmproxy now offically has a web-based user interface
-      called mitmweb. We consider it stable for all features currently exposed 
-      in the UI, but it still misses a lot of mitmproxy’s options.
-      
-    * Windows Compatibility: With mitmweb, mitmproxy is now useable on Windows. 
-      We are also introducing an installer (kindly sponsored by BitRock) that 
-      simplifies setup.
-      
-    * Configuration: The config file format is now a single YAML file. In most cases,
-      converting to the new format should be trivial - please see the docs for
-      more information.
-
-    * Console: Significant UI improvements - including sorting of flows by
-      size, type and url, status bar improvements, much faster indentation for
-      HTTP views, and more.
-
-    * HTTP/2: Significant improvements, but is temporarily disabled by default
-      due to wide-spread protocol implementation errors on some large website
-
-    * WebSocket: The protocol implementation is now mature, and is enabled by
-      default. Complete UI support is coming in the next release. Hooks for 
-      message interception and manipulation are available.
-
-    * A myriad of other small improvements throughout the project.
-
-
-16 October 2016: mitmproxy 0.18
-
-    * Python 3 Compatibility for mitmproxy and pathod (Shadab Zafar, GSoC 2016)
-
-    * Major improvements to mitmweb (Clemens Brunner & Jason Hao, GSoC 2016)
-
-    * Internal Core Refactor: Separation of most features into isolated Addons
-
-    * Initial Support for WebSockets
-
-    * Improved HTTP/2 Support
-
-    * Reverse Proxy Mode now automatically adjusts host headers and TLS Server Name Indication
-
-    * Improved HAR export
-
-    * Improved export functionality for curl, python code, raw http etc.
-
-    * Flow URLs are now truncated in the console for better visibility
-
-    * New filters for TCP, HTTP and marked flows.
-
-    * Mitmproxy now handles comma-separated Cookie headers
-
-    * Merge mitmproxy and pathod documentation
-
-    * Mitmdump now sanitizes its console output to not include control characters
-
-    * Improved message body handling for HTTP messages:
-      .raw_content provides the message body as seen on the wire
-      .content provides the decompressed body (e.g. un-gzipped)
-      .text provides the body decompressed and decoded body
-
-    * New HTTP Message getters/setters for cookies and form contents.
-
-    * Add ability to view only marked flows in mitmproxy
-
-    * Improved Script Reloader (Always use polling, watch for whole directory)
-
-    * Use tox for testing
-
-    * Unicode support for tnetstrings
-
-    * Add dumpfile converters for mitmproxy versions 0.11 and 0.12
-
-    * Numerous bugfixes
-
-
-9 April 2016: mitmproxy 0.17
-
-    * Simplify repository and release structure. mitmproxy now comes as a single package, including netlib and pathod.
-
-    * Rename the Python package from libmproxy to mitmproxy.
-
-    * New option to add server certs to client chain (CVE-2016-2402, John Kozyrakis)
-
-    * Enable HTTP/2 by default (Thomas Kriechbaumer)
-
-    * Improved HAR extractor (Shadab Zafar)
-
-    * Add icon for OSX and Windows binaries
-
-    * Add content view for query parameters (Will Coster)
-
-    * Initial work on Python 3 compatibility
-
-    * locust.io export (Zohar Lorberbaum)
-
-    * Fix XSS vulnerability in HTTP errors (Will Coster)
-
-    * Numerous bugfixes and minor improvements
-
-
-15 February 2016: mitmproxy 0.16
-
-    * Completely revised HTTP2 implementation based on hyper-h2 (Thomas Kriechbaumer)
-
-    * Export flows as cURL command, Python code or raw HTTP (Shadab Zafar)
-
-    * Fixed compatibility with the Android Emulator (Will Coster)
-
-    * Script Reloader: Inline scripts are reloaded automatically if modified (Matthew Shao)
-
-    * Inline script hooks for TCP mode (Michael J. Bazzinotti)
-
-    * Add default ciphers to support iOS9 App Transport Security (Jorge Villacorta)
-
-    * Basic Authentication for mitmweb (Guillem Anguera)
-
-    * Exempt connections from interception based on TLS Server Name Indication (David Weinstein)
-
-    * Provide Python Wheels for faster installation
-
-    * Numerous bugfixes and minor improvements
-
-
-4 December 2015: mitmproxy 0.15
-
-    * Support for loading and converting older dumpfile formats (0.13 and up)
-
-    * Content views for inline script (@chrisczub)
-
-    * Better handling of empty header values (Benjamin Lee/@bltb)
-
-    * Fix a gnarly memory leak in mitmdump
-
-    * A number of bugfixes and small improvements
-
-
-6 November 2015: mitmproxy 0.14
-
-    * Statistics: 399 commits, 13 contributors, 79 closed issues, 37 closed
-      PRs, 103 days
-
-    * Docs: Greatly updated docs now hosted on ReadTheDocs!
-      http://docs.mitmproxy.org
-
-    * Docs: Fixed Typos, updated URLs etc. (Nick Badger, Ben Lerner, Choongwoo
-      Han, onlywade, Jurriaan Bremer)
-
-    * mitmdump: Colorized TTY output
-
-    * mitmdump: Use mitmproxy's content views for human-readable output (Chris
-      Czub)
-
-    * mitmproxy and mitmdump: Support for displaying UTF8 contents
-
-    * mitmproxy: add command line switch to disable mouse interaction (Timothy
-      Elliott)
-
-    * mitmproxy: bug fixes (Choongwoo Han, sethp-jive, FreeArtMan)
-
-    * mitmweb: bug fixes (Colin Bendell)
-
-    * libmproxy: Add ability to fall back to TCP passthrough for non-HTTP
-      connections.
-
-    * libmproxy: Avoid double-connect in case of TLS Server Name Indication.
-      This yields a massive speedup for TLS handshakes.
-
-    * libmproxy: Prevent unneccessary upstream connections (macmantrl)
-
-    * Inline Scripts: New API for HTTP Headers:
-      http://docs.mitmproxy.org/en/latest/dev/models.html#netlib.http.Headers
-
-    * Inline Scripts: Properly handle exceptions in `done` hook
-
-    * Inline Scripts: Allow relative imports, provide `__file__`
-
-    * Examples: Add probabilistic TLS passthrough as an inline script
-
-    * netlib: Refactored HTTP protocol handling code
-
-    * netlib: ALPN support
-
-    * netlib: fixed a bug in the optional certificate verification.
-
-    * netlib: Initial Python 3.5 support (this is the first prerequisite for
-      3.x support in mitmproxy)
-
-
-24 July 2015: mitmproxy 0.13
-
-    * Upstream certificate validation. See the --verify-upstream-cert,
-      --upstream-trusted-cadir and --upstream-trusted-ca parameters. Thanks to
-      Kyle Morton (github.com/kyle-m) for his work on this.
-
-    * Add HTTP transparent proxy mode. This uses the host headers from HTTP
-      traffic (rather than SNI and IP address information from the OS) to
-      implement perform transparent proxying. Thanks to github.com/ijiro123 for
-      this feature.
-
-    * Add ~src and ~dst REGEX filters, allowing matching on source and
-      destination addresses in the form of <IP>:<Port>
-
-    * mitmproxy console: change g/G keyboard shortcuts to match less. Thanks to
-      Jose Luis Honorato (github.com/jlhonora).
-
-    * mitmproxy console: Flow marking and unmarking. Marked flows are not
-      deleted when the flow list is cleared. Thanks to Jake Drahos
-      (github.com/drahosj).
-
-    * mitmproxy console: add marking of flows
-
-    * Remove the certforward feature. It was added to allow exploitation of
-      #gotofail, which is no longer a common vulnerability. Permitting this
-      hugely increased the complexity of packaging and distributing mitmproxy.
-
-
-
-
-3 June 2015: mitmproxy 0.12.1
-
-    * mitmproxy console: mouse interaction - scroll in the flow list, click on
-      flow to view, click to switch between tabs.
-
-    * Update our crypto defaults: SHA256, 2048 bit RSA, 4096 bit DH parameters.
-
-    * BUGFIX: crash under some circumstances when copying to clipboard.
-
-    * BUGFIX: occasional crash when deleting flows.
-
-
-18 May 2015: mitmproxy 0.12
-
-    * mitmproxy console: Significant revamp of the UI. The major changes are
-      listed below, and in addition almost every aspect of the UI has
-      been tweaked, and performance has improved significantly.
-
-    * mitmproxy console: A new options screen has been created ("o" shortcut),
-      and many options that were previously manipulated directly via a
-      keybinding have been moved there.
-
-    * mitmproxy console: Big improvement in palettes. This includes improvements
-      to all colour schemes. Palettes now set the terminal background colour by
-      default, and a new --palette-transparent option has been added to disable
-      this.
-
-    * mitmproxy console: g/G shortcuts throughout mitmproxy console to jump
-      to the beginning/end of the current view.
-
-    * mitmproxy console: switch  palettes on the fly from the options screen.
-
-    * mitmproxy console: A cookie editor has been added for mitmproxy console
-      at long last.
-
-    * mitmproxy console: Various components of requests and responses can be
-      copied to the clipboard from mitmproxy - thanks to @marceloglezer.
-
-    * Support for creating new requests from scratch in mitmproxy console (@marceloglezer).
-
-    * SSLKEYLOGFILE environment variable to specify a logging location for TLS
-      master keys. This can be used with tools like Wireshark to allow TLS
-      decoding.
-
-    * Server facing SSL cipher suite specification (thanks to Jim Shaver).
-
-    * Official support for transparent proxying on FreeBSD - thanks to Mike C
-      (http://github.com/mike-pt).
-
-    * Many other small bugfixes and improvemenets throughout the project.
-
-
-29 Dec 2014: mitmproxy 0.11.2:
-
-    * Configuration files - mitmproxy.conf, mitmdump.conf, common.conf in the
-      .mitmproxy directory.
-    * Better handling of servers that reject connections that are not SNI.
-    * Many other small bugfixes and improvements.
-
-
-15 November 2014: mitmproxy 0.11.1:
-
-    * Bug fixes: connection leaks some crashes
-
-
-7 November 2014: mitmproxy 0.11:
-
-    * Performance improvements for mitmproxy console
-
-    * SOCKS5 proxy mode allows mitmproxy to act as a SOCKS5 proxy server
-
-    * Data streaming for response bodies exceeding a threshold
-      (bradpeabody@gmail.com)
-
-    * Ignore hosts or IP addresses, forwarding both HTTP and HTTPS traffic
-      untouched
-
-    * Finer-grained control of traffic replay, including options to ignore
-      contents or parameters when matching flows (marcelo.glezer@gmail.com)
-
-    * Pass arguments to inline scripts
-
-    * Configurable size limit on HTTP request and response bodies
-
-    * Per-domain specification of interception certificates and keys (see
-      --cert option)
-
-    * Certificate forwarding, relaying upstream SSL certificates verbatim (see
-      --cert-forward)
-
-    * Search and highlighting for HTTP request and response bodies in
-      mitmproxy console (pedro@worcel.com)
-
-    * Transparent proxy support on Windows
-
-    * Improved error messages and logging
-
-    * Support for FreeBSD in transparent mode, using pf (zbrdge@gmail.com)
-
-    * Content view mode for WBXML (davidshaw835@air-watch.com)
-
-    * Better documentation, with a new section on proxy modes
-
-    * Generic TCP proxy mode
-
-    * Countless bugfixes and other small improvements
-
-    * pathod: Hugely improved SSL support, including dynamic generation of certificates
-    using the mitproxy cacert
-
-7 November 2014: pathod 0.11:
-
-  * Hugely improved SSL support, including dynamic generation of certificates
-    using the mitproxy cacert
-
-  * pathoc -S dumps information on the remote SSL certificate chain
-
-  * Big improvements to fuzzing, including random spec selection and memoization to avoid repeating randomly generated patterns
-
-  * Reflected patterns, allowing you to embed a pathod server response specification in a pathoc request, resolving both on client side. This makes fuzzing proxies and other intermediate systems much better.
-
-
-28 January 2014: mitmproxy 0.10:
-
-    * Support for multiple scripts and multiple script arguments
-
-    * Easy certificate install through the in-proxy web app, which is now
-      enabled by default
-
-    * Forward proxy mode, that forwards proxy requests to an upstream HTTP server
-
-    * Reverse proxy now works with SSL
-
-    * Search within a request/response using the "/" and "n" shortcut keys
-
-    * A view that beatifies CSS files if cssutils is available
-
-    * Bug fix, documentation improvements, and more.
-
-
-25 August 2013: mitmproxy 0.9.2:
-
-    * Improvements to the mitmproxywrapper.py helper script for OSX.
-
-    * Don't take minor version into account when checking for serialized file
-      compatibility.
-
-    * Fix a bug causing resource exhaustion under some circumstances for SSL
-      connections.
-
-    * Revamp the way we store interception certificates. We used to store these
-      on disk, they're now in-memory. This fixes a race condition related to
-      cert handling, and improves compatibility with Windows, where the rules
-      governing permitted file names are weird, resulting in errors for some
-      valid IDNA-encoded names.
-
-    * Display transfer rates for responses in the flow list.
-
-    * Many other small bugfixes and improvements.
-
-
-25 August 2013: pathod 0.9.2:
-
-    * Adapt to interface changes in netlib
-
-
-16 June 2013: mitmproxy 0.9.1:
-
-    * Use "correct" case for Content-Type headers added by mitmproxy.
-
-    * Make UTF environment detection more robust.
-
-    * Improved MIME-type detection for viewers.
-
-    * Always read files in binary mode (Windows compatibility fix).
-
-    * Some developer documentation.
-
-
-15 May 2013: mitmproxy 0.9:
-
-    * Upstream certs mode is now the default.
-
-    * Add a WSGI container that lets you host in-proxy web applications.
-
-    * Full transparent proxy support for Linux and OSX.
-
-    * Introduce netlib, a common codebase for mitmproxy and pathod
-      (http://github.com/cortesi/netlib).
-
-    * Full support for SNI.
-
-    * Color palettes for mitmproxy, tailored for light and dark terminal
-      backgrounds.
-
-    * Stream flows to file as responses arrive with the "W" shortcut in
-      mitmproxy.
-
-    * Extend the filter language, including ~d domain match operator, ~a to
-      match asset flows (js, images, css).
-
-    * Follow mode in mitmproxy ("F" shortcut) to "tail" flows as they arrive.
-
-    * --dummy-certs option to specify and preserve the dummy certificate
-      directory.
-
-    * Server replay from the current captured buffer.
-
-    * Huge improvements in content views. We now have viewers for AMF, HTML,
-      JSON, Javascript, images, XML, URL-encoded forms, as well as hexadecimal
-      and raw views.
-
-    * Add Set Headers, analagous to replacement hooks. Defines headers that are set
-      on flows, based on a matching pattern.
-
-    * A graphical editor for path components in mitmproxy.
-
-    * A small set of standard user-agent strings, which can be used easily in
-      the header editor.
-
-    * Proxy authentication to limit access to mitmproxy
-
-    * pathod: Proxy mode. You can now configure clients to use pathod as an
-      HTTP/S proxy.
-
-    * pathoc: Proxy support, including using CONNECT to tunnel directly to
-      targets.
-
-    * pathoc: client certificate support.
-
-    * pathod: API improvements, bugfixes.
-
-
-15 May 2013: pathod 0.9 (version synced with mitmproxy):
-
-    * Pathod proxy mode. You can now configure clients to use pathod as an
-      HTTP/S proxy.
-
-    * Pathoc proxy support, including using CONNECT to tunnel directly to
-      targets.
-
-    * Pathoc client certificate support.
-
-    * API improvements, bugfixes.
-
-
-16 November 2012: pathod 0.3:
-
-    A release focusing on shoring up our fuzzing capabilities, especially with
-    pathoc.
-
-    * pathoc -q and -r options, output full request and response text.
-
-    * pathod -q and -r options, add full request and response text to pathod's
-      log buffer.
-
-    * pathoc and pathod -x option, makes -q and -r options log in hex dump
-      format.
-
-    * pathoc -C option, specify response codes to ignore.
-
-    * pathoc -T option, instructs pathoc to ignore timeouts.
-
-    * pathoc -o option, a one-shot mode that exits after the first non-ignored
-      response.
-
-    * pathoc and pathod -e option, which explains the resulting message by
-      expanding random and generated portions, and logging a reproducible
-      specification.
-
-    * Streamline the specification langauge. HTTP response message is now
-      specified using the "r" mnemonic.
-
-    * Add a "u" mnemonic for specifying User-Agent strings. Add a set of
-      standard user-agent strings accessible through shortcuts.
-
-    * Major internal refactoring and cleanup.
-
-    * Many bugfixes.
-
-
-22 August 2012: pathod 0.2:
-
-    * Add pathoc, a pathological HTTP client.
-
-    * Add libpathod.test, a truss for using pathod in unit tests.
-
-    * Add an injection operator to the specification language.
-
-    * Allow Python escape sequences in value literals.
-
-    * Allow execution of requests and responses from file, using the new + operator.
-
-    * Add daemonization to Pathod, and make it more robust for public-facing use.
-
-    * Let pathod pick an arbitrary open port if -p 0 is specified.
-
-    * Move from Tornado to netlib, the network library written for mitmproxy.
-
-    * Move the web application to Flask.
-
-    * Massively expand the documentation.
-
 
 5 April 2012: mitmproxy 0.8:
 
@@ -592,14 +29,14 @@
 20 February 2012: mitmproxy 0.7:
 
     * New built-in key/value editor. This lets you interactively edit URL query
-      strings, headers and URL-encoded form data.
+      strings, headers and URL-encoded form data. 
 
     * Extend script API to allow duplication and replay of flows.
-
+    
     * API for easy manipulation of URL-encoded forms and query strings.
-
+    
     * Add "D" shortcut in mitmproxy to duplicate a flow.
-
+    
     * Reverse proxy mode. In this mode mitmproxy acts as an HTTP server,
       forwarding all traffic to a specified upstream server.
 
@@ -607,13 +44,13 @@
       improve spacing and layout throughout.
 
     * Add support for filtering by HTTP method.
-
+   
     * Add the ability to specify an HTTP body size limit.
-
+    
     * Move to typed netstrings for serialization format - this makes 0.7
       backwards-incompatible with serialized data from 0.6!
 
-    * Significant improvements in speed and responsiveness of UI.
+    * Significant improvements in speed and responsiveness of UI. 
 
     * Many minor bugfixes and improvements.
 
@@ -678,14 +115,14 @@
       100% of CPU.
 
 
-30 March 2011: mitmproxy 0.4
+30 March 2011: mitmproxy 0.4 
 
     * Full serialization of HTTP conversations
-
+    
     * Client and server replay
-
+    
     * On-the-fly generation of dummy SSL certificates
-
+   
     * mitmdump has "grown up" into a powerful tcpdump-like tool for HTTP/S
 
     * Dozens of improvements to the mitmproxy console interface
@@ -693,22 +130,22 @@
     * Python scripting hooks for programmatic modification of traffic
 
 
-1 March 2010: mitmproxy 0.2
+1 March 2010: mitmproxy 0.2 
 
     * Big speed and responsiveness improvements, thanks to Thomas Roth
-
+    
     * Support urwid 0.9.9
-
+    
     * Terminal beeping based on filter expressions
-
+    
     * Filter expressions for terminal beeps, limits, interceptions and sticky
       cookies can now be passed on the command line.
 
     * Save requests and responses to file
-
+    
     * Split off non-interactive dump functionality into a new tool called
       mitmdump
-
+    
     * "A" will now accept all intercepted connections
-
+    
     * Lots of bugfixes

CONTRIBUTORS

@@ -1,189 +1,18 @@
-  2407	Aldo Cortesi
-  1873	Maximilian Hils
-   556	Thomas Kriechbaumer
-   258	Shadab Zafar
-    97	Jason
-    83	Marcelo Glezer
-    68	Clemens
-    28	Jim Shaver
-    18	Henrik Nordstrom
-    16	Matthew Shao
-    14	Pedro Worcel
-    14	David Weinstein
-    13	Thomas Roth
-    11	Jake Drahos
-    11	Stephen Altamirano
-    11	arjun23496
-    11	Justus Wingert
-    10	András Veres-Szentkirályi
-    10	Zohar Lorberbaum
-    10	smill
-    10	Chris Czub
-    10	Sandor Nemes
-    10	Doug Freed
-     9	ikoz
-     9	Legend Tang
-     9	Rouli
-     9	Kyle Morton
-     8	Jason A. Novak
-     8	Chandler Abraham
-     7	Matthias Urlichs
-     7	Brad Peabody
-     7	dufferzafar
-     7	Alexis Hildebrandt
-     6	Felix Yan
-     5	Will Coster
-     5	Sam Cleveland
-     5	iroiro123
-     5	elitest
-     5	Tomaz Muraus
-     5	Choongwoo Han
-     4	Schamper
-     4	Youhei Sakurai
-     4	Bryan Bishop
-     4	root
-     4	Valtteri Virtanen
-     4	Clemens Brunner
-     4	Marc Liyanage
-     4	Wade 524
-     4	chhsiao90
-     4	yonder
-     4	Michael J. Bazzinotti
-     3	Ryan Welton
-     3	Ryan Laughlin
-     3	Kyle Manna
-     3	Eli Shvartsman
-     3	Vincent Haupert
-     3	Manish Kumar
-     3	Zack B
-     3	MatthewShao
-     3	redfast00
-     3	requires.io
-     3	Guillem Anguera
-     3	smill@cuckoo.sh
-     3	Chris Neasbitt
-     3	Benjamin Lee
-     2	Steven Van Acker
-     2	Slobodan Mišković
-     2	Jim Lloyd
-     2	isra17
-     2	israel
-     2	Sean Coates
-     2	Sachin Kelkar
-     2	jpkrause
-     2	Bennett Blodinger
-     2	lilydjwg
-     2	Michael Frister
-     2	Israel Nir
-     2	Cory Benfield
-     2	phackt
-     2	Anant
-     2	Jaime Soriano Pastor
-     2	Paul
-     2	Colin Bendell
-     2	依云
-     2	Heikki Hannikainen
-     2	Rob Wills
-     2	Niko Kommenda
-     2	Naveen Pai
-     2	strohu
-     2	alts
-     2	Yoginski
-     2	Mark E. Haase
-     2	Wade Catron
-     2	Terry Long
-     2	Krzysztof Bielicki
-     2	Nick Badger
-     1	Nicolas Esteves
-     1	Andrew Orr
-     1	Andrey Plotnikov
-     1	Andy Smith
-     1	Angelo Agatino Nicolosi
-     1	Anthony Zhang
-     1	BSalita
-     1	Ben Lerner
-     1	Bradley Baetz
-     1	Brady Law
-     1	Brett Randall
-     1	Chris Hamant
-     1	Christian Frichot
-     1	Dan Wilbraham
-     1	David Dworken
-     1	David Shaw
-     1	Doug Lethin
-     1	Drake Caraker
-     1	Edgar Boda-Majer
-     1	Eric Entzel
-     1	Felix Wolfsteller
-     1	FreeArtMan
-     1	Gabriel Kirkpatrick
-     1	Henrik Nordström
-     1	Israel Blancas
-     1	Ivaylo Popov
-     1	JC
-     1	Jakub Nawalaniec
-     1	Jakub Wilk
-     1	James Billingham
-     1	Jason Pepas
-     1	Jean Regisser
-     1	Jonathan Jones
-     1	Jorge Villacorta
-     1	Kit Randel
-     1	Kostya Esmukov
-     1	Linmiao Xu
-     1	Lucas Cimon
-     1	M. Utku Altinkaya
-     1	Mathieu Mitchell
-     1	Michael Bisbjerg
-     1	Mike C
-     1	Mike Fotinakis
-     1	Mikhail Korobov
-     1	Morton Fox
-     1	Nick HS
-     1	Nick Raptis
-     1	Aditya
-     1	Oleksandr Sheremet
-     1	Parth Ganatra
-     1	Pritam Baral
-     1	Quentin Pradet
-     1	Rich Somerfield
-     1	Rory McCann
-     1	Rune Halvorsen
-     1	Ryo Onodera
-     1	Sahil Chelaramani
-     1	Sahn Lam
-     1	Sanchit Sokhey
-     1	Seppo Yli-Olli
-     1	Sergey Chipiga
-     1	Stefan Wärting
-     1	Steve Phillips
-     1	Steven Noble
-     1	Suyash
-     1	Tai Dickerson
-     1	Tarashish Mishra
-     1	TearsDontFalls
-     1	Thiago Arrais
-     1	Tim Becker
-     1	Timothy Elliott
-     1	Tyler St. Onge
-     1	Ulrich Petri
-     1	Vyacheslav Bakhmutov
-     1	Wes Turner
-     1	Yuangxuan Wang
-     1	capt8bit
-     1	cle1000
-     1	davidpshaw
-     1	deployable
-     1	gecko655
-     1	jlhonora
-     1	joebowbeer
-     1	kronick
-     1	meeee
-     1	michaeljau
-     1	peralta
-     1	phil plante
-     1	sentient07
-     1	sethp-jive
-     1	starenka
-     1	vulnminer
-     1	vzvu3k6k
+ 485 Aldo Cortesi
+  18 Henrik Nordstrom
+  13 Thomas Roth
+  11 Stephen Altamirano
+   6 András Veres-Szentkirályi
+   4 Valtteri Virtanen
+   2 alts
+   2 Michael Frister
+   2 Mark E. Haase
+   2 Heikki Hannikainen
+   1 meeee
+   1 capt8bit
+   1 Yuangxuan Wang
+   1 Ulrich Petri
+   1 Rune Halvorsen
+   1 Rory McCann
+   1 Henrik Nordström
+   1 Felix Wolfsteller

LICENSE

@@ -1,19 +1,690 @@
-Copyright (c) 2013, Aldo Cortesi. All rights reserved.
+mitmproxy is licensed under the terms of the GNU General Public
+License version 3, with the following addition:
 
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
+  In addition, as a special exception, the copyright holders give
+permission to link the code of this program or portions of this
+program with the OpenSSL project's "OpenSSL" library (or with modified
+versions of it that use the same license as the "OpenSSL" library),
+and distribute linked combinations including the two. 
 
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
+  You must obey the GNU General Public License in all respects for all
+of the code used other than "OpenSSL".  If you modify file(s) provided
+under this license, you may extend this exception to your version of
+the file, but you are not obligated to do so. If you do not wish to do
+so, delete this exception statement from your version.
 
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+
+                    GNU GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+                            Preamble
+
+  The GNU General Public License is a free, copyleft license for
+software and other kinds of works.
+
+  The licenses for most software and other practical works are designed
+to take away your freedom to share and change the works.  By contrast,
+the GNU General Public License is intended to guarantee your freedom to
+share and change all versions of a program--to make sure it remains free
+software for all its users.  We, the Free Software Foundation, use the
+GNU General Public License for most of our software; it applies also to
+any other work released this way by its authors.  You can apply it to
+your programs, too.
+
+  When we speak of free software, we are referring to freedom, not
+price.  Our General Public Licenses are designed to make sure that you
+have the freedom to distribute copies of free software (and charge for
+them if you wish), that you receive source code or can get it if you
+want it, that you can change the software or use pieces of it in new
+free programs, and that you know you can do these things.
+
+  To protect your rights, we need to prevent others from denying you
+these rights or asking you to surrender the rights.  Therefore, you have
+certain responsibilities if you distribute copies of the software, or if
+you modify it: responsibilities to respect the freedom of others.
+
+  For example, if you distribute copies of such a program, whether
+gratis or for a fee, you must pass on to the recipients the same
+freedoms that you received.  You must make sure that they, too, receive
+or can get the source code.  And you must show them these terms so they
+know their rights.
+
+  Developers that use the GNU GPL protect your rights with two steps:
+(1) assert copyright on the software, and (2) offer you this License
+giving you legal permission to copy, distribute and/or modify it.
+
+  For the developers' and authors' protection, the GPL clearly explains
+that there is no warranty for this free software.  For both users' and
+authors' sake, the GPL requires that modified versions be marked as
+changed, so that their problems will not be attributed erroneously to
+authors of previous versions.
+
+  Some devices are designed to deny users access to install or run
+modified versions of the software inside them, although the manufacturer
+can do so.  This is fundamentally incompatible with the aim of
+protecting users' freedom to change the software.  The systematic
+pattern of such abuse occurs in the area of products for individuals to
+use, which is precisely where it is most unacceptable.  Therefore, we
+have designed this version of the GPL to prohibit the practice for those
+products.  If such problems arise substantially in other domains, we
+stand ready to extend this provision to those domains in future versions
+of the GPL, as needed to protect the freedom of users.
+
+  Finally, every program is threatened constantly by software patents.
+States should not allow patents to restrict development and use of
+software on general-purpose computers, but in those that do, we wish to
+avoid the special danger that patents applied to a free program could
+make it effectively proprietary.  To prevent this, the GPL assures that
+patents cannot be used to render the program non-free.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.
+
+                       TERMS AND CONDITIONS
+
+  0. Definitions.
+
+  "This License" refers to version 3 of the GNU General Public License.
+
+  "Copyright" also means copyright-like laws that apply to other kinds of
+works, such as semiconductor masks.
+
+  "The Program" refers to any copyrightable work licensed under this
+License.  Each licensee is addressed as "you".  "Licensees" and
+"recipients" may be individuals or organizations.
+
+  To "modify" a work means to copy from or adapt all or part of the work
+in a fashion requiring copyright permission, other than the making of an
+exact copy.  The resulting work is called a "modified version" of the
+earlier work or a work "based on" the earlier work.
+
+  A "covered work" means either the unmodified Program or a work based
+on the Program.
+
+  To "propagate" a work means to do anything with it that, without
+permission, would make you directly or secondarily liable for
+infringement under applicable copyright law, except executing it on a
+computer or modifying a private copy.  Propagation includes copying,
+distribution (with or without modification), making available to the
+public, and in some countries other activities as well.
+
+  To "convey" a work means any kind of propagation that enables other
+parties to make or receive copies.  Mere interaction with a user through
+a computer network, with no transfer of a copy, is not conveying.
+
+  An interactive user interface displays "Appropriate Legal Notices"
+to the extent that it includes a convenient and prominently visible
+feature that (1) displays an appropriate copyright notice, and (2)
+tells the user that there is no warranty for the work (except to the
+extent that warranties are provided), that licensees may convey the
+work under this License, and how to view a copy of this License.  If
+the interface presents a list of user commands or options, such as a
+menu, a prominent item in the list meets this criterion.
+
+  1. Source Code.
+
+  The "source code" for a work means the preferred form of the work
+for making modifications to it.  "Object code" means any non-source
+form of a work.
+
+  A "Standard Interface" means an interface that either is an official
+standard defined by a recognized standards body, or, in the case of
+interfaces specified for a particular programming language, one that
+is widely used among developers working in that language.
+
+  The "System Libraries" of an executable work include anything, other
+than the work as a whole, that (a) is included in the normal form of
+packaging a Major Component, but which is not part of that Major
+Component, and (b) serves only to enable use of the work with that
+Major Component, or to implement a Standard Interface for which an
+implementation is available to the public in source code form.  A
+"Major Component", in this context, means a major essential component
+(kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to
+produce the work, or an object code interpreter used to run it.
+
+  The "Corresponding Source" for a work in object code form means all
+the source code needed to generate, install, and (for an executable
+work) run the object code and to modify the work, including scripts to
+control those activities.  However, it does not include the work's
+System Libraries, or general-purpose tools or generally available free
+programs which are used unmodified in performing those activities but
+which are not part of the work.  For example, Corresponding Source
+includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically
+linked subprograms that the work is specifically designed to require,
+such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+  The Corresponding Source need not include anything that users
+can regenerate automatically from other parts of the Corresponding
+Source.
+
+  The Corresponding Source for a work in source code form is that
+same work.
+
+  2. Basic Permissions.
+
+  All rights granted under this License are granted for the term of
+copyright on the Program, and are irrevocable provided the stated
+conditions are met.  This License explicitly affirms your unlimited
+permission to run the unmodified Program.  The output from running a
+covered work is covered by this License only if the output, given its
+content, constitutes a covered work.  This License acknowledges your
+rights of fair use or other equivalent, as provided by copyright law.
+
+  You may make, run and propagate covered works that you do not
+convey, without conditions so long as your license otherwise remains
+in force.  You may convey covered works to others for the sole purpose
+of having them make modifications exclusively for you, or provide you
+with facilities for running those works, provided that you comply with
+the terms of this License in conveying all material for which you do
+not control copyright.  Those thus making or running the covered works
+for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of
+your copyrighted material outside their relationship with you.
+
+  Conveying under any other circumstances is permitted solely under
+the conditions stated below.  Sublicensing is not allowed; section 10
+makes it unnecessary.
+
+  3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+  No covered work shall be deemed part of an effective technological
+measure under any applicable law fulfilling obligations under article
+11 of the WIPO copyright treaty adopted on 20 December 1996, or
+similar laws prohibiting or restricting circumvention of such
+measures.
+
+  When you convey a covered work, you waive any legal power to forbid
+circumvention of technological measures to the extent such circumvention
+is effected by exercising rights under this License with respect to
+the covered work, and you disclaim any intention to limit operation or
+modification of the work as a means of enforcing, against the work's
+users, your or third parties' legal rights to forbid circumvention of
+technological measures.
+
+  4. Conveying Verbatim Copies.
+
+  You may convey verbatim copies of the Program's source code as you
+receive it, in any medium, provided that you conspicuously and
+appropriately publish on each copy an appropriate copyright notice;
+keep intact all notices stating that this License and any
+non-permissive terms added in accord with section 7 apply to the code;
+keep intact all notices of the absence of any warranty; and give all
+recipients a copy of this License along with the Program.
+
+  You may charge any price or no price for each copy that you convey,
+and you may offer support or warranty protection for a fee.
+
+  5. Conveying Modified Source Versions.
+
+  You may convey a work based on the Program, or the modifications to
+produce it from the Program, in the form of source code under the
+terms of section 4, provided that you also meet all of these conditions:
+
+    a) The work must carry prominent notices stating that you modified
+    it, and giving a relevant date.
+
+    b) The work must carry prominent notices stating that it is
+    released under this License and any conditions added under section
+    7.  This requirement modifies the requirement in section 4 to
+    "keep intact all notices".
+
+    c) You must license the entire work, as a whole, under this
+    License to anyone who comes into possession of a copy.  This
+    License will therefore apply, along with any applicable section 7
+    additional terms, to the whole of the work, and all its parts,
+    regardless of how they are packaged.  This License gives no
+    permission to license the work in any other way, but it does not
+    invalidate such permission if you have separately received it.
+
+    d) If the work has interactive user interfaces, each must display
+    Appropriate Legal Notices; however, if the Program has interactive
+    interfaces that do not display Appropriate Legal Notices, your
+    work need not make them do so.
+
+  A compilation of a covered work with other separate and independent
+works, which are not by their nature extensions of the covered work,
+and which are not combined with it such as to form a larger program,
+in or on a volume of a storage or distribution medium, is called an
+"aggregate" if the compilation and its resulting copyright are not
+used to limit the access or legal rights of the compilation's users
+beyond what the individual works permit.  Inclusion of a covered work
+in an aggregate does not cause this License to apply to the other
+parts of the aggregate.
+
+  6. Conveying Non-Source Forms.
+
+  You may convey a covered work in object code form under the terms
+of sections 4 and 5, provided that you also convey the
+machine-readable Corresponding Source under the terms of this License,
+in one of these ways:
+
+    a) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by the
+    Corresponding Source fixed on a durable physical medium
+    customarily used for software interchange.
+
+    b) Convey the object code in, or embodied in, a physical product
+    (including a physical distribution medium), accompanied by a
+    written offer, valid for at least three years and valid for as
+    long as you offer spare parts or customer support for that product
+    model, to give anyone who possesses the object code either (1) a
+    copy of the Corresponding Source for all the software in the
+    product that is covered by this License, on a durable physical
+    medium customarily used for software interchange, for a price no
+    more than your reasonable cost of physically performing this
+    conveying of source, or (2) access to copy the
+    Corresponding Source from a network server at no charge.
+
+    c) Convey individual copies of the object code with a copy of the
+    written offer to provide the Corresponding Source.  This
+    alternative is allowed only occasionally and noncommercially, and
+    only if you received the object code with such an offer, in accord
+    with subsection 6b.
+
+    d) Convey the object code by offering access from a designated
+    place (gratis or for a charge), and offer equivalent access to the
+    Corresponding Source in the same way through the same place at no
+    further charge.  You need not require recipients to copy the
+    Corresponding Source along with the object code.  If the place to
+    copy the object code is a network server, the Corresponding Source
+    may be on a different server (operated by you or a third party)
+    that supports equivalent copying facilities, provided you maintain
+    clear directions next to the object code saying where to find the
+    Corresponding Source.  Regardless of what server hosts the
+    Corresponding Source, you remain obligated to ensure that it is
+    available for as long as needed to satisfy these requirements.
+
+    e) Convey the object code using peer-to-peer transmission, provided
+    you inform other peers where the object code and Corresponding
+    Source of the work are being offered to the general public at no
+    charge under subsection 6d.
+
+  A separable portion of the object code, whose source code is excluded
+from the Corresponding Source as a System Library, need not be
+included in conveying the object code work.
+
+  A "User Product" is either (1) a "consumer product", which means any
+tangible personal property which is normally used for personal, family,
+or household purposes, or (2) anything designed or sold for incorporation
+into a dwelling.  In determining whether a product is a consumer product,
+doubtful cases shall be resolved in favor of coverage.  For a particular
+product received by a particular user, "normally used" refers to a
+typical or common use of that class of product, regardless of the status
+of the particular user or of the way in which the particular user
+actually uses, or expects or is expected to use, the product.  A product
+is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent
+the only significant mode of use of the product.
+
+  "Installation Information" for a User Product means any methods,
+procedures, authorization keys, or other information required to install
+and execute modified versions of a covered work in that User Product from
+a modified version of its Corresponding Source.  The information must
+suffice to ensure that the continued functioning of the modified object
+code is in no case prevented or interfered with solely because
+modification has been made.
+
+  If you convey an object code work under this section in, or with, or
+specifically for use in, a User Product, and the conveying occurs as
+part of a transaction in which the right of possession and use of the
+User Product is transferred to the recipient in perpetuity or for a
+fixed term (regardless of how the transaction is characterized), the
+Corresponding Source conveyed under this section must be accompanied
+by the Installation Information.  But this requirement does not apply
+if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has
+been installed in ROM).
+
+  The requirement to provide Installation Information does not include a
+requirement to continue to provide support service, warranty, or updates
+for a work that has been modified or installed by the recipient, or for
+the User Product in which it has been modified or installed.  Access to a
+network may be denied when the modification itself materially and
+adversely affects the operation of the network or violates the rules and
+protocols for communication across the network.
+
+  Corresponding Source conveyed, and Installation Information provided,
+in accord with this section must be in a format that is publicly
+documented (and with an implementation available to the public in
+source code form), and must require no special password or key for
+unpacking, reading or copying.
+
+  7. Additional Terms.
+
+  "Additional permissions" are terms that supplement the terms of this
+License by making exceptions from one or more of its conditions.
+Additional permissions that are applicable to the entire Program shall
+be treated as though they were included in this License, to the extent
+that they are valid under applicable law.  If additional permissions
+apply only to part of the Program, that part may be used separately
+under those permissions, but the entire Program remains governed by
+this License without regard to the additional permissions.
+
+  When you convey a copy of a covered work, you may at your option
+remove any additional permissions from that copy, or from any part of
+it.  (Additional permissions may be written to require their own
+removal in certain cases when you modify the work.)  You may place
+additional permissions on material, added by you to a covered work,
+for which you have or can give appropriate copyright permission.
+
+  Notwithstanding any other provision of this License, for material you
+add to a covered work, you may (if authorized by the copyright holders of
+that material) supplement the terms of this License with terms:
+
+    a) Disclaiming warranty or limiting liability differently from the
+    terms of sections 15 and 16 of this License; or
+
+    b) Requiring preservation of specified reasonable legal notices or
+    author attributions in that material or in the Appropriate Legal
+    Notices displayed by works containing it; or
+
+    c) Prohibiting misrepresentation of the origin of that material, or
+    requiring that modified versions of such material be marked in
+    reasonable ways as different from the original version; or
+
+    d) Limiting the use for publicity purposes of names of licensors or
+    authors of the material; or
+
+    e) Declining to grant rights under trademark law for use of some
+    trade names, trademarks, or service marks; or
+
+    f) Requiring indemnification of licensors and authors of that
+    material by anyone who conveys the material (or modified versions of
+    it) with contractual assumptions of liability to the recipient, for
+    any liability that these contractual assumptions directly impose on
+    those licensors and authors.
+
+  All other non-permissive additional terms are considered "further
+restrictions" within the meaning of section 10.  If the Program as you
+received it, or any part of it, contains a notice stating that it is
+governed by this License along with a term that is a further
+restriction, you may remove that term.  If a license document contains
+a further restriction but permits relicensing or conveying under this
+License, you may add to a covered work material governed by the terms
+of that license document, provided that the further restriction does
+not survive such relicensing or conveying.
+
+  If you add terms to a covered work in accord with this section, you
+must place, in the relevant source files, a statement of the
+additional terms that apply to those files, or a notice indicating
+where to find the applicable terms.
+
+  Additional terms, permissive or non-permissive, may be stated in the
+form of a separately written license, or stated as exceptions;
+the above requirements apply either way.
+
+  8. Termination.
+
+  You may not propagate or modify a covered work except as expressly
+provided under this License.  Any attempt otherwise to propagate or
+modify it is void, and will automatically terminate your rights under
+this License (including any patent licenses granted under the third
+paragraph of section 11).
+
+  However, if you cease all violation of this License, then your
+license from a particular copyright holder is reinstated (a)
+provisionally, unless and until the copyright holder explicitly and
+finally terminates your license, and (b) permanently, if the copyright
+holder fails to notify you of the violation by some reasonable means
+prior to 60 days after the cessation.
+
+  Moreover, your license from a particular copyright holder is
+reinstated permanently if the copyright holder notifies you of the
+violation by some reasonable means, this is the first time you have
+received notice of violation of this License (for any work) from that
+copyright holder, and you cure the violation prior to 30 days after
+your receipt of the notice.
+
+  Termination of your rights under this section does not terminate the
+licenses of parties who have received copies or rights from you under
+this License.  If your rights have been terminated and not permanently
+reinstated, you do not qualify to receive new licenses for the same
+material under section 10.
+
+  9. Acceptance Not Required for Having Copies.
+
+  You are not required to accept this License in order to receive or
+run a copy of the Program.  Ancillary propagation of a covered work
+occurring solely as a consequence of using peer-to-peer transmission
+to receive a copy likewise does not require acceptance.  However,
+nothing other than this License grants you permission to propagate or
+modify any covered work.  These actions infringe copyright if you do
+not accept this License.  Therefore, by modifying or propagating a
+covered work, you indicate your acceptance of this License to do so.
+
+  10. Automatic Licensing of Downstream Recipients.
+
+  Each time you convey a covered work, the recipient automatically
+receives a license from the original licensors, to run, modify and
+propagate that work, subject to this License.  You are not responsible
+for enforcing compliance by third parties with this License.
+
+  An "entity transaction" is a transaction transferring control of an
+organization, or substantially all assets of one, or subdividing an
+organization, or merging organizations.  If propagation of a covered
+work results from an entity transaction, each party to that
+transaction who receives a copy of the work also receives whatever
+licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the
+Corresponding Source of the work from the predecessor in interest, if
+the predecessor has it or can get it with reasonable efforts.
+
+  You may not impose any further restrictions on the exercise of the
+rights granted or affirmed under this License.  For example, you may
+not impose a license fee, royalty, or other charge for exercise of
+rights granted under this License, and you may not initiate litigation
+(including a cross-claim or counterclaim in a lawsuit) alleging that
+any patent claim is infringed by making, using, selling, offering for
+sale, or importing the Program or any portion of it.
+
+  11. Patents.
+
+  A "contributor" is a copyright holder who authorizes use under this
+License of the Program or a work on which the Program is based.  The
+work thus licensed is called the contributor's "contributor version".
+
+  A contributor's "essential patent claims" are all patent claims
+owned or controlled by the contributor, whether already acquired or
+hereafter acquired, that would be infringed by some manner, permitted
+by this License, of making, using, or selling its contributor version,
+but do not include claims that would be infringed only as a
+consequence of further modification of the contributor version.  For
+purposes of this definition, "control" includes the right to grant
+patent sublicenses in a manner consistent with the requirements of
+this License.
+
+  Each contributor grants you a non-exclusive, worldwide, royalty-free
+patent license under the contributor's essential patent claims, to
+make, use, sell, offer for sale, import and otherwise run, modify and
+propagate the contents of its contributor version.
+
+  In the following three paragraphs, a "patent license" is any express
+agreement or commitment, however denominated, not to enforce a patent
+(such as an express permission to practice a patent or covenant not to
+sue for patent infringement).  To "grant" such a patent license to a
+party means to make such an agreement or commitment not to enforce a
+patent against the party.
+
+  If you convey a covered work, knowingly relying on a patent license,
+and the Corresponding Source of the work is not available for anyone
+to copy, free of charge and under the terms of this License, through a
+publicly available network server or other readily accessible means,
+then you must either (1) cause the Corresponding Source to be so
+available, or (2) arrange to deprive yourself of the benefit of the
+patent license for this particular work, or (3) arrange, in a manner
+consistent with the requirements of this License, to extend the patent
+license to downstream recipients.  "Knowingly relying" means you have
+actual knowledge that, but for the patent license, your conveying the
+covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that
+country that you have reason to believe are valid.
+
+  If, pursuant to or in connection with a single transaction or
+arrangement, you convey, or propagate by procuring conveyance of, a
+covered work, and grant a patent license to some of the parties
+receiving the covered work authorizing them to use, propagate, modify
+or convey a specific copy of the covered work, then the patent license
+you grant is automatically extended to all recipients of the covered
+work and works based on it.
+
+  A patent license is "discriminatory" if it does not include within
+the scope of its coverage, prohibits the exercise of, or is
+conditioned on the non-exercise of one or more of the rights that are
+specifically granted under this License.  You may not convey a covered
+work if you are a party to an arrangement with a third party that is
+in the business of distributing software, under which you make payment
+to the third party based on the extent of your activity of conveying
+the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory
+patent license (a) in connection with copies of the covered work
+conveyed by you (or copies made from those copies), or (b) primarily
+for and in connection with specific products or compilations that
+contain the covered work, unless you entered into that arrangement,
+or that patent license was granted, prior to 28 March 2007.
+
+  Nothing in this License shall be construed as excluding or limiting
+any implied license or other defenses to infringement that may
+otherwise be available to you under applicable patent law.
+
+  12. No Surrender of Others' Freedom.
+
+  If conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot convey a
+covered work so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you may
+not convey it at all.  For example, if you agree to terms that obligate you
+to collect a royalty for further conveying from those to whom you convey
+the Program, the only way you could satisfy both those terms and this
+License would be to refrain entirely from conveying the Program.
+
+  13. Use with the GNU Affero General Public License.
+
+  Notwithstanding any other provision of this License, you have
+permission to link or combine any covered work with a work licensed
+under version 3 of the GNU Affero General Public License into a single
+combined work, and to convey the resulting work.  The terms of this
+License will continue to apply to the part which is the covered work,
+but the special requirements of the GNU Affero General Public License,
+section 13, concerning interaction through a network will apply to the
+combination as such.
+
+  14. Revised Versions of this License.
+
+  The Free Software Foundation may publish revised and/or new versions of
+the GNU General Public License from time to time.  Such new versions will
+be similar in spirit to the present version, but may differ in detail to
+address new problems or concerns.
+
+  Each version is given a distinguishing version number.  If the
+Program specifies that a certain numbered version of the GNU General
+Public License "or any later version" applies to it, you have the
+option of following the terms and conditions either of that numbered
+version or of any later version published by the Free Software
+Foundation.  If the Program does not specify a version number of the
+GNU General Public License, you may choose any version ever published
+by the Free Software Foundation.
+
+  If the Program specifies that a proxy can decide which future
+versions of the GNU General Public License can be used, that proxy's
+public statement of acceptance of a version permanently authorizes you
+to choose that version for the Program.
+
+  Later license versions may give you additional or different
+permissions.  However, no additional obligations are imposed on any
+author or copyright holder as a result of your choosing to follow a
+later version.
+
+  15. Disclaimer of Warranty.
+
+  THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
+APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
+HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
+OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
+THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
+IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
+ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+  16. Limitation of Liability.
+
+  IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
+WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
+THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
+GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
+USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
+DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
+PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
+EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
+SUCH DAMAGES.
+
+  17. Interpretation of Sections 15 and 16.
+
+  If the disclaimer of warranty and limitation of liability provided
+above cannot be given local legal effect according to their terms,
+reviewing courts shall apply local law that most closely approximates
+an absolute waiver of all civil liability in connection with the
+Program, unless a warranty or assumption of liability accompanies a
+copy of the Program in return for a fee.
+
+                     END OF TERMS AND CONDITIONS
+
+            How to Apply These Terms to Your New Programs
+
+  If you develop a new program, and you want it to be of the greatest
+possible use to the public, the best way to achieve this is to make it
+free software which everyone can redistribute and change under these terms.
+
+  To do so, attach the following notices to the program.  It is safest
+to attach them to the start of each source file to most effectively
+state the exclusion of warranty; and each file should have at least
+the "copyright" line and a pointer to where the full notice is found.
+
+    <one line to give the program's name and a brief idea of what it does.>
+    Copyright (C) <year>  <name of author>
+
+    This program is free software: you can redistribute it and/or modify
+    it under the terms of the GNU General Public License as published by
+    the Free Software Foundation, either version 3 of the License, or
+    (at your option) any later version.
+
+    This program is distributed in the hope that it will be useful,
+    but WITHOUT ANY WARRANTY; without even the implied warranty of
+    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+    GNU General Public License for more details.
+
+    You should have received a copy of the GNU General Public License
+    along with this program.  If not, see <http://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+  If the program does terminal interaction, make it output a short
+notice like this when it starts in an interactive mode:
+
+    <program>  Copyright (C) <year>  <name of author>
+    This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+    This is free software, and you are welcome to redistribute it
+    under certain conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License.  Of course, your program's commands
+might be different; for a GUI interface, you would use an "about box".
+
+  You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary.
+For more information on this, and how to apply and follow the GNU GPL, see
+<http://www.gnu.org/licenses/>.
+
+  The GNU General Public License does not permit incorporating your program
+into proprietary programs.  If your program is a subroutine library, you
+may consider it more useful to permit linking proprietary applications with
+the library.  If this is what you want to do, use the GNU Lesser General
+Public License instead of this License.  But first, please read
+<http://www.gnu.org/philosophy/why-not-lgpl.html>.

MANIFEST.in

@@ -1,3 +1,10 @@
-graft mitmproxy
-graft pathod
-recursive-exclude * *.pyc *.pyo *.swo *.swp *.map
+include LICENSE
+include CHANGELOG
+include CONTRIBUTORS
+include README.txt
+exclude README.mkd
+recursive-include examples *
+recursive-include doc *
+recursive-include test *
+recursive-include libmproxy/resources *
+recursive-exclude test *.swo *.swp *.pyc

README.mkd

@@ -0,0 +1,74 @@
+__mitmproxy__ is an SSL-capable man-in-the-middle proxy for HTTP. It provides a
+console interface that allows traffic flows to be inspected and edited on the
+fly.
+
+__mitmdump__ is the command-line version of mitmproxy, with the same
+functionality but without the user interface. Think tcpdump for HTTP.
+
+Complete documentation and a set of practical tutorials is included in the
+distribution package, and is also available at
+[mitmproxy.org](http://mitmproxy.org).
+
+
+Features
+--------
+
+- Intercept HTTP requests and responses and modify them on the fly.
+- Save complete HTTP conversations for later replay and analysis.
+- Replay the client-side of an HTTP conversations.
+- Replay HTTP responses of a previously recorded server.
+- Reverse proxy mode to forward traffic to a specified server.
+- Make scripted changes to HTTP traffic using Python. 
+- SSL certificates for interception are generated on the fly.
+
+
+Download
+--------
+
+Releases and rendered documentation can be found on the mitmproxy website:
+
+[mitmproxy.org](http://mitmproxy.org)
+
+Source is hosted on github: 
+
+[github.com/cortesi/mitmproxy](http://github.com/cortesi/mitmproxy)
+
+
+Community
+---------
+
+Come join us in the #mitmproxy channel on the OFTC IRC network
+(irc://irc.oftc.net:6667).
+
+We also have a mailing list, hosted here:
+
+    http://groups.google.com/group/mitmproxy
+
+
+Requirements
+------------
+
+* [Python](http://www.python.org) 2.6.x or 2.7.x.
+* [PyOpenSSL](http://pypi.python.org/pypi/pyOpenSSL) 0.12 or newer.
+* [pyasn1](http://pypi.python.org/pypi/pyasn1) 0.1.2 or newer.
+* [urwid](http://excess.org/urwid/) version 0.9.8 or newer.
+* [PIL](http://www.pythonware.com/products/pil/) version 1.1 or newer.
+* [lxml](http://lxml.de/) version 2.3 or newer.
+
+The following auxiliary components may be needed if you plan to hack on
+mitmproxy:
+
+* The test suite uses the [pry](http://github.com/cortesi/pry) unit testing
+  library.
+* Rendering the documentation requires [countershape](http://github.com/cortesi/countershape).
+
+__mitmproxy__ is tested and developed on OSX, Linux and OpenBSD. Windows is not
+supported at the moment.
+
+You should also make sure that your console environment is set up with the
+following: 
+    
+* EDITOR environment variable to determine the external editor.
+* PAGER environment variable to determine the external pager.
+* Appropriate entries in your mailcap files to determine external
+  viewers for request and response contents.

README.rst

@@ -1,189 +0,0 @@
-mitmproxy
-^^^^^^^^^
-
-|travis| |appveyor| |coverage| |latest_release| |python_versions|
-
-This repository contains the **mitmproxy** and **pathod** projects.
-
-``mitmproxy`` is an interactive, SSL-capable intercepting proxy with a console
-interface.
-
-``mitmdump`` is the command-line version of mitmproxy. Think tcpdump for HTTP.
-
-``mitmweb`` is a web-based interface for mitmproxy.
-
-``pathoc`` and ``pathod`` are perverse HTTP client and server applications
-designed to let you craft almost any conceivable HTTP request, including ones
-that creatively violate the standards.
-
-
-Documentation & Help
---------------------
-
-
-General information, tutorials, and precompiled binaries can be found on the mitmproxy
-and pathod websites.
-
-|mitmproxy_site|
-
-The latest documentation for mitmproxy is also available on ReadTheDocs.
-
-|mitmproxy_docs|
-
-
-Join our discussion forum on Discourse to ask questions, help
-each other solve problems, and come up with new ideas for the project.
-
-|mitmproxy_discourse|
-
-
-Join our developer chat on Slack if you would like to contribute to mitmproxy itself.
-
-|slack|
-
-
-Installation
-------------
-
-The installation instructions are `here <http://docs.mitmproxy.org/en/stable/install.html>`__.
-If you want to contribute changes, keep on reading.
-
-Contributing
-------------
-
-As an open source project, mitmproxy welcomes contributions of all forms. If you would like to bring the project forward,
-please consider contributing in the following areas:
-
-- **Maintenance:** We are *incredibly* thankful for individuals who are stepping up and helping with maintenance. This includes (but is not limited to) triaging issues, reviewing pull requests and picking up stale ones, helping out other users in our forums_, creating minimal, complete and verifiable examples or test cases for existing bug reports, updating documentation, or fixing minor bugs that have recently been reported.
-- **Code Contributions:** We actively mark issues that we consider are `good first contributions`_. If you intend to work on a larger contribution to the project, please come talk to us first.
-
-Development Setup
------------------
-
-To get started hacking on mitmproxy, please follow the `advanced installation`_ steps to install mitmproxy from source, but stop right before running ``pip3 install mitmproxy``. Instead, do the following:
-
-.. code-block:: text
-
-    git clone https://github.com/mitmproxy/mitmproxy.git
-    cd mitmproxy
-    ./dev.sh  # "powershell .\dev.ps1" on Windows
-
-
-The *dev* script will create a `virtualenv`_ environment in a directory called "venv"
-and install all mandatory and optional dependencies into it. The primary
-mitmproxy components - mitmproxy and pathod - are installed as
-"editable", so any changes to the source in the repository will be reflected
-live in the virtualenv.
-
-The main executables for the project - ``mitmdump``, ``mitmproxy``,
-``mitmweb``, ``pathod``, and ``pathoc`` - are all created within the
-virtualenv. After activating the virtualenv, they will be on your $PATH, and
-you can run them like any other command:
-
-.. code-block:: text
-
-    . venv/bin/activate  # "venv\Scripts\activate" on Windows
-    mitmdump --version
-
-Testing
--------
-
-If you've followed the procedure above, you already have all the development
-requirements installed, and you can run the full test suite (including tests for code style and documentation) with tox_:
-
-.. code-block:: text
-
-    tox
-
-For speedier testing, we recommend you run `pytest`_ directly on individual test files or folders:
-
-.. code-block:: text
-
-    cd test/mitmproxy/addons
-    pytest --cov mitmproxy.addons.anticache --looponfail test_anticache.py
-
-As pytest does not check the code style, you probably want to run ``tox -e lint`` before committing your changes.
-
-Please ensure that all patches are accompanied by matching changes in the test
-suite. The project tries to maintain 100% test coverage and enforces this strictly for some parts of the codebase.
-
-Documentation
--------------
-
-The mitmproxy documentation is build using Sphinx_, which is installed
-automatically if you set up a development environment as described above. After
-installation, you can render the documentation like this:
-
-.. code-block:: text
-
-    cd docs
-    make clean
-    make html
-    make livehtml
-
-The last command invokes `sphinx-autobuild`_, which watches the Sphinx directory and rebuilds
-the documentation when a change is detected.
-
-Code Style
-----------
-
-Keeping to a consistent code style throughout the project makes it easier to
-contribute and collaborate. Please stick to the guidelines in
-`PEP8`_ and the `Google Style Guide`_ unless there's a very
-good reason not to.
-
-This is automatically enforced on every PR. If we detect a linting error, the
-PR checks will fail and block merging. You can run our lint checks yourself
-with the following command:
-
-.. code-block:: text
-
-    tox -e lint
-
-
-.. |mitmproxy_site| image:: https://shields.mitmproxy.org/api/https%3A%2F%2F-mitmproxy.org-blue.svg
-    :target: https://mitmproxy.org/
-    :alt: mitmproxy.org
-
-.. |mitmproxy_docs| image:: https://shields.mitmproxy.org/api/docs-latest-brightgreen.svg
-    :target: http://docs.mitmproxy.org/en/latest/
-    :alt: mitmproxy documentation
-
-.. |mitmproxy_discourse| image:: https://shields.mitmproxy.org/api/https%3A%2F%2F-discourse.mitmproxy.org-orange.svg
-    :target: https://discourse.mitmproxy.org
-    :alt: Discourse: mitmproxy
-
-.. |slack| image:: http://slack.mitmproxy.org/badge.svg
-    :target: http://slack.mitmproxy.org/
-    :alt: Slack Developer Chat
-
-.. |travis| image:: https://shields.mitmproxy.org/travis/mitmproxy/mitmproxy/master.svg?label=travis%20ci
-    :target: https://travis-ci.org/mitmproxy/mitmproxy
-    :alt: Travis Build Status
-
-.. |appveyor| image:: https://shields.mitmproxy.org/appveyor/ci/mhils/mitmproxy/master.svg?label=appveyor%20ci
-    :target: https://ci.appveyor.com/project/mhils/mitmproxy
-    :alt: Appveyor Build Status
-
-.. |coverage| image:: https://shields.mitmproxy.org/codecov/c/github/mitmproxy/mitmproxy/master.svg?label=codecov
-    :target: https://codecov.io/gh/mitmproxy/mitmproxy
-    :alt: Coverage Status
-
-.. |latest_release| image:: https://shields.mitmproxy.org/pypi/v/mitmproxy.svg
-    :target: https://pypi.python.org/pypi/mitmproxy
-    :alt: Latest Version
-
-.. |python_versions| image:: https://shields.mitmproxy.org/pypi/pyversions/mitmproxy.svg
-    :target: https://pypi.python.org/pypi/mitmproxy
-    :alt: Supported Python versions
-
-.. _`advanced installation`: http://docs.mitmproxy.org/en/latest/install.html#advanced-installation
-.. _virtualenv: https://virtualenv.pypa.io/
-.. _`pytest`: http://pytest.org/
-.. _tox: https://tox.readthedocs.io/
-.. _Sphinx: http://sphinx-doc.org/
-.. _sphinx-autobuild: https://pypi.python.org/pypi/sphinx-autobuild
-.. _PEP8: https://www.python.org/dev/peps/pep-0008
-.. _`Google Style Guide`: https://google.github.io/styleguide/pyguide.html
-.. _forums: https://discourse.mitmproxy.org/
-.. _`good first contributions`: https://github.com/mitmproxy/mitmproxy/issues?q=is%3Aissue+is%3Aopen+label%3Agood-first-contribution

README.txt

@@ -0,0 +1,84 @@
+**mitmproxy** is an SSL-capable man-in-the-middle proxy for HTTP. It provides a
+console interface that allows traffic flows to be inspected and edited on the
+fly.
+
+**mitmdump** is the command-line version of mitmproxy, with the same
+functionality but without the user interface. Think tcpdump for HTTP.
+
+Complete documentation and a set of practical tutorials is included in the
+distribution package, and is also available at mitmproxy.org_.
+
+
+Features
+--------
+
+- Intercept HTTP requests and responses and modify them on the fly.
+- Save complete HTTP conversations for later replay and analysis.
+- Replay the client-side of an HTTP conversations.
+- Replay HTTP responses of a previously recorded server.
+- Reverse proxy mode to forward traffic to a specified server.
+- Make scripted changes to HTTP traffic using Python. 
+- SSL certificates for interception are generated on the fly.
+
+
+Download
+--------
+
+Releases and rendered documentation can be found on the mitmproxy website:
+
+mitmproxy.org_
+
+Source is hosted on github: 
+
+`github.com/cortesi/mitmproxy`_
+
+
+Community
+---------
+
+Come join us in the #mitmproxy channel on the OFTC IRC network
+(irc.oftc.net, port 6667).
+
+We also have a mailing list, hosted here:
+
+http://groups.google.com/group/mitmproxy
+
+
+Requirements
+------------
+
+* Python_ 2.6.x or 2.7.x.
+* PyOpenSSL_ 0.12 or newer.
+* pyasn1_ 0.1.2 or newer.
+* urwid_  version 0.9.8 or newer.
+* PIL_  version 1.1 or newer.
+* lxml_ version 2.3 or newer.
+
+The following auxiliary components may be needed if you plan to hack on
+mitmproxy:
+
+* The test suite uses the pry_ unit testing
+  library.
+* Rendering the documentation requires countershape_.
+
+**mitmproxy** is tested and developed on OSX, Linux and OpenBSD. Windows is not
+supported at the moment.
+
+You should also make sure that your console environment is set up with the
+following: 
+    
+* EDITOR environment variable to determine the external editor.
+* PAGER environment variable to determine the external pager.
+* Appropriate entries in your mailcap files to determine external
+  viewers for request and response contents.
+
+.. _mitmproxy.org: http://mitmproxy.org
+.. _github.com/cortesi/mitmproxy: http://github.com/cortesi/mitmproxy
+.. _python: http://www.python.org
+.. _PyOpenSSL: http://pypi.python.org/pypi/pyOpenSSL
+.. _pyasn1: http://pypi.python.org/pypi/pyasn1
+.. _PIL: http://www.pythonware.com/products/pil/
+.. _lxml: http://lxml.de/
+.. _urwid: http://excess.org/urwid/
+.. _pry: http://github.com/cortesi/pry
+.. _countershape: http://github.com/cortesi/countershape

dev.ps1

@@ -1,20 +0,0 @@
-$ErrorActionPreference = "Stop"
-
-$pyver = python --version
-if($pyver -notmatch "3\.[5-9]") {
-    Write-Warning "Unexpected Python version, expected Python 3.5 or above: $pyver"
-}
-
-python -m venv .\venv --copies
-& .\venv\Scripts\activate.ps1
-
-python -m pip install --disable-pip-version-check -U pip
-cmd /c "pip install -r requirements.txt 2>&1"
-
-echo @"
-
-  * Created virtualenv environment in .\venv.
-  * Installed all dependencies into the virtualenv.
-  * Activated virtualenv environment.
-
-"@

dev.sh

@@ -1,15 +0,0 @@
-#!/bin/sh
-set -e
-set -x
-
-echo "Creating dev environment in ./venv..."
-
-python3 -m venv venv
-. venv/bin/activate
-pip3 install -U pip setuptools
-pip3 install -r requirements.txt
-
-echo ""
-echo "  * Created virtualenv environment in ./venv."
-echo "  * Installed all dependencies into the virtualenv."
-echo "  * You can now activate the $(python3 --version) virtualenv with this command: \`. venv/bin/activate\`"

doc-src/02-docstyle.css

@@ -0,0 +1,137 @@
+
+a {
+    color: #3F8ED8;
+    text-decoration: none;
+}
+
+
+#hd.doc {
+    -x-system-font:none;
+    font-family: Helvetica,Arial,Tahoma,Verdana,Sans-Serif;
+    color: #444444;
+    margin: 0;
+    margin-bottom: 1em;
+}
+
+#hd.doc h1 {
+    letter-spacing: 3px;
+    font-size: 2.5em;
+    margin: 0.3em 0;
+    font-weight: normal;
+}
+
+#nav {
+    float: right;
+}
+
+
+#bd {
+    font: 16px/21px "HelveticaNeue","Helvetica Neue",Helvetica,Arial,sans-serif;
+    line-height: 1.5;
+    color: #444444;
+}
+
+#bd h1, #bd h2, #bd h3 {
+    font-family: "Georgia","Times New Roman",Helvetica,Arial,sans-serif;
+    font-weight: normal;
+    color: #181818;
+}
+
+#bd h1 {
+    font-size: 1.9em;
+    border-bottom: 2px solid #ff7033;
+    margin-top: 5px;
+    margin-bottom: 5px;
+}
+
+#bd h2 {
+    font-size: 1.4em;
+    border-bottom: 1px solid #cccccc;
+    margin-top: 5px;
+    margin-bottom: 5px;
+}
+
+
+#bd h3 {
+    margin-bottom: 0px;
+}
+
+#bd p {
+    margin: 1em 0;
+    margin-top: 0.5em;
+}
+
+/* Keyboard shortcuts */
+#bd em {
+    font-weight: bold;
+    color: #00A700; 
+    font-style: normal;
+}
+
+#ft.doc {
+    color: #aaa;
+    border-top: 1px solid #aaa;
+    clear: both;
+    margin-top: 2em;
+    font-size: 0.8em;
+    letter-spacing: 0.5px;
+}
+
+.faq .question {
+    font-size: 1.1em;
+    font-weight: bold;
+}
+
+pre {
+    font-size: 0.9em;
+    line-height: 1.4;
+    padding: 10px;
+    background-color: #dddddd;
+    margin: 1em 0;
+}
+
+.terminal {
+    color: #c0c0c0;
+    font-size: 1em;
+    background: #000000;
+}
+
+.docindex {
+    font-size: 1.3em;
+    line-height: 1.3;
+    margin-top: 0.1em;
+    margin-bottom: 0;
+    margin-left: 0px;
+}
+
+.docindex li {
+    list-style-position: inside;
+    margin-left: 0;
+}
+
+.docindex ul {
+    margin-left: 2em;
+    margin-top: 0.1em;
+    margin-bottom: 0.1em;
+}
+
+li a {
+    text-decoration: none;
+}
+
+.highlight {
+    font-size: 14px;
+}
+.example_legend{
+    line-height: 1;
+    font-size: 12px;
+}
+.example pre {
+    margin: 0;
+}
+
+.kvtable th {
+    text-align: left;
+    white-space: nowrap;
+}
+

doc-src/_layout.html

@@ -0,0 +1,30 @@
+<div id="doc">
+    <div style="" id="hd" class="doc">
+        <!--(block nav)-->
+        <div id="nav">
+            <!--(block pb)-->
+            <a href="@!urlTo(previous)!@">prev</a>
+            <!--(end)-->
+            <!--(block nb)-->
+            <a href="@!urlTo(next)!@">next</a>
+            <!--(end)-->
+            $!pb if previous else "prev"!$ |
+            <a href="@!urlTo('/index.html')!@">index</a> |
+            $!nb if next else "next"!$
+        </div>
+        <!--(end)-->
+        $!nav if this.title!="docs" else ""!$
+        <h1><a href="@!urlTo("/index.html")!@">mitmproxy 0.8 docs</a></h1>
+    </div>
+    <div id="bd">
+        <div id="yui-main">
+            <div style="" class="yui-b">
+                $!title if this.title!="docs" else ""!$
+                $!body!$
+            </div>
+        </div>
+    </div>
+    <div style="" id="ft" class="doc">
+        <p>@!copyright!@</p>
+    </div>
+</div>

doc-src/_websitelayout.html

@@ -0,0 +1,42 @@
+<a href="http://github.com/cortesi/mitmproxy"><img style="position: absolute; top: 0; right: 0; border: 0;" src="https://d3nwyuy0nl342s.cloudfront.net/img/e6bef7a091f5f3138b8cd40bc3e114258dd68ddf/687474703a2f2f73332e616d617a6f6e6177732e636f6d2f6769746875622f726962626f6e732f666f726b6d655f72696768745f7265645f6161303030302e706e67" alt="Fork me on GitHub"></a>
+<div class="yui-t7" id="doc">
+    <div style="" id="hd">
+        <div class="HorizontalNavBar">
+            <ul>
+                <li class="inactive"><a href="@!urlTo("/index.html")!@">home</a></li>
+                <li class="active"><a href="@!urlTo("doc/index.html")!@">docs</a></li>
+                <li class="inactive"><a href="@!urlTo("/about.html")!@">about</a></li>
+            </ul>
+        </div>
+        <h1><a href="@!urlTo("/index.html")!@">mitmproxy</a> </h1>
+        <br>
+        <p>an SSL-capable man-in-the-middle proxy</p>
+    </div>
+    <div id="bd">
+        <div id="yui-main">
+            <div style="" class="yui-b">
+                <!--(block nav)-->
+                <div id="nav">
+                    <!--(block pb)-->
+                    <a href="@!urlTo(previous)!@">prev</a>
+                    <!--(end)-->
+                    <!--(block nb)-->
+                    <a href="@!urlTo(next)!@">next</a>
+                    <!--(end)-->
+                    $!pb if previous and not previous.parent.root else "prev"!$ |
+                    <a href="@!urlTo('doc/index.html')!@">index</a> |
+                    $!nb if next and not next.parent.root else "next"!$
+                </div>
+                <!--(end)-->
+                $!nav if this.title!="docs" else ""!$
+                $!title if this.title!="docs" else "<h1>mitmproxy 0.8 docs</h1>"!$
+                $!body!$
+            </div>
+        </div>
+    </div>
+    <div style="" id="ft">
+        <p>Copyright 2011 Aldo Cortesi</p>
+    </div>
+</div>
+
+$!ga!$

doc-src/admin.html

@@ -0,0 +1,7 @@
+
+Please send any comments, suggestions and bug reports to <a href="mailto:$!docMaintainerEmail!$">$!docMaintainerEmail!$</a>.
+
+__mitmproxy__ is licensed under Version 3 of the Gnu General Public License,
+the full text of which can be found in the LICENSE file in the source
+distribution.
+

doc-src/anticache.html

@@ -0,0 +1,10 @@
+
+- 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, and during [client
+replay](@!urlTo("clientreplay.html")!@).
+

doc-src/certinstall/android.html

@@ -0,0 +1,103 @@
+
+The proxy situation on Android is [an
+embarrasment](http://code.google.com/p/android/issues/detail?id=1273).  It's
+scarcely credible, but Android didn't have a global proxy setting at all until
+quite recently, and it's still not supported on many common Android versions.
+In the meantime the app ecosystem has grown used to life without this basic
+necessity, and many apps merrily ignore it even if it's there. The upshot is
+that in many cases the only way to make interception work on Android is to do
+it without relying on the proxy settings.
+
+We used an Asus Transformer Prime TF201 with Android 4.0.3 in the examples
+below - your device may differ, but the broad process should be similar. 
+
+
+Installing the mitmproxy certificate
+====================================
+
+The first step is to install mitmproxy's interception certificate on the
+Android device. In your ~/.mitmproxy directory, there should be a file called
+__mitmproxy-ca-cert.cer__ - we need to transfer this file to
+__/sdcard/Downloads__ on the Android device. If this file doesn't exist for
+you, your certs were generated with an older version of mitmproxy - just copy
+the __mitmproxy-ca-cert.pem__ file to __mitmproxy-ca-cert.cer__ and proceed
+from there.
+
+In this case, we're using wget from Better Terminal Emulator Pro to transfer
+the certificate from a local HTTP server. Other terminal applications may work,
+and you might also transfer the file via external media like an SDcard:
+
+<img src="android-shellwgetmitmproxyca.png"/>
+
+Once we have the certificate on the local disk, we need to import it into the
+list of trusted CAs. Go to Settings -&gt; Security -&gt; Credential Storage,
+and select "Install from storage":
+
+<img src="android-settingssecuritymenu.png"/>
+
+The certificate in /sdcard/Downloads is automatically located and offered for
+installation. Installing the cert will delete the download file from the local
+disk:
+
+<img src="android-settingssecurityinstallca.png"/>
+
+Afterwards, you should see the certificate listed in the Trusted Credentials
+store:
+
+<img src="android-settingssecurityuserinstalledca.png"/>
+
+If you're lucky enough to be working with an app that obeys the wireless proxy
+settings, you're just about done - simply configure the settings to point at
+mitmproxy. If not, proceed to the next step...
+
+
+Working around Android's proxy shortcomings
+===========================================
+
+In response to Android's proxy situation, a number of apps have been created to
+duct-tape proxy support onto the OS. These tools work by running a rudimentary
+local proxy on the device, and forwarding all traffic destined for HTTP/S ports
+to it using iptables. Since the proxy is running locally, it can detect what
+the final IP address of the redirected traffic would have been. The local proxy
+then connects to a user-configured upstream proxy, and initiates a proxy
+CONNECT request to the destination IP.
+
+Now, if the configured upstream proxy is mitmproxy, we have a slight problem.
+Proxy requests from the Android device in this scheme will specify only the
+destination IP address, __not__ the destination domain. Mitmproxy needs the
+target domain to generate a valid interception certificate. The solution is
+mitmproxy's [upstream certificate](@!urlTo("upstreamcerts.html")!@) option.
+When this is active, mitmproxy makes a connection to the upstream server to
+obtain the certificate Common Name and Subject Alternative Names. 
+
+Adding all this together, we can achieve reliable Android interception with
+only a few more minutes of setup. The instructions below show how to set up an
+Android device with
+[ProxyDroid](https://play.google.com/store/apps/details?id=org.proxydroid) (the
+local "duct-tape" proxy implementation) to achieve interception.
+
+Install ProxyDroid
+------------------
+
+First, root your device - this is required to install ProxyDroid. Then install
+ProxyDroid from the Google Play store:
+
+<img src="android-proxydroidinstall.png"/>
+
+You will be prompted for super-user access, which you must allow. Next, enter
+the ProxyDroid settings, and change the proxy settings to point to your
+mitmproxy instance. When you're done, it should look something like this:
+
+<img src="android-proxydroidsettings.png"/>
+
+In this case, our mitmproxy instance is at the host __maru.otago.ac.nz__,
+running on port __8080__.
+
+When you start mitmproxy, make sure that the upstream certificate option is set
+(use the _--upstream-cert_ command-line option, or enable it interactively
+using the _o_ shortcut):
+
+<pre class="terminal">
+mitmproxy --upstream-cert
+</pre>
+

doc-src/certinstall/firefox.html

@@ -0,0 +1,19 @@
+
+How to install the __mitmproxy__ certificate authority in Firefox:
+
+### 1. If needed, copy the ~/.mitmproxy/mitmproxy-ca-cert.pem file to the target.
+
+### 2: Open preferences, click on "Advanced", then select"Encryption":
+
+<img src="@!urlTo('firefox3.jpg')!@"/>
+
+### 3: Click "View Certificates", "Import", and select the certificate file: 
+
+<img src="@!urlTo('firefox3-import.jpg')!@"/>
+
+### 4: Tick "Trust this CS to identify web sites", and click "Ok":
+
+<img src="@!urlTo('firefox3-trust.jpg')!@"/>
+
+You should now see the mitmproxy certificate listed in the Authorities tab.
+

doc-src/certinstall/index.py

@@ -0,0 +1,9 @@
+from countershape import Page
+
+pages = [
+    Page("firefox.html", "Firefox"),
+    Page("osx.html", "OSX"),
+    Page("windows7.html", "Windows 7"),
+    Page("ios.html", "IOS"),
+    Page("android.html", "Android"),
+]

doc-src/certinstall/ios.html

@@ -0,0 +1,18 @@
+
+How to install the __mitmproxy__ certificate authority on IOS devices:
+
+### 1: Set up the Mail app on the device to receive email.
+
+### 2: Mail the mitmproxy-ca-cert.pem file to the device, and tap on the attachment.
+
+### 3: You will be prompted to install a profile. Click "Install":
+
+<img src="@!urlTo('ios-profile.png')!@"/>
+
+### 4: Accept the warning by clicking "Install" again:
+
+<img src="@!urlTo('ios-warning.png')!@"/>
+
+### 5: The certificate should now be trusted:
+
+<img src="@!urlTo('ios-installed.png')!@"/>

doc-src/certinstall/osx.html

@@ -0,0 +1,13 @@
+
+How to install the __mitmproxy__ certificate authority in OSX:
+
+### 1: Open Finder, and double-click on the mitmproxy-ca-cert.pem file.
+
+
+### 2: You will be prompted to add the certificate. Click "Always Trust": 
+
+<img src="@!urlTo('osx-addcert-alwaystrust.png')!@"/>
+
+You may be prompted for your password. You should now see the mitmproxy cert
+listed under "Certificates".
+

doc-src/certinstall/windows7.html

@@ -0,0 +1,19 @@
+
+How to install the __mitmproxy__ certificate authority in Windows 7:
+
+### 1: Copy the ~/.mitmproxy/mitmproxy-ca-cert.p12 file to the target system.
+
+### 2: Double-click the certificate file. You should see a certificate import wizard:
+
+<img src="@!urlTo('win7-wizard.png')!@"/>
+
+### 3: Click "Next" until you're prompted for the certificate store:
+
+<img src="@!urlTo('win7-certstore.png')!@"/>
+
+### 4: Select "Place all certificates in the following store", and select "Trusted Root Certification Authorities":
+
+<img src="@!urlTo('win7-certstore-trustedroot.png')!@"/>
+
+### 5: Click "Next" and "Finish". 
+

doc-src/clientreplay.html

@@ -1,7 +1,6 @@
-.. _clientreplay:
 
-Client-side replay
-==================
+- command-line: _-c path_ 
+- mitmproxy shortcut: _c_
 
 Client-side replay does what it says on the tin: you provide a previously saved
 HTTP conversation, and mitmproxy replays the client requests one by one. Note
@@ -10,9 +9,6 @@ before starting the next request. This might differ from the recorded
 conversation, where requests may have been made concurrently.
 
 You may want to use client-side replay in conjunction with the
-:ref:`anticache` option, to make sure the server responds with complete data.
+[anticache](@!urlTo("anticache.html")!@) option. 
+
 
-================== ===========
-command-line       ``-c path``
-mitmproxy shortcut :kbd:`R` then :kbd:`c`
-================== ===========

doc-src/faq.html

@@ -0,0 +1,19 @@
+
+## Any tips for running mitmproxy on OSX?
+
+You can use the OSX <b>open</b> program to create a simple and effective
+<b>~/.mailcap</b> file to view HTTP bodies:
+
+<pre>
+application/*; /usr/bin/open -Wn %s
+audio/*; /usr/bin/open -Wn %s
+image/*; /usr/bin/open -Wn %s
+video/*; /usr/bin/open -Wn %s
+</pre>
+
+
+## I'd like to hack on mitmproxy. What should I work on?
+
+There's a __todo__ file at the top of the source tree that outlines a variety
+of tasks, from simple to complex. If you don't have your own itch, feel free to
+scratch one of those!

doc-src/filters.html

@@ -1,38 +1,34 @@
-.. _filters:
 
-Filter expressions
-==================
-
-Many commands in :program:`mitmproxy` and :program:`mitmdump` take a filter expression.
+Many commands in __mitmproxy__ and __mitmdump__ take a filter expression.
 Filter expressions consist of the following operators:
 
-.. documentedlist::
-    :header: "Expression" "Description"
-    :listobject: mitmproxy.flowfilter.help
+<table>
+    <!--(for i in filt_help)-->
+        <tr>
+            <td class="filt_cmd">@!i[0]!@</td>
+            <td class="filt_help">@!i[1]!@</td>
+        </tr>
+    <!--(end)-->
+</table>
 
 - Regexes are Python-style
 - Regexes can be specified as quoted strings
 - Header matching (~h, ~hq, ~hs) is against a string of the form "name: value".
 - Strings with no operators are matched against the request URL.
-- The default binary operator is &.
+- The default binary operator is &amp;.
 
 Examples
---------
+========
 
 URL containing "google.com":
 
-.. code-block:: none
-
     google\.com
 
 Requests whose body contains the string "test":
 
-.. code-block:: none
-
     ~q ~b test
 
 Anything but requests with a text/html content type:
 
-.. code-block:: none
+    !(~q & ~t \"text/html\")
 
-    !(~q & ~t "text/html")

doc-src/index.html

@@ -0,0 +1,37 @@
+
+<ul class="docindex">
+    <li><a href="@!urlTo("intro.html")!@">Introduction</a></li>
+    <li><a href="@!urlTo("install.html")!@">Installation</a></li>
+    <li><a href="@!urlTo("mitmproxy.html")!@">mitmproxy</a></li>
+    <li><a href="@!urlTo("mitmdump.html")!@">mitmdump</a></li>
+    <li>Features</li>
+    <ul>
+        <li><a href="@!urlTo("clientreplay.html")!@">Client-side replay</a></li>
+        <li><a href="@!urlTo("serverreplay.html")!@">Server-side replay</a></li>
+        <li><a href="@!urlTo("sticky.html")!@">Sticky cookies and auth</a></li>
+        <li><a href="@!urlTo("reverseproxy.html")!@">Reverse proxy mode</a></li>
+        <li><a href="@!urlTo("upstreamcerts.html")!@">Upstream Certs</a></li>
+        <li><a href="@!urlTo("replacements.html")!@">Replacements</a></li>
+        <li><a href="@!urlTo("anticache.html")!@">Anticache</a></li>
+        <li><a href="@!urlTo("filters.html")!@">Filter expressions</a></li>
+    </ul>
+    <li><a href="@!urlTo("scripts.html")!@">Scripts</a></li>
+    <li><a href="@!urlTo("ssl.html")!@">Setting up SSL interception</a></li>
+        <ul>
+            <li><a href="@!urlTo("certinstall/firefox.html")!@">Firefox</a></li>
+            <li><a href="@!urlTo("certinstall/osx.html")!@">OSX</a></li>
+            <li><a href="@!urlTo("certinstall/windows7.html")!@">Windows 7</a></li>
+            <li><a href="@!urlTo("certinstall/ios.html")!@">iPhone/iPad</a></li>
+            <li><a href="@!urlTo("certinstall/android.html")!@">Android</a></li>
+        </ul>
+     <li><a href="@!urlTo("library.html")!@">libmproxy</a></li>
+     <li>Tutorials</li>
+        <ul>
+            <li> <a href="@!urlTo("tutorials/30second.html")!@">Client replay: a 30 second example</a> </li>
+            <li> <a href="@!urlTo("tutorials/gamecenter.html")!@">Setting highscores on Apple's GameCenter</a> </li>
+        </ul>
+     <li><a href="@!urlTo("faq.html")!@">FAQ</a></li>
+     <li><a href="@!urlTo("admin.html")!@">Administrivia</a></li>
+</ul>
+
+

doc-src/index.py

@@ -0,0 +1,89 @@
+import os, sys
+import countershape
+from countershape import Page, Directory, PythonModule, markup
+import countershape.template
+sys.path.insert(0, "..")
+from libmproxy import filt
+
+MITMPROXY_SRC = "~/git/public/mitmproxy"
+
+if ns.options.website:
+    ns.title = countershape.template.Template(None, "<h1>@!this.title!@</h1>")
+    this.layout = countershape.Layout("_websitelayout.html")
+else:
+    ns.title = countershape.template.Template(None, "<h1>@!this.title!@</h1>")
+    this.layout = countershape.Layout("_layout.html")
+
+this.markup = markup.Markdown()
+ns.docMaintainer = "Aldo Cortesi"
+ns.docMaintainerEmail = "aldo@corte.si"
+ns.copyright = u"\u00a9 mitmproxy project, 2012"
+
+ns.index = countershape.widgets.SiblingPageIndex('/index.html', divclass="pageindex")
+
+def mpath(p):
+    p = os.path.join(MITMPROXY_SRC, p)
+    return os.path.expanduser(p)
+
+ns.license = file(mpath("LICENSE")).read()
+ns.index_contents = file(mpath("README.mkd")).read()
+
+
+
+top = os.path.abspath(os.getcwd())
+def example(s):
+    d = file(mpath(s)).read()
+    extemp = """<div class="example">%s<div class="example_legend">(%s)</div></div>"""
+    return extemp%(countershape.template.Syntax("py")(d), s)
+
+
+ns.example = example
+
+filt_help = []
+for i in filt.filt_unary:
+    filt_help.append(
+        ("~%s"%i.code, i.help)
+    )
+for i in filt.filt_rex:
+    filt_help.append(
+        ("~%s regex"%i.code, i.help)
+    )
+for i in filt.filt_int:
+    filt_help.append(
+        ("~%s int"%i.code, i.help)
+    )
+filt_help.sort()
+filt_help.extend(
+    [
+        ("!", "unary not"),
+        ("&", "and"),
+        ("|", "or"),
+        ("(...)", "grouping"),
+    ]
+)
+ns.filt_help = filt_help
+
+
+
+pages = [
+    Page("index.html", "docs"),
+    Page("intro.html", "Introduction"),
+    Page("install.html", "Installation"),
+    Page("mitmproxy.html", "mitmproxy"),
+    Page("mitmdump.html", "mitmdump"),
+    Page("clientreplay.html", "Client-side replay"),
+    Page("serverreplay.html", "Server-side replay"),
+    Page("sticky.html", "Sticky cookies and auth"),
+    Page("upstreamcerts.html", "Upstream Certs"),
+    Page("replacements.html", "Replacements"),
+    Page("reverseproxy.html", "Reverse proxy mode"),
+    Page("anticache.html", "Anticache"),
+    Page("filters.html", "Filter expressions"),
+    Page("scripts.html", "Scripts"),
+    Page("ssl.html", "Setting up SSL interception"),
+    Directory("certinstall"),
+    Page("library.html", "libmproxy: mitmproxy as a library"),
+    Directory("tutorials"),
+    Page("faq.html", "FAQ"),
+    Page("admin.html", "Administrivia")
+]

doc-src/install.html

@@ -0,0 +1,57 @@
+
+## Using Pip 
+
+The preferred way to install mitmproxy is to use
+[pip](http://pypi.python.org/pypi/pip). A single command will install the
+latest release of mitmproxy, along with all its dependencies:
+
+<pre>
+sudo pip install mitmproxy
+</pre>
+
+
+## From Source
+
+- When installing from source, you will need to install the
+[dependencies](@!urlTo("intro.html")!@) by hand. 
+- Then run the following command from the base of the source distribution:
+    
+<pre>
+sudo python setup.py install
+</pre>
+
+
+## OSX
+
+- Make sure that XCode is installed from the App Store, and that the
+command-line tools have been downloaded (XCode/Preferences/Downloads).
+- Install __pip__ using the following command:
+    
+<pre>
+sudo easy_install pip
+</pre>
+
+- Now use __pip__ to set up the dependencies and do the install:
+
+<pre>
+sudo pip install mitmproxy
+</pre>
+
+This procedure may vary if, for instance, you've installed Python from an
+external source like [homebrew](http://mxcl.github.com/homebrew/). In that
+case, the easiest way to proceed is to first install __easy_install__, then
+continue as above.
+
+There are a few bits of customization you might want to do to make mitmproxy
+comfortable to use. At the moment, mitmproxy's color scheme is optimized for a
+dark background terminal, so you probably want to change the default. You can
+use the OSX <b>open</b> program to create a simple and effective
+<b>~/.mailcap</b> file to view HTTP bodies:
+
+<pre>
+application/*; /usr/bin/open -Wn %s
+audio/*; /usr/bin/open -Wn %s
+image/*; /usr/bin/open -Wn %s
+video/*; /usr/bin/open -Wn %s
+</pre>
+

doc-src/intro.html

@@ -0,0 +1,4 @@
+
+@!index_contents!@
+
+

doc-src/library.html

@@ -0,0 +1,12 @@
+
+All of mitmproxy's basic functionality is exposed through the __libmproxy__
+library. The example below shows a simple implementation of the "sticky cookie"
+functionality included in the interactive mitmproxy program. Traffic is
+monitored for __cookie__ and __set-cookie__ headers, and requests are rewritten
+to include a previously seen cookie if they don't already have one. In effect,
+this lets you log in to a site using your browser, and then make subsequent
+requests using a tool like __curl__, which will then seem to be part of the
+authenticated session.
+
+$!example("examples/stickycookies")!$
+

doc-src/mitmdump.html

@@ -0,0 +1,54 @@
+
+__mitmdump__ is the command-line companion to mitmproxy. It provides
+tcpdump-like functionality to let you view, record, and programmatically
+transform HTTP traffic. See the _--help_ flag output for complete
+documentation.
+
+
+
+## Example: saving traffic
+
+<pre class="terminal">
+> mitmdump -w outfile
+</pre>
+
+Start up mitmdump in proxy mode, and write all traffic to __outfile__. 
+
+
+## Example: client replay
+
+<pre class="terminal">
+> mitmdump -nc outfile
+</pre>
+
+Start mitmdump without binding to the proxy port (_-n_), then replay all
+requests from outfile (_-c filename_). Flags combine in the obvious way, so
+you can replay requests from one file, and write the resulting flows to
+another:
+
+<pre class="terminal">
+> mitmdump -nc srcfile -w dstfile
+</pre>
+
+See the [Client-side Replay](@!urlTo("clientreplay.html")!@) section for more information.
+
+
+## Example: running a script
+
+<pre class="terminal">
+> mitmdump -s examples/add_header.py
+</pre>
+
+This runs the __add_header.py__ example script, which simply adds a new header
+to all responses.
+
+
+## Example: scripted data transformation
+
+<pre class="terminal">
+> mitmdump -ns examples/add_header.py -r srcfile -w dstfile
+</pre>
+
+This command loads flows from __srcfile__, transforms it according to the
+specified script, then writes it back to __dstfile__.
+

doc-src/mitmproxy.html

@@ -0,0 +1,112 @@
+
+__mitmproxy__ is a console tool that allows interactive examination and
+modification of HTTP traffic. Use the _?_ shortcut key to view,
+context-sensitive documentation from any __mitmproxy__ screen.
+
+## Flow list
+
+The flow list shows an index of captured flows in chronological order. 
+
+<img src="@!urlTo("screenshots/mitmproxy.png")!@"/>
+
+- __1__: A GET request, returning a 302 Redirect response.
+- __2__: A GET request, returning 16.75kb of text/html data.
+- __3__: A replayed request. 
+- __4__: Intercepted flows are indicated with orange text. The user may edit
+these flows, and then accept them (using the _a_ key) to continue. In this
+case, the request has been intercepted on the way to the server.
+- __5__: A response intercepted from the server on the way to the client.
+- __6__: The event log can be toggled on and off using the _e_ shortcut key. This
+pane shows events and errors that may not result in a flow that shows up in the
+flow pane.
+- __7__: Flow count.
+- __8__: Various information on mitmproxy's state. In this case, we have an
+interception pattern set to ".*".
+- __9__: Bind address indicator - mitmproxy is listening on port 8080 of all
+interfaces.
+
+
+## Flow view
+
+The __Flow View__ lets you inspect and manipulate a single flow:
+
+<img src="@!urlTo("screenshots/mitmproxy-flowview.png")!@"/>
+
+- __1__: Flow summary.
+- __2__: The Request/Response tabs, showing you which part of the flow you are
+currently viewing. In the example above, we're viewing the Response. Hit _tab_
+to switch between the Response and the Request.
+- __3__: Headers.
+- __4__: Body.
+- __5__: View Mode indicator. In this case, we're viewing the body in __hex__
+mode. The other available modes are __pretty__, which uses a number of
+heuristics to show you a friendly view of various content types, and __raw__,
+which shows you exactly what's there without any changes. You can change modes
+using the _m_ key.
+
+
+## Grid Editor
+
+Much of the data that we'd like to interact with in mitmproxy is structured.
+For instance, headers, queries and form data can all be thought of as a list of
+key/value pairs. Mitmproxy has a built-in editor that lays this type of data
+out in a grid for easy manipulation. 
+
+At the moment, the Grid Editor is used in four parts of mitmproxy:
+
+- Editing request or response headers (_e_ for edit, then _h_ for headers in flow view) 
+- Editing a query string (_e_ for edit, then _q_ for query in flow view)
+- Editing a URL-encoded form (_e_ for edit, then _f_ for form in flow view)
+- Editing replacement patterns (_R_ globally)
+
+If there is is no data, an empty editor will be started to let you add some.
+Here is the editor showing the headers from a request:
+
+<img src="@!urlTo("screenshots/mitmproxy-kveditor.png")!@"/>
+
+To edit, navigate to the key or value you want to modify using the arrow or vi
+navigation keys, and press enter. The background color will change to show that
+you are in edit mode for the specified field:
+
+<img src="@!urlTo("screenshots/mitmproxy-kveditor-editmode.png")!@"/>
+
+Modify the field as desired, then press escape to exit edit mode when you're
+done. You can also add a row (_a_ key), delete a row (_d_ key), spawn an
+external editor on a field (_e_ key). Be sure to consult the context-sensitive
+help (_?_ key) for more.
+
+
+# Example: Interception
+
+__mitmproxy__'s interception functionality lets you pause an HTTP request or
+response, inspect and modify it, and then accept it to send it on to the server
+or client. 
+
+
+### 1: Set an interception pattern
+
+<img src="@!urlTo('mitmproxy-intercept-filt.png')!@"/>
+
+We press _i_ to set an interception pattern. In this case, the __~q__ filter
+pattern tells __mitmproxy__ to intercept all requests. For complete filter
+syntax, see the [Filter expressions](@!urlTo("filters.html")!@) section of this
+document, or the built-in help function in __mitmproxy__.
+
+### 2: Intercepted connections are indicated with orange text:
+
+<img src="@!urlTo('mitmproxy-intercept-mid.png')!@"/>
+
+### 3: You can now view and modify the request:
+
+<img src="@!urlTo('mitmproxy-intercept-options.png')!@"/>
+
+In this case, we viewed the request by selecting it, pressed _e_ for "edit"
+and _m_ for "method" to change the HTTP request method.
+
+### 4: Accept the intercept to continue:
+
+<img src="@!urlTo('mitmproxy-intercept-result.png')!@"/>
+
+Finally, we press _a_ to accept the modified request, which is then sent on to
+the server. In this case, we changed the request from an HTTP GET to
+OPTIONS, and Google's server has responded with a 405 "Method not allowed". 

doc-src/replacements.html

@@ -1,7 +1,5 @@
-.. _replacements:
-
-Replacements
-============
+- command-line: _--replace_, _--replace-from-file_
+- mitmproxy shortcut: _R_
 
 Mitmproxy lets you specify an arbitrary number of patterns that define text
 replacements within flows. Each pattern has 3 components: a filter that defines
@@ -14,59 +12,50 @@ replace hook is triggered on server response, the replacement is only run on
 the Response object leaving the Request intact. You control whether the hook
 triggers on the request, response or both using the filter pattern. If you need
 finer-grained control than this, it's simple to create a script using the
-replacement API on Flow components.
+replacement API on Flow components. 
 
 Replacement hooks are extremely handy in interactive testing of applications.
 For instance you can use a replace hook to replace the text "XSS" with a
 complicated XSS exploit, and then "inject" the exploit simply by interacting
 with the application through the browser. When used with tools like Firebug and
 mitmproxy's own interception abilities, replacement hooks can be an amazingly
-flexible and powerful feature.
+flexible and powerful feature. 
 
 
-On the command-line
--------------------
+## On the command-line
 
 The replacement hook command-line options use a compact syntax to make it easy
 to specify all three components at once. The general form is as follows:
 
-.. code-block:: none
-
     /patt/regex/replacement
 
-Here, **patt** is a mitmproxy filter expression, **regex** is a valid Python
-regular expression, and **replacement** is a string literal. The first
-character in the expression (``/`` in this case) defines what the separation
+Here, __patt__ is a mitmproxy filter expression, __regex__ is a valid Python
+regular expression, and __replacement__ is a string literal. The first
+character in the expression (__/__ in this case) defines what the separation
 character is. Here's an example of a valid expression that replaces "foo" with
 "bar" in all requests:
 
-.. code-block:: none
-
     :~q:foo:bar
 
 In practice, it's pretty common for the replacement literal to be long and
 complex. For instance, it might be an XSS exploit that weighs in at hundreds or
 thousands of characters. To cope with this, there's a variation of the
 replacement hook specifier that lets you load the replacement text from a file.
-So, you might start **mitmdump** as follows:
+So, you might start __mitmdump__ as follows:
 
->>> mitmdump --replace-from-file :~q:foo:~/xss-exploit
+<pre class="terminal">
+mitmdump --replace-from-file :~q:foo:~/xss-exploit
+</pre>
 
-This will load the replacement text from the file ``~/xss-exploit``.
+This will load the replacement text from the file __~/xss-exploit__.
 
-Both the ``--replace`` and ``--replace-from-file`` flags can be passed multiple
+Both the _--replace_ and _--replace-from-file_ flags can be passed multiple
 times.
 
 
-Interactively
--------------
+## Interactively
 
-The :kbd:`R` shortcut key in the mitmproxy options menu (:kbd:`o`) lets you add and edit
-replacement hooks using a built-in editor. The context-sensitive help (:kbd:`?`) has
-complete usage information.
+The _R_ shortcut key in mitmproxy lets you add and edit replacement hooks using
+a built-in editor. The context-sensitive help (_h_) has complete usage
+information.
 
-================== =======================
-command-line       ``--replace``,
-                   ``--replace-from-file``
-mitmproxy shortcut :kbd:`o` then :kbd:`R`
-================== =======================

doc-src/reverseproxy.html

@@ -0,0 +1,8 @@
+
+- command-line: _-P_ http[s]://hostname[:port]
+- mitmproxy shortcut: _P_
+
+In reverse proxy mode, mitmproxy acts as a standard HTTP server and forwards
+all requests to the specified upstream server. Note that the displayed URL for
+flows in this mode will use the value of the __Host__ header field from the
+request, not the reverse proxy server.

doc-src/scripts.html

@@ -0,0 +1,129 @@
+
+__mitmproxy__ has a powerful scripting API that allows you to modify flows
+on-the-fly or rewrite previously saved flows locally. 
+
+The mitmproxy scripting API is event driven - a script is simply a Python
+module that exposes a set of event methods. Here's a complete mitmproxy script
+that adds a new header to every HTTP response before it is returned to the
+client:
+
+$!example("examples/add_header.py")!$
+
+The first argument to each event method is an instance of ScriptContext that
+lets the script interact with the global mitmproxy state. The __response__
+event also gets an instance of Flow, which we can use to manipulate the
+response itself.
+
+
+## Events
+
+### start(ScriptContext)
+
+Called once on startup, before any other events.
+
+
+###clientconnect(ScriptContext, ClientConnect)
+
+Called when a client initiates a connection to the proxy. Note that
+a connection can correspond to multiple HTTP requests.
+
+
+###request(ScriptContext, Flow)
+
+Called when a client request has been received. The __Flow__ object is
+guaranteed to have a non-None __request__ attribute.
+
+
+### response(ScriptContext, Flow)
+
+Called when a server response has been received. The __Flow__ object is
+guaranteed to have non-None __request__ and __response__ attributes.
+
+
+### error(ScriptContext, Flow)
+
+Called when a flow error has occurred, e.g. invalid server responses, or
+interrupted connections. This is distinct from a valid server HTTP error
+response, which is simply a response with an HTTP error code. The __Flow__
+object is guaranteed to have non-None __request__ and __error__ attributes.
+
+
+### clientdisconnect(ScriptContext, ClientDisconnect)
+
+Called when a client disconnects from the proxy.
+
+### done(ScriptContext)
+
+Called once on script shutdown, after any other events.
+
+
+## API
+
+The main classes you will deal with in writing mitmproxy scripts are:
+
+<table class="kvtable">
+    <tr>
+        <th>libmproxy.flow.ClientConnection</th>
+        <td>Describes a client connection.</td>
+    </tr>
+    <tr>
+        <th>libmproxy.flow.ClientDisconnection</th>
+        <td>Describes a client disconnection.</td>
+    </tr>
+    <tr>
+        <th>libmproxy.flow.Error</th>
+        <td>A communications error.</td>
+    </tr>
+    <tr>
+        <th>libmproxy.flow.Flow</th>
+        <td>A collection of objects representing a single HTTP transaction.</td>
+    </tr>
+    <tr>
+        <th>libmproxy.flow.Headers</th>
+        <td>HTTP headers for a request or response.</td>
+    </tr>
+    <tr>
+        <th>libmproxy.flow.ODict</th>
+
+        <td>A dictionary-like object for managing sets of key/value data. There
+        is also a variant called CaselessODict that ignores key case for some
+        calls (used mainly for headers).</td>
+    </tr>
+    <tr>
+        <th>libmproxy.flow.Response</th>
+        <td>An HTTP response.</td>
+    </tr>
+    <tr>
+        <th>libmproxy.flow.Request</th>
+        <td>An HTTP request.</td>
+    </tr>
+    <tr>
+        <th>libmproxy.flow.ScriptContext</th>
+        <td> A handle for interacting with mitmproxy's from within scripts.  </td>
+    </tr>
+    <tr>
+        <th>libmproxy.certutils.SSLCert</th>
+        <td>Exposes information SSL certificates.</td>
+    </tr>
+</table>
+
+The canonical API documentation is the code. You can view the API documentation
+using pydoc (which is installed with Python by default), like this:
+
+<pre class="terminal">
+> pydoc libmproxy.flow.Request
+</pre>
+
+
+## Running scripts on saved flows
+
+Sometimes, we want to run a script on __Flow__ objects that are already
+complete.  This happens when you start a script, and then load a saved set of
+flows from a file (see the "scripted data transformation" example on the
+[mitmdump](@!urlTo("mitmdump.html")!@) page). It also happens when you run a
+one-shot script on a single flow through the _|_ (pipe) shortcut in mitmproxy.
+
+In this case, there are no client connections, and the events are run in the
+following order: __start__, __request__, __response__, __error__, __done__.  If
+the flow doesn't have a __response__ or __error__ associated with it, the
+matching event will be skipped. 

doc-src/serverreplay.html

@@ -0,0 +1,35 @@
+
+- command-line: _-S path_ 
+- mitmproxy shortcut: _S_
+
+Server-side replay lets us replay server responses from a saved HTTP
+conversation.
+
+Matching requests with responses
+--------------------------------
+
+By default, __mitmproxy__ excludes request headers when matching incoming
+requests with responses from the replay file. This works in most circumstances,
+and makes it possible to replay server responses in situations where request
+headers would naturally vary, e.g. using a different user agent. The _--rheader
+headername_ command-line option allows you to override this behaviour by
+specifying individual headers that should be included in matching.
+
+
+Response refreshing
+-------------------
+
+Simply replaying server responses without modification will often result in
+unexpected behaviour. For example cookie timeouts that were in the future at
+the time a conversation was recorded might be in the past at the time it is
+replayed. By default, __mitmproxy__ refreshes server responses before sending
+them to the client. The __date__, __expires__ and __last-modified__ headers are
+all updated to have the same relative time offset as they had at the time of
+recording. So, if they were in the past at the time of recording, they will be
+in the past at the time of replay, and vice versa. Cookie expiry times are
+updated in a similar way.
+
+You can turn off response refreshing using the _--norefresh_ argument, or using
+the _o_ options shortcut within __mitmproxy__.
+
+

doc-src/ssl.html

@@ -0,0 +1,46 @@
+
+The first time __mitmproxy__ or __mitmdump__ is started, the following set of
+certificate files for a dummy Certificate Authority are created in the config
+directory (~/.mitmproxy by default): 
+
+<table>
+    <tr>
+        <td>mitmproxy-ca.pem</td>
+        <td>The private key and certificate in PEM format.</td>
+    </tr>
+    <tr>
+        <td>mitmproxy-ca-cert.pem</td>
+        <td>The certificate in PEM format. Use this to distribute to most
+        non-Windows platforms.</td>
+    </tr>
+    <tr>
+        <td>mitmproxy-ca-cert.p12</td>
+        <td>The certificate in PKCS12 format. For use on Windows.</td>
+    </tr>
+</table>
+    
+This CA is used for on-the-fly generation of dummy certificates for SSL
+interception. Since your browser won't trust the __mitmproxy__ CA out of the
+box (and rightly so), you will see an SSL cert warning every time you visit a
+new SSL domain through __mitmproxy__. When you're testing a single site through
+a browser, just accepting the bogus SSL cert manually is not too much trouble,
+but there are a number of cases where you will want to configure your testing
+system or browser to trust the __mitmproxy__ CA as a signing root authority:
+
+- If you are testing non-browser software that checks SSL cert validity using
+the system certificate store.
+- You are testing an app that makes non-interactive (JSONP, script src, etc.)
+requests to SSL resources. Another workaround in this case is to manually visit
+the page through the browser, and add a certificate exception.
+- You just don't want to deal with the hassle of continuously adding cert
+exceptions.
+
+
+Installing the mitmproxy CA
+---------------------------
+
+* [Firefox](@!urlTo("certinstall/firefox.html")!@)
+* [OSX](@!urlTo("certinstall/osx.html")!@)
+* [Windows 7](@!urlTo("certinstall/windows7.html")!@)
+* [iPhone/iPad](@!urlTo("certinstall/ios.html")!@)
+

doc-src/sticky.html

@@ -1,10 +1,9 @@
-.. _sticky:
 
-Sticky cookies and auth
-=======================
+## Sticky cookies
 
-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
@@ -14,28 +13,22 @@ 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 :ref:`clientreplay` - you can
-record the authentication process once, and simply replay it on startup every time you need
-to interact with the secured resources.
-
-================== ======================
-command-line       ``-t FILTER``
-mitmproxy shortcut :kbd:`o` then :kbd:`t`
-================== ======================
+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.
 
 
-Sticky auth
------------
+## Sticky auth
+
+- 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
+__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 :program:`mitmproxy` doesn't (yet) support
-replay of HTTP Digest authentication.
-
-================== ======================
-command-line       ``-u FILTER``
-mitmproxy shortcut :kbd:`o` then :kbd:`A`
-================== ======================
+authentication through the proxy. Note that __mitmproxy__ doesn't (yet) support
+replay of HTTP Digest authentication. 

doc-src/syntax.css

@@ -0,0 +1,120 @@
+.highlight  { background: #f8f8f8; }
+.highlight .c { color: #408080; font-style: italic } /* Comment */
+.highlight .err { border: 1px solid #FF0000 } /* Error */
+.highlight .k { color: #008000; font-weight: bold } /* Keyword */
+.highlight .o { color: #666666 } /* Operator */
+.highlight .cm { color: #408080; font-style: italic } /* Comment.Multiline */
+.highlight .cp { color: #BC7A00 } /* Comment.Preproc */
+.highlight .c1 { color: #408080; font-style: italic } /* Comment.Single */
+.highlight .cs { color: #408080; font-style: italic } /* Comment.Special */
+.highlight .gd { color: #A00000 } /* Generic.Deleted */
+.highlight .ge { font-style: italic } /* Generic.Emph */
+.highlight .gr { color: #FF0000 } /* Generic.Error */
+.highlight .gh { color: #000080; font-weight: bold } /* Generic.Heading */
+.highlight .gi { color: #00A000 } /* Generic.Inserted */
+.highlight .go { color: #808080 } /* Generic.Output */
+.highlight .gp { color: #000080; font-weight: bold } /* Generic.Prompt */
+.highlight .gs { font-weight: bold } /* Generic.Strong */
+.highlight .gu { color: #800080; font-weight: bold } /* Generic.Subheading */
+.highlight .gt { color: #0040D0 } /* Generic.Traceback */
+.highlight .kc { color: #008000; font-weight: bold } /* Keyword.Constant */
+.highlight .kd { color: #008000; font-weight: bold } /* Keyword.Declaration */
+.highlight .kp { color: #008000 } /* Keyword.Pseudo */
+.highlight .kr { color: #008000; font-weight: bold } /* Keyword.Reserved */
+.highlight .kt { color: #B00040 } /* Keyword.Type */
+.highlight .m { color: #666666 } /* Literal.Number */
+.highlight .s { color: #BA2121 } /* Literal.String */
+.highlight .na { color: #7D9029 } /* Name.Attribute */
+.highlight .nb { color: #008000 } /* Name.Builtin */
+.highlight .nc { color: #0000FF; font-weight: bold } /* Name.Class */
+.highlight .no { color: #880000 } /* Name.Constant */
+.highlight .nd { color: #AA22FF } /* Name.Decorator */
+.highlight .ni { color: #999999; font-weight: bold } /* Name.Entity */
+.highlight .ne { color: #D2413A; font-weight: bold } /* Name.Exception */
+.highlight .nf { color: #0000FF } /* Name.Function */
+.highlight .nl { color: #A0A000 } /* Name.Label */
+.highlight .nn { color: #0000FF; font-weight: bold } /* Name.Namespace */
+.highlight .nt { color: #008000; font-weight: bold } /* Name.Tag */
+.highlight .nv { color: #19177C } /* Name.Variable */
+.highlight .ow { color: #AA22FF; font-weight: bold } /* Operator.Word */
+.highlight .w { color: #bbbbbb } /* Text.Whitespace */
+.highlight .mf { color: #666666 } /* Literal.Number.Float */
+.highlight .mh { color: #666666 } /* Literal.Number.Hex */
+.highlight .mi { color: #666666 } /* Literal.Number.Integer */
+.highlight .mo { color: #666666 } /* Literal.Number.Oct */
+.highlight .sb { color: #BA2121 } /* Literal.String.Backtick */
+.highlight .sc { color: #BA2121 } /* Literal.String.Char */
+.highlight .sd { color: #BA2121; font-style: italic } /* Literal.String.Doc */
+.highlight .s2 { color: #BA2121 } /* Literal.String.Double */
+.highlight .se { color: #BB6622; font-weight: bold } /* Literal.String.Escape */
+.highlight .sh { color: #BA2121 } /* Literal.String.Heredoc */
+.highlight .si { color: #BB6688; font-weight: bold } /* Literal.String.Interpol */
+.highlight .sx { color: #008000 } /* Literal.String.Other */
+.highlight .sr { color: #BB6688 } /* Literal.String.Regex */
+.highlight .s1 { color: #BA2121 } /* Literal.String.Single */
+.highlight .ss { color: #19177C } /* Literal.String.Symbol */
+.highlight .bp { color: #008000 } /* Name.Builtin.Pseudo */
+.highlight .vc { color: #19177C } /* Name.Variable.Class */
+.highlight .vg { color: #19177C } /* Name.Variable.Global */
+.highlight .vi { color: #19177C } /* Name.Variable.Instance */
+.highlight .il { color: #666666 } /* Literal.Number.Integer.Long */
+.grokdoc  { background: #f8f8f8; }
+.grokdoc .c { color: #408080; font-style: italic } /* Comment */
+.grokdoc .err { border: 1px solid #FF0000 } /* Error */
+.grokdoc .k { color: #008000; font-weight: bold } /* Keyword */
+.grokdoc .o { color: #666666 } /* Operator */
+.grokdoc .cm { color: #408080; font-style: italic } /* Comment.Multiline */
+.grokdoc .cp { color: #BC7A00 } /* Comment.Preproc */
+.grokdoc .c1 { color: #408080; font-style: italic } /* Comment.Single */
+.grokdoc .cs { color: #408080; font-style: italic } /* Comment.Special */
+.grokdoc .gd { color: #A00000 } /* Generic.Deleted */
+.grokdoc .ge { font-style: italic } /* Generic.Emph */
+.grokdoc .gr { color: #FF0000 } /* Generic.Error */
+.grokdoc .gh { color: #000080; font-weight: bold } /* Generic.Heading */
+.grokdoc .gi { color: #00A000 } /* Generic.Inserted */
+.grokdoc .go { color: #808080 } /* Generic.Output */
+.grokdoc .gp { color: #000080; font-weight: bold } /* Generic.Prompt */
+.grokdoc .gs { font-weight: bold } /* Generic.Strong */
+.grokdoc .gu { color: #800080; font-weight: bold } /* Generic.Subheading */
+.grokdoc .gt { color: #0040D0 } /* Generic.Traceback */
+.grokdoc .kc { color: #008000; font-weight: bold } /* Keyword.Constant */
+.grokdoc .kd { color: #008000; font-weight: bold } /* Keyword.Declaration */
+.grokdoc .kp { color: #008000 } /* Keyword.Pseudo */
+.grokdoc .kr { color: #008000; font-weight: bold } /* Keyword.Reserved */
+.grokdoc .kt { color: #B00040 } /* Keyword.Type */
+.grokdoc .m { color: #666666 } /* Literal.Number */
+.grokdoc .s { color: #BA2121 } /* Literal.String */
+.grokdoc .na { color: #7D9029 } /* Name.Attribute */
+.grokdoc .nb { color: #008000 } /* Name.Builtin */
+.grokdoc .nc { color: #0000FF; font-weight: bold } /* Name.Class */
+.grokdoc .no { color: #880000 } /* Name.Constant */
+.grokdoc .nd { color: #AA22FF } /* Name.Decorator */
+.grokdoc .ni { color: #999999; font-weight: bold } /* Name.Entity */
+.grokdoc .ne { color: #D2413A; font-weight: bold } /* Name.Exception */
+.grokdoc .nf { color: #0000FF } /* Name.Function */
+.grokdoc .nl { color: #A0A000 } /* Name.Label */
+.grokdoc .nn { color: #0000FF; font-weight: bold } /* Name.Namespace */
+.grokdoc .nt { color: #008000; font-weight: bold } /* Name.Tag */
+.grokdoc .nv { color: #19177C } /* Name.Variable */
+.grokdoc .ow { color: #AA22FF; font-weight: bold } /* Operator.Word */
+.grokdoc .w { color: #bbbbbb } /* Text.Whitespace */
+.grokdoc .mf { color: #666666 } /* Literal.Number.Float */
+.grokdoc .mh { color: #666666 } /* Literal.Number.Hex */
+.grokdoc .mi { color: #666666 } /* Literal.Number.Integer */
+.grokdoc .mo { color: #666666 } /* Literal.Number.Oct */
+.grokdoc .sb { color: #BA2121 } /* Literal.String.Backtick */
+.grokdoc .sc { color: #BA2121 } /* Literal.String.Char */
+.grokdoc .sd { color: #BA2121; font-style: italic } /* Literal.String.Doc */
+.grokdoc .s2 { color: #BA2121 } /* Literal.String.Double */
+.grokdoc .se { color: #BB6622; font-weight: bold } /* Literal.String.Escape */
+.grokdoc .sh { color: #BA2121 } /* Literal.String.Heredoc */
+.grokdoc .si { color: #BB6688; font-weight: bold } /* Literal.String.Interpol */
+.grokdoc .sx { color: #008000 } /* Literal.String.Other */
+.grokdoc .sr { color: #BB6688 } /* Literal.String.Regex */
+.grokdoc .s1 { color: #BA2121 } /* Literal.String.Single */
+.grokdoc .ss { color: #19177C } /* Literal.String.Symbol */
+.grokdoc .bp { color: #008000 } /* Name.Builtin.Pseudo */
+.grokdoc .vc { color: #19177C } /* Name.Variable.Class */
+.grokdoc .vg { color: #19177C } /* Name.Variable.Global */
+.grokdoc .vi { color: #19177C } /* Name.Variable.Instance */
+.grokdoc .il { color: #666666 } /* Literal.Number.Integer.Long */

doc-src/tutorials/30second.html

@@ -1,50 +1,48 @@
-.. _30second:
-
-Client playback: a 30 second example
-====================================
 
 My local cafe is serviced by a rickety and unreliable wireless network,
 generously sponsored with ratepayers' money by our city council. After
 connecting, you  are redirected to an SSL-protected page that prompts you for a
 username and password. Once you've entered your details, you are free to enjoy
 the intermittent dropouts, treacle-like speeds and incorrectly configured
-transparent proxy.
+transparent proxy. 
 
 I tend to automate this kind of thing at the first opportunity, on the theory
 that time spent now will be more than made up in the long run. In this case, I
-might use Firebug_ to ferret out the form post
+might use [Firebug](http://getfirebug.com/) to ferret out the form post
 parameters and target URL, then fire up an editor to write a little script
-using Python's urllib_ to simulate a submission.
-That's a lot of futzing about. With mitmproxy we can do the job
+using Python's [urllib](http://docs.python.org/library/urllib.html) to simulate
+a submission. That's a lot of futzing about. With mitmproxy we can do the job
 in literally 30 seconds, without having to worry about any of the details.
 Here's how.
 
-1. Run mitmdump to record our HTTP conversation to a file.
-----------------------------------------------------------
+## 1. Run mitmdump to record our HTTP conversation to a file.
 
->>> mitmdump -w wireless-login
+<pre class="terminal">
+> mitmdump -w wireless-login
+</pre>
 
-2. Point your browser at the mitmdump instance.
------------------------------------------------
+## 2. Point your browser at the mitmdump instance. 
 
-I use a tiny Firefox addon called `Toggle Proxy`_ to switch quickly to and from mitmproxy.
-I'm assuming you've already :ref:`configured
+I use a tiny Firefox addon called [Toggle
+Proxy](https://addons.mozilla.org/en-us/firefox/addon/toggle-proxy-51740/) to
+switch quickly to and from mitmproxy. I'm assuming you've already [configured
 your browser with mitmproxy's SSL certificate
-authority <certinstall>`.
+authority](http://mitmproxy.org/doc/ssl.html).
+
+## 3. Log in as usual. 
 
-3. Log in as usual.
--------------------
 
 And that's it! You now have a serialized version of the login process in the
 file wireless-login, and you can replay it at any time like this:
 
->>> mitmdump -c wireless-login
+<pre class="terminal">
+> mitmdump -c wireless-login
+</pre>
 
-Embellishments
---------------
+## Embellishments
 
 We're really done at this point, but there are a couple of embellishments we
-could make if we wanted. I use wicd_ to
+could make if we wanted. I use [wicd](http://wicd.sourceforge.net/) to
 automatically join wireless networks I frequent, and it lets me specify a
 command to run after connecting. I used the client replay command above and
 voila! - totally hands-free wireless network startup.
@@ -54,13 +52,10 @@ forth. These add only a few moments to the time it takes to replay, but they're
 not really needed and I somehow feel compelled to trim them anyway. So, we fire up
 the mitmproxy console tool on our serialized conversation, like so:
 
->>> mitmproxy -r wireless-login
+<pre class="terminal">
+> mitmproxy -r wireless-login
+</pre>
 
-We can now go through and manually delete (using the :kbd:`d` keyboard shortcut)
-everything we want to trim. When we're done, we use :kbd:`w` to save the
+We can now go through and manually delete (using the __d__ keyboard shortcut)
+everything we want to trim. When we're done, we use __w__ to save the
 conversation back to the file.
-
-.. _Firebug: https://getfirebug.com/
-.. _urllib: https://docs.python.org/library/urllib.html
-.. _Toggle Proxy: https://addons.mozilla.org/en-us/firefox/addon/toggle-proxy-51740/
-.. _wicd: https://launchpad.net/wicd

doc-src/tutorials/gamecenter.html

@@ -0,0 +1,105 @@
+
+## The setup
+
+In this tutorial, I'm going to show you how simple it is to creatively
+interfere with Apple Game Center traffic using mitmproxy. To set things up, I
+registered my mitmproxy CA certificate with my iPhone - there's a [step by step
+set of instructions](@!urlTo("certinstall/ios.html")!@) elsewhere in this manual. I then
+started mitmproxy on my desktop, and configured the iPhone to use it as a
+proxy. 
+
+
+## Taking a look at the Game Center traffic
+
+Lets take a first look at the Game Center traffic. The game I'll use in this
+tutorial is [Super Mega
+Worm](http://itunes.apple.com/us/app/super-mega-worm/id388541990?mt=8) - a
+great little retro-apocalyptic sidescroller for the iPhone: 
+
+<center>
+    <img src="@!urlTo("tutorials/supermega.png")!@"/>
+</center>
+
+After finishing a game (take your time), watch the traffic flowing through
+mitmproxy:
+
+<center>
+    <img src="@!urlTo("tutorials/one.png")!@"/>
+</center>
+
+We see a bunch of things we might expect - initialisation, the retrieval of
+leaderboards and so forth. Then, right at the end, there's a POST to this
+tantalising URL:
+
+<pre>
+https://service.gc.apple.com/WebObjects/GKGameStatsService.woa/wa/submitScore
+</pre>
+
+The contents of the submission are particularly interesting:
+
+<!--(block|syntax("xml"))-->
+<plist version="1.0">
+<dict>
+    <key>category</key>
+    <string>SMW_Adv_USA1</string>
+    <key>score-value</key>
+    <integer>55</integer>
+    <key>timestamp</key>
+    <integer>1301553284461</integer>
+</dict>
+</plist>
+<!--(end)-->
+
+This is a [property list](http://en.wikipedia.org/wiki/Property_list),
+containing an identifier for the game, a score (55, in this case), and a
+timestamp. Looks pretty simple to mess with.
+
+
+## Modifying and replaying the score submission
+
+Lets edit the score submission. First, select it in mitmproxy, then press
+__enter__ to view it. Make sure you're viewing the request, not the response -
+you can use __tab__ to flick between the two. Now press __e__ for edit. You'll
+be prompted for the part of the request you want to change - press __b__ for
+body.  Your preferred editor (taken from the EDITOR environment variable) will
+now fire up. Lets bump the score up to something a bit more ambitious:
+
+<!--(block|syntax("xml"))-->
+<plist version="1.0">
+<dict>
+    <key>category</key>
+    <string>SMW_Adv_USA1</string>
+    <key>score-value</key>
+    <integer>2200272667</integer>
+    <key>timestamp</key>
+    <integer>1301553284461</integer>
+</dict>
+</plist>
+<!--(end)-->
+
+Save the file and exit your editor. 
+
+The final step is to replay this modified request. Simply press __r__ for
+replay.
+
+## The glorious result and some intrigue
+
+<center>
+    <img src="@!urlTo("tutorials/leaderboard.png")!@"/>
+</center>
+
+And that's it - according to the records, I am the greatest Super Mega Worm
+player of all time. 
+
+Curiously, the top competitors' scores are all the same: 2,147,483,647. If you
+think that number seems familiar, you're right: it's 2^31-1, the maximum value
+you can fit into a signed 32-bit int. Now let me tell you another peculiar
+thing about Super Mega Worm - at the end of every game, it submits your highest
+previous score to the Game Center, not your current score.  This means that it
+stores your highscore somewhere, and I'm guessing that it reads that stored
+score back into a signed integer. So, if you _were_ to cheat by the relatively
+pedestrian means of modifying the saved score on your jailbroken phone, then
+2^31-1 might well be the maximum score you could get. Then again, if the game
+itself stores its score in a signed 32-bit int, you could get the same score
+through perfect play, effectively beating the game. So, which is it in this
+case? I'll leave that for you to decide.

doc-src/tutorials/index.py

@@ -0,0 +1,6 @@
+from countershape import Page
+
+pages = [
+    Page("30second.html", "Client playback: a 30 second example"),
+    Page("gamecenter.html", "Setting highscores on Apple's GameCenter"),
+]

doc-src/upstreamcerts.html

@@ -0,0 +1,15 @@
+- command-line: _--upstream-cert_ 
+- mitmproxy shortcut: _o_, then _u_
+
+Normally, mitmproxy uses the target domain specified in a client's proxy
+request to generate an interception certificate. When __upstream-cert__ mode is
+activated a different procedure is followed: a connection is made to the
+specified remote server to retrieve its __Common Name__ and __Subject
+Alternative Names__. This feature is especially useful when the client
+specifies an IP address rather than a host name in the proxy request. If this
+is the case, we can only generate a certificate if we can establish the __CN__
+and __SANs__ from the upstream server.
+
+Note that __upstream-cert__ mode does not work when the remote server relies on
+[Server Name Indication](http://en.wikipedia.org/wiki/Server_Name_Indication).
+Luckily, SNI is still not very widely used.

docs/.gitignore

@@ -1 +0,0 @@
-_build/

docs/Makefile

@@ -1,195 +0,0 @@
-# Makefile for Sphinx documentation
-#
-
-# You can set these variables from the command line.
-SPHINXOPTS    =
-SPHINXBUILD   = sphinx-build
-PAPER         =
-BUILDDIR      = _build
-
-# User-friendly check for sphinx-build
-ifeq ($(shell which $(SPHINXBUILD) >/dev/null 2>&1; echo $$?), 1)
-$(error The '$(SPHINXBUILD)' command was not found. Make sure you have Sphinx installed, then set the SPHINXBUILD environment variable to point to the full path of the '$(SPHINXBUILD)' executable. Alternatively you can add the directory with the executable to your PATH. If you don't have Sphinx installed, grab it from http://sphinx-doc.org/)
-endif
-
-# Internal variables.
-PAPEROPT_a4     = -D latex_paper_size=a4
-PAPEROPT_letter = -D latex_paper_size=letter
-ALLSPHINXOPTS   = -d $(BUILDDIR)/doctrees $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) .
-# the i18n builder cannot share the environment and doctrees with the others
-I18NSPHINXOPTS  = $(PAPEROPT_$(PAPER)) $(SPHINXOPTS) .
-
-.PHONY: help clean html dirhtml singlehtml pickle json htmlhelp qthelp devhelp epub latex latexpdf text man changes linkcheck doctest coverage gettext
-
-help:
-	@echo "Please use \`make <target>' where <target> is one of"
-	@echo "  html       to make standalone HTML files"
-	@echo "  dirhtml    to make HTML files named index.html in directories"
-	@echo "  singlehtml to make a single large HTML file"
-	@echo "  pickle     to make pickle files"
-	@echo "  json       to make JSON files"
-	@echo "  htmlhelp   to make HTML files and a HTML help project"
-	@echo "  qthelp     to make HTML files and a qthelp project"
-	@echo "  applehelp  to make an Apple Help Book"
-	@echo "  devhelp    to make HTML files and a Devhelp project"
-	@echo "  epub       to make an epub"
-	@echo "  latex      to make LaTeX files, you can set PAPER=a4 or PAPER=letter"
-	@echo "  latexpdf   to make LaTeX files and run them through pdflatex"
-	@echo "  latexpdfja to make LaTeX files and run them through platex/dvipdfmx"
-	@echo "  text       to make text files"
-	@echo "  man        to make manual pages"
-	@echo "  texinfo    to make Texinfo files"
-	@echo "  info       to make Texinfo files and run them through makeinfo"
-	@echo "  gettext    to make PO message catalogs"
-	@echo "  changes    to make an overview of all changed/added/deprecated items"
-	@echo "  xml        to make Docutils-native XML files"
-	@echo "  pseudoxml  to make pseudoxml-XML files for display purposes"
-	@echo "  linkcheck  to check all external links for integrity"
-	@echo "  doctest    to run all doctests embedded in the documentation (if enabled)"
-	@echo "  coverage   to run coverage check of the documentation (if enabled)"
-
-clean:
-	rm -rf $(BUILDDIR)/*
-
-html:
-	$(SPHINXBUILD) -b html $(ALLSPHINXOPTS) $(BUILDDIR)/html
-	@echo
-	@echo "Build finished. The HTML pages are in $(BUILDDIR)/html."
-
-dirhtml:
-	$(SPHINXBUILD) -b dirhtml $(ALLSPHINXOPTS) $(BUILDDIR)/dirhtml
-	@echo
-	@echo "Build finished. The HTML pages are in $(BUILDDIR)/dirhtml."
-
-singlehtml:
-	$(SPHINXBUILD) -b singlehtml $(ALLSPHINXOPTS) $(BUILDDIR)/singlehtml
-	@echo
-	@echo "Build finished. The HTML page is in $(BUILDDIR)/singlehtml."
-
-pickle:
-	$(SPHINXBUILD) -b pickle $(ALLSPHINXOPTS) $(BUILDDIR)/pickle
-	@echo
-	@echo "Build finished; now you can process the pickle files."
-
-json:
-	$(SPHINXBUILD) -b json $(ALLSPHINXOPTS) $(BUILDDIR)/json
-	@echo
-	@echo "Build finished; now you can process the JSON files."
-
-htmlhelp:
-	$(SPHINXBUILD) -b htmlhelp $(ALLSPHINXOPTS) $(BUILDDIR)/htmlhelp
-	@echo
-	@echo "Build finished; now you can run HTML Help Workshop with the" \
-	      ".hhp project file in $(BUILDDIR)/htmlhelp."
-
-qthelp:
-	$(SPHINXBUILD) -b qthelp $(ALLSPHINXOPTS) $(BUILDDIR)/qthelp
-	@echo
-	@echo "Build finished; now you can run "qcollectiongenerator" with the" \
-	      ".qhcp project file in $(BUILDDIR)/qthelp, like this:"
-	@echo "# qcollectiongenerator $(BUILDDIR)/qthelp/mitmproxy.qhcp"
-	@echo "To view the help file:"
-	@echo "# assistant -collectionFile $(BUILDDIR)/qthelp/mitmproxy.qhc"
-
-applehelp:
-	$(SPHINXBUILD) -b applehelp $(ALLSPHINXOPTS) $(BUILDDIR)/applehelp
-	@echo
-	@echo "Build finished. The help book is in $(BUILDDIR)/applehelp."
-	@echo "N.B. You won't be able to view it unless you put it in" \
-	      "~/Library/Documentation/Help or install it in your application" \
-	      "bundle."
-
-devhelp:
-	$(SPHINXBUILD) -b devhelp $(ALLSPHINXOPTS) $(BUILDDIR)/devhelp
-	@echo
-	@echo "Build finished."
-	@echo "To view the help file:"
-	@echo "# mkdir -p $$HOME/.local/share/devhelp/mitmproxy"
-	@echo "# ln -s $(BUILDDIR)/devhelp $$HOME/.local/share/devhelp/mitmproxy"
-	@echo "# devhelp"
-
-epub:
-	$(SPHINXBUILD) -b epub $(ALLSPHINXOPTS) $(BUILDDIR)/epub
-	@echo
-	@echo "Build finished. The epub file is in $(BUILDDIR)/epub."
-
-latex:
-	$(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
-	@echo
-	@echo "Build finished; the LaTeX files are in $(BUILDDIR)/latex."
-	@echo "Run \`make' in that directory to run these through (pdf)latex" \
-	      "(use \`make latexpdf' here to do that automatically)."
-
-latexpdf:
-	$(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
-	@echo "Running LaTeX files through pdflatex..."
-	$(MAKE) -C $(BUILDDIR)/latex all-pdf
-	@echo "pdflatex finished; the PDF files are in $(BUILDDIR)/latex."
-
-latexpdfja:
-	$(SPHINXBUILD) -b latex $(ALLSPHINXOPTS) $(BUILDDIR)/latex
-	@echo "Running LaTeX files through platex and dvipdfmx..."
-	$(MAKE) -C $(BUILDDIR)/latex all-pdf-ja
-	@echo "pdflatex finished; the PDF files are in $(BUILDDIR)/latex."
-
-text:
-	$(SPHINXBUILD) -b text $(ALLSPHINXOPTS) $(BUILDDIR)/text
-	@echo
-	@echo "Build finished. The text files are in $(BUILDDIR)/text."
-
-man:
-	$(SPHINXBUILD) -b man $(ALLSPHINXOPTS) $(BUILDDIR)/man
-	@echo
-	@echo "Build finished. The manual pages are in $(BUILDDIR)/man."
-
-texinfo:
-	$(SPHINXBUILD) -b texinfo $(ALLSPHINXOPTS) $(BUILDDIR)/texinfo
-	@echo
-	@echo "Build finished. The Texinfo files are in $(BUILDDIR)/texinfo."
-	@echo "Run \`make' in that directory to run these through makeinfo" \
-	      "(use \`make info' here to do that automatically)."
-
-info:
-	$(SPHINXBUILD) -b texinfo $(ALLSPHINXOPTS) $(BUILDDIR)/texinfo
-	@echo "Running Texinfo files through makeinfo..."
-	make -C $(BUILDDIR)/texinfo info
-	@echo "makeinfo finished; the Info files are in $(BUILDDIR)/texinfo."
-
-gettext:
-	$(SPHINXBUILD) -b gettext $(I18NSPHINXOPTS) $(BUILDDIR)/locale
-	@echo
-	@echo "Build finished. The message catalogs are in $(BUILDDIR)/locale."
-
-changes:
-	$(SPHINXBUILD) -b changes $(ALLSPHINXOPTS) $(BUILDDIR)/changes
-	@echo
-	@echo "The overview file is in $(BUILDDIR)/changes."
-
-linkcheck:
-	$(SPHINXBUILD) -b linkcheck $(ALLSPHINXOPTS) $(BUILDDIR)/linkcheck
-	@echo
-	@echo "Link check complete; look for any errors in the above output " \
-	      "or in $(BUILDDIR)/linkcheck/output.txt."
-
-doctest:
-	$(SPHINXBUILD) -b doctest $(ALLSPHINXOPTS) $(BUILDDIR)/doctest
-	@echo "Testing of doctests in the sources finished, look at the " \
-	      "results in $(BUILDDIR)/doctest/output.txt."
-
-coverage:
-	$(SPHINXBUILD) -b coverage $(ALLSPHINXOPTS) $(BUILDDIR)/coverage
-	@echo "Testing of coverage in the sources finished, look at the " \
-	      "results in $(BUILDDIR)/coverage/python.txt."
-
-xml:
-	$(SPHINXBUILD) -b xml $(ALLSPHINXOPTS) $(BUILDDIR)/xml
-	@echo
-	@echo "Build finished. The XML files are in $(BUILDDIR)/xml."
-
-pseudoxml:
-	$(SPHINXBUILD) -b pseudoxml $(ALLSPHINXOPTS) $(BUILDDIR)/pseudoxml
-	@echo
-	@echo "Build finished. The pseudo-XML files are in $(BUILDDIR)/pseudoxml."
-
-livehtml:
-	sphinx-autobuild -b html -z '../mitmproxy' -r '___jb_(old|bak|tmp)___$$' $(ALLSPHINXOPTS) $(BUILDDIR)/html

docs/_static/theme_overrides.css

@@ -1,44 +0,0 @@
-
-/* override table width restrictions */
-.wy-table-responsive table td, .wy-table-responsive table th {
-    white-space: normal;
-}
-
-.wy-table-responsive > table > tbody > tr > td {
-    vertical-align: top !important;
-}
-
-.wy-table-responsive {
-    margin-bottom: 24px;
-    max-width: 100%;
-    overflow: visible;
-}
-
-.wy-menu-vertical header, .wy-menu-vertical p.caption {
-    color: #e0e0e0;
-}
-
-.code-block-caption {
-    height: 1.5em;
-}
-
-.code-block-caption .caption-text {
-    font-size: 0.8em;
-    float: right;
-}
-
-.code-block-caption .headerlink {
-    display: none !important;
-}
-
-.function .headerlink {
-    display: none !important;
-}
-
-dl .reference.internal {
-    display: none !important;
-}
-
-dl .headerlink {
-    display: none !important;
-}

docs/_templates/page.html

@@ -1,10 +0,0 @@
-{% extends "!page.html" %}
-{% block sidebartitle %}
-    <a href="https://mitmproxy.org/" style="margin-bottom: 7px; background: none !important;">
-        <button class="btn btn-info">
-            <i class="fa fa-arrow-left"></i>
-            Return to mitmproxy.org
-        </button>
-    </a>
-    {{ super() }}
-{% endblock %}

docs/certinstall.rst

@@ -1,208 +0,0 @@
-.. _certinstall:
-
-About Certificates
-==================
-
-Introduction
-------------
-
-Mitmproxy can decrypt encrypted traffic on the fly, as long as the client
-trusts its built-in certificate authority. Usually this means that the
-mitmproxy CA certificates have to be installed on the client device.
-
-Quick Setup
------------
-
-By far the easiest way to install the mitmproxy certificates is to use the
-built-in certificate installation app. To do this, just start mitmproxy and
-configure your target device with the correct proxy settings. Now start a
-browser on the device, and visit the magic domain **mitm.it**. You should see
-something like this:
-
-.. image:: certinstall-webapp.png
-
-Click on the relevant icon, follow the setup instructions for the platform
-you're on and you are good to go.
-
-
-Installing the mitmproxy CA certificate manually
-------------------------------------------------
-
-Sometimes using the quick install app is not an option - Java or the iOS
-Simulator spring to mind - or you just need to do it manually for some other
-reason. Below is a list of pointers to manual certificate installation
-documentation for some common platforms.
-
-The mitmproxy CA cert is located in ``~/.mitmproxy`` after it has been generated at the first
-start of mitmproxy.
-
-
-iOS
-^^^
-
-See http://jasdev.me/intercepting-ios-traffic
-
-and http://web.archive.org/web/20150920082614/http://kb.mit.edu/confluence/pages/viewpage.action?pageId=152600377
-
-iOS Simulator
-^^^^^^^^^^^^^
-
-See https://github.com/ADVTOOLS/ADVTrustStore#how-to-use-advtruststore
-
-Java
-^^^^
-
-See http://docs.oracle.com/cd/E19906-01/820-4916/geygn/index.html
-
-Android/Android Simulator
-^^^^^^^^^^^^^^^^^^^^^^^^^
-
-See http://wiki.cacert.org/FAQ/ImportRootCert#Android_Phones_.26_Tablets
-
-Windows
-^^^^^^^
-
-See http://windows.microsoft.com/en-ca/windows/import-export-certificates-private-keys#1TC=windows-7
-
-Windows (automated)
-^^^^^^^^^^^^^^^^^^^
-
->>> certutil.exe -importpfx Root mitmproxy-ca-cert.p12
-
-See also: https://technet.microsoft.com/en-us/library/cc732443.aspx
-
-Mac OS X
-^^^^^^^^
-
-See https://support.apple.com/kb/PH7297?locale=en_US
-
-Ubuntu/Debian
-^^^^^^^^^^^^^
-
-See http://askubuntu.com/questions/73287/how-do-i-install-a-root-certificate/94861#94861
-
-Mozilla Firefox
-^^^^^^^^^^^^^^^
-
-See https://wiki.mozilla.org/MozillaRootCertificate#Mozilla_Firefox
-
-Chrome on Linux
-^^^^^^^^^^^^^^^
-
-See https://code.google.com/p/chromium/wiki/LinuxCertManagement
-
-
-The mitmproxy certificate authority
------------------------------------
-
-The first time **mitmproxy** or **mitmdump** is run, the mitmproxy Certificate
-Authority (CA) is created in the config directory (``~/.mitmproxy`` by default).
-This CA is used for on-the-fly generation of dummy certificates for each of the
-SSL sites that your client visits. Since your browser won't trust the
-mitmproxy CA out of the box, you will see an SSL certificate warning every
-time you visit a new SSL domain through mitmproxy. When you are testing a
-single site through a browser, just accepting the bogus SSL cert manually is
-not too much trouble, but there are a many circumstances where you will want to
-configure your testing system or browser to trust the mitmproxy CA as a
-signing root authority. For security reasons, the mitmproxy CA is generated uniquely on the first start and is not shared between mitmproxy installations on different devices.
-
-Certificate Pinning
-^^^^^^^^^^^^^^^^^^^
-
-Some applications employ `Certificate Pinning`_ to prevent man-in-the-middle attacks.
-This means that **mitmproxy** and **mitmdump's** certificates will not be
-accepted by these applications without modifying them. It is recommended to use the
-:ref:`passthrough` feature in order to prevent **mitmproxy** and **mitmdump** from intercepting
-traffic to these specific domains. If you want to intercept the pinned connections, you need to patch the application manually. For Android and (jailbroken) iOS devices, various tools exist to accomplish this.
-
-
-CA and cert files
------------------
-
-The files created by mitmproxy in the .mitmproxy directory are as follows:
-
-===================== ==========================================================================
-mitmproxy-ca.pem      The certificate **and the private key** in PEM format.
-mitmproxy-ca-cert.pem The certificate in PEM format.
-                      Use this to distribute on most non-Windows platforms.
-mitmproxy-ca-cert.p12 The certificate in PKCS12 format. For use on Windows.
-mitmproxy-ca-cert.cer Same file as .pem, but with an extension expected by some Android devices.
-===================== ==========================================================================
-
-Using a custom certificate
---------------------------
-
-You can use your own certificate by passing the ``--cert [domain=]path_to_certificate`` option to
-mitmproxy. Mitmproxy then uses the provided certificate for interception of the
-specified domain instead of generating a certificate signed by its own CA.
-
-The certificate file is expected to be in the PEM format.  You can include
-intermediary certificates right below your leaf certificate, so that your PEM
-file roughly looks like this:
-
-.. code-block:: none
-
-    -----BEGIN PRIVATE KEY-----
-    <private key>
-    -----END PRIVATE KEY-----
-    -----BEGIN CERTIFICATE-----
-    <cert>
-    -----END CERTIFICATE-----
-    -----BEGIN CERTIFICATE-----
-    <intermediary cert (optional)>
-    -----END CERTIFICATE-----
-
-
-For example, you can generate a certificate in this format using these instructions:
-
-
->>> openssl genrsa -out cert.key 2048
->>> openssl req -new -x509 -key cert.key -out cert.crt
-    (Specify the mitm domain as Common Name, e.g. *.google.com)
->>> cat cert.key cert.crt > cert.pem
-
-Now, you can run mitmproxy with the generated certificate:
-
-**For all domain names**
-
-``>>>mitmproxy --cert *=cert.pem``
-
-**For specific domain names**
-
-``>>>mitmproxy --cert *.example.com=cert.pem``
-
-**Note:** ``*.example.com`` is for all the subdomains. You can also use ``www.example.com`` for a particular subdomain.
-
-
-Using a custom certificate authority
-------------------------------------
-
-By default, mitmproxy will use ``~/.mitmproxy/mitmproxy-ca.pem`` as
-the certificate authority to generate certificates for all domains for which no
-custom certificate is provided (see above). You can use your own certificate
-authority by passing the ``--cadir DIRECTORY`` option to mitmproxy. Mitmproxy
-will then look for ``mitmproxy-ca.pem`` in the specified directory. If
-no such file exists, it will be generated automatically.
-
-
-Using a client side certificate
--------------------------------
-
-You can use a client certificate by passing the ``--client-certs DIRECTORY|FILE``
-option to mitmproxy. Using a directory allows certs to be selected based on
-hostname, while using a filename allows a single specific certificate to be used for
-all SSL connections. Certificate files must be in the PEM format and should
-contain both the unencrypted private key and the certificate.
-
-Multiple certs by Hostname
-^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-If you've specified a directory to ``--client-certs``, then the following
-behavior will be taken:
-
-If you visit example.org, mitmproxy looks for a file named ``example.org.pem`` in the specified
-directory and uses this as the client cert.
-
-
-
-.. _Certificate Pinning: http://security.stackexchange.com/questions/29988/what-is-certificate-pinning/

docs/conf.py

@@ -1,243 +0,0 @@
-import importlib
-import inspect
-import os
-import subprocess
-import sys
-
-sys.path.insert(0, os.path.abspath('..'))
-from mitmproxy import version as mversion
-
-
-extensions = [
-    'sphinx.ext.autodoc',
-    'sphinx.ext.doctest',
-    'sphinx.ext.extlinks',
-    'sphinx.ext.linkcode',
-    'sphinx.ext.viewcode',
-    'sphinx.ext.napoleon',
-    'sphinxcontrib.documentedlist'
-]
-
-# https://github.com/sphinx-doc/sphinx/pull/2053
-napoleon_include_special_with_doc = False
-
-autodoc_member_order = "bysource"
-
-# Add any paths that contain templates here, relative to this directory.
-templates_path = ['_templates']
-
-# The suffix(es) of source filenames.
-# You can specify multiple suffix as a list of string:
-# source_suffix = ['.rst', '.md']
-source_suffix = '.rst'
-
-# The encoding of source files.
-#source_encoding = 'utf-8-sig'
-
-# The master toctree document.
-master_doc = 'index'
-
-# General information about the project.
-project = u'mitmproxy docs'
-copyright = u'2016, the mitmproxy project'
-author = u'The mitmproxy project'
-
-# The version info for the project you're documenting, acts as replacement for
-# |version| and |release|, also used in various other places throughout the
-# built documents.
-#
-# The short X.Y version.
-version = mversion.VERSION
-# The full version, including alpha/beta/rc tags.
-release = mversion.VERSION
-
-# The language for content autogenerated by Sphinx. Refer to documentation
-# for a list of supported languages.
-#
-# This is also used if you do content translation via gettext catalogs.
-# Usually you set "language" from the command line for these cases.
-language = None
-
-# There are two options for replacing |today|: either, you set today to some
-# non-false value, then it is used:
-#today = ''
-# Else, today_fmt is used as the format for a strftime call.
-#today_fmt = '%B %d, %Y'
-
-# List of patterns, relative to source directory, that match files and
-# directories to ignore when looking for source files.
-exclude_patterns = ['_build']
-
-# The reST default role (used for this markup: `text`) to use for all
-# documents.
-#default_role = None
-
-# If true, '()' will be appended to :func: etc. cross-reference text.
-#add_function_parentheses = True
-
-# If true, the current module name will be prepended to all description
-# unit titles (such as .. function::).
-#add_module_names = True
-
-# If true, sectionauthor and moduleauthor directives will be shown in the
-# output. They are ignored by default.
-#show_authors = False
-
-# The name of the Pygments (syntax highlighting) style to use.
-pygments_style = 'sphinx'
-
-# A list of ignored prefixes for module index sorting.
-modindex_common_prefix = ['mitmproxy.']
-
-# If true, keep warnings as "system message" paragraphs in the built documents.
-#keep_warnings = False
-
-# If true, `todo` and `todoList` produce output, else they produce nothing.
-todo_include_todos = False
-
-
-# -- Options for HTML output ----------------------------------------------
-
-# The theme to use for HTML and HTML Help pages.  See the documentation for
-# a list of builtin themes.
-html_theme = 'sphinx_rtd_theme'
-
-# Theme options are theme-specific and customize the look and feel of a theme
-# further.  For a list of options available for each theme, see the
-# documentation.
-html_theme_options = {
-    'logo_only': True,
-}
-
-# Add any paths that contain custom themes here, relative to this directory.
-#html_theme_path = []
-
-# The name for this set of Sphinx documents.  If None, it defaults to
-# "<project> v<release> documentation".
-html_title = "mitmproxy %s documentation" % version
-
-# A shorter title for the navigation bar.  Default is the same as html_title.
-#html_short_title = None
-
-# The name of an image file (relative to this directory) to place at the top
-# of the sidebar.
-html_logo = "mitmproxy-docs.png"
-
-# The name of an image file (within the static path) to use as favicon of the
-# docs.  This file should be a Windows icon file (.ico) being 16x16 or 32x32
-# pixels large.
-html_favicon = "favicon.ico"
-
-# Add any paths that contain custom static files (such as style sheets) here,
-# relative to this directory. They are copied after the builtin static files,
-# so a file named "default.css" will overwrite the builtin "default.css".
-html_static_path = ['_static']
-
-# Add any extra paths that contain custom files (such as robots.txt or
-# .htaccess) here, relative to this directory. These files are copied
-# directly to the root of the documentation.
-#html_extra_path = []
-
-# If not '', a 'Last updated on:' timestamp is inserted at every page bottom,
-# using the given strftime format.
-#html_last_updated_fmt = '%b %d, %Y'
-
-# If true, SmartyPants will be used to convert quotes and dashes to
-# typographically correct entities.
-#html_use_smartypants = True
-
-# Custom sidebar templates, maps document names to template names.
-#html_sidebars = {}
-
-# Additional templates that should be rendered to pages, maps page names to
-# template names.
-#html_additional_pages = {}
-
-# If false, no module index is generated.
-#html_domain_indices = True
-
-# If false, no index is generated.
-#html_use_index = True
-
-# If true, the index is split into individual pages for each letter.
-#html_split_index = False
-
-# If true, links to the reST sources are added to the pages.
-html_show_sourcelink = False
-
-# If true, "Created using Sphinx" is shown in the HTML footer. Default is True.
-#html_show_sphinx = True
-
-# If true, "(C) Copyright ..." is shown in the HTML footer. Default is True.
-#html_show_copyright = True
-
-# If true, an OpenSearch description file will be output, and all pages will
-# contain a <link> tag referring to it.  The value of this option must be the
-# base URL from which the finished HTML is served.
-#html_use_opensearch = ''
-
-# This is the file name suffix for HTML files (e.g. ".xhtml").
-#html_file_suffix = None
-
-# Language to be used for generating the HTML full-text search index.
-# Sphinx supports the following languages:
-#   'da', 'de', 'en', 'es', 'fi', 'fr', 'hu', 'it', 'ja'
-#   'nl', 'no', 'pt', 'ro', 'ru', 'sv', 'tr'
-#html_search_language = 'en'
-
-# A dictionary with options for the search language support, empty by default.
-# Now only 'ja' uses this config value
-#html_search_options = {'type': 'default'}
-
-# The name of a javascript file (relative to the configuration directory) that
-# implements a search results scorer. If empty, the default will be used.
-#html_search_scorer = 'scorer.js'
-
-# Output file base name for HTML help builder.
-htmlhelp_basename = 'mitmproxydoc'
-
-last_tag, tag_dist, commit = (
-    subprocess.check_output(["git", "describe", "--tags", "--long"])
-        .decode()
-        .strip()
-        .rsplit("-", 2)
-)
-tag_dist = int(tag_dist)
-if tag_dist == 0:
-    tag = last_tag
-else:
-    tag = "master"
-
-SRCBASE = "https://github.com/mitmproxy/mitmproxy/blob/{}".format(tag)
-
-extlinks = dict(
-    src = (SRCBASE + r"/%s", '')
-)
-
-
-def linkcode_resolve(domain, info):
-    if domain != 'py':
-        return None
-    module, fullname = info['module'], info['fullname']
-    if not module:
-        return None
-    obj = importlib.import_module(module)
-    for item in fullname.split('.'):
-        obj = getattr(obj, item, None)
-    if obj is None:
-        return None
-    try:
-        spath = inspect.getsourcefile(obj)
-        _, line = inspect.getsourcelines(obj)
-    except (TypeError, IOError):
-        return None
-    if spath.rfind("mitmproxy") > -1:
-        off = spath.rfind("mitmproxy")
-        mpath = spath[off:]
-    else:
-        return None
-    return SRCBASE + "/%s#L%s" % (mpath, line)
-
-
-def setup(app):
-    app.add_stylesheet('theme_overrides.css')

docs/config.rst

@@ -1,13 +0,0 @@
-.. _config:
-
-Configuration
-=============
-
-Mitmproxy is configured with a YAML_ file, located at
-``~/.mitmproxy/config.yaml``. We'll have complete documentation for all
-supported options in the next release in the meantime, please consult the
-source_ for a complete list of options and types.
-
-
-.. _YAML: http://www.yaml.org/start.html
-.. _source: https://github.com/mitmproxy/mitmproxy/blob/master/mitmproxy/options.py

docs/custom-routing.txt

@@ -1,24 +0,0 @@
-# Adapted from http://tldp.org/HOWTO/TransparentProxy-6.html (6.2 Second method)
-# Note that the choice of firewall mark (3) and routing table (2) was fairly arbitrary.
-# If you are already using policy routing or firewall marking for some other purpose,
-# make sure you choose unique numbers here. Otherwise, don't worry about it.
-
-
-
-# On the router, run
-
-PROXY_IP=192.168.1.100
-TARGET_IP=192.168.1.110
-
-iptables -t mangle -A PREROUTING -j ACCEPT -p tcp -m multiport --dports 80,443 -s ! $TARGET_IP
-# Alternative to MITM the whole network:
-# iptables -t mangle -A PREROUTING -j ACCEPT -p tcp -m multiport --dports 80,443 -s  $PROXY_IP
-iptables -t mangle -A PREROUTING -j MARK --set-mark 3 -p tcp -m multiport --dports 80,443
-ip rule add fwmark 3 table 2
-ip route add default via $PROXY_IP dev br0 table 2
-
-
-
-# On the proxy machine, run
-
-iptables -A PREROUTING -t nat -i eth0 -p tcp -m multiport --dports 80,443 -j REDIRECT --to-port 8080

docs/dev/addingviews.html

@@ -1,52 +0,0 @@
-As discussed in [the Flow View section of the mitmproxy
-overview](@!urlTo("mitmproxy.html")!@), mitmproxy allows you to inspect and
-manipulate flows.  When inspecting a single flow, mitmproxy uses a number of
-heuristics to show a friendly view of various content types; if mitmproxy
-cannot show a friendly view, mitmproxy defaults to a __raw__ view.
-
-Each content type invokes a different flow viewer to parse the data and display
-the friendly view. Users can add custom content viewers by adding a view class
-to contentview.py, discussed below.
-
-## Adding a new View class to contentview.py
-
-The content viewers used by mitmproxy to present a friendly view of various
-content types are stored in contentview.py.  Reviewing this file shows a number
-of classes named ViewSomeDataType, each with the properties: __name__,
-__prompt__, and __content\_types__ and a function named __\_\_call\_\___.
-
-Adding a new content viewer to parse a data type is as simple as writing a new
-View class.  Your new content viewer View class should have the same properties
-as the other View classes: __name__, __prompt__, and __content\_types__ and a
-__\_\_call\_\___ function to parse the content of the request/response.
-
-* The __name__ property should be a string describing the contents and new content viewer;
-* The __prompt__ property should be a two item tuple:
-
-  - __1__: A string that will be used to display the new content viewer's type; and
-  - __2__: A one character string that will be the hotkey used to select the new content viewer from the Flow View screen;
-
-* The __content\_types__ property should be a list of strings of HTTP Content\-Types that the new content viewer can parse.
-  * Note that mitmproxy will use the content\_types to try and heuristically show a friendly view of content and that you can override the built-in views by populating content\_types with values for content\_types that are already parsed -- e.g. "image/png".
-
-After defining the __name__, __prompt__, and __content\_types__ properties of
-the class, you should write the __\_\_call\_\___ function, which will parse the
-request/response data and provide a friendly view of the data.  The
-__\_\_call\_\___ function should take the following arguments: __self__,
-__hdrs__, __content__, __limit__; __hdrs__ is a MultiDict object containing
-the headers of the request/response; __content__ is the content of the
-request/response, and __limit__ is an integer representing the amount of data
-to display in the view window.
-
-The __\_\_call\_\___ function returns two values: (1) a string describing the
-parsed data; and (2) the parsed data for friendly display.  The parsed data to
-be displayed should be a list of strings formatted for display.  You can use
-the __\_view\_text__ function in contentview.py to format text for display.
-Alternatively, you can display content as a series of key-value pairs; to do
-so, prepare a list of lists, where each list item is a two item list -- a key
-that describes the data, and then the data itself; after preparing the list of
-lists, use the __common.format\_keyvals__ function on it to prepare it as text
-for display.
-
-If the new content viewer fails or throws an exception, mitmproxy will default
-to a __raw__ view.

docs/dev/contributing.rst

@@ -1,11 +0,0 @@
-.. _contributing:
-
-Contributing
-============
-
-As an open source project, **mitmproxy** welcomes contributions of all forms. 
-
-Please head over to the README_ to get started! 😃
-
-
-.. _README: https://github.com/mitmproxy/mitmproxy/blob/master/README.rst

docs/dev/sslkeylogfile.rst

@@ -1,15 +0,0 @@
-.. _sslkeylogfile:
-
-TLS Master Secrets
-==================
-
-The SSL master keys can be logged by mitmproxy so that external programs can decrypt TLS
-connections both from and to the proxy. Key logging is enabled by setting the environment variable
-:envvar:`SSLKEYLOGFILE` so that it points to a writable text file.
-Recent versions of WireShark can use these log files to decrypt packets.
-You can specify the key file path in WireShark via
-
-:samp:`Edit -> Preferences -> Protocols -> SSL -> (Pre)-Master-Secret log filename`.
-
-Note that :envvar:`SSLKEYLOGFILE` is respected by other programs as well, e.g. Firefox and Chrome.
-If this creates any issues, you can set :envvar:`MITMPROXY_SSLKEYLOGFILE` alternatively.

docs/features/anticache.rst

@@ -1,15 +0,0 @@
-.. _anticache:
-
-Anticache
-=========
-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
-:ref:`clientreplay`, when you want to make sure the server responds with complete data.
-
-
-================== ======================
-command-line       ``--anticache``
-mitmproxy shortcut :kbd:`o` then :kbd:`a`
-================== ======================

docs/features/passthrough.rst

@@ -1,102 +0,0 @@
-.. _passthrough:
-
-Ignore Domains
-==============
-
-There are two main reasons why you may want to exempt some traffic from mitmproxy's interception
-mechanism:
-
-- **Certificate pinning:** Some traffic is is protected using `Certificate Pinning`_ and
-  mitmproxy's interception leads to errors. For example, the Twitter app, Windows Update or
-  the Apple App Store fail to work if mitmproxy is active.
-- **Convenience:** You really don't care about some parts of the traffic and just want them to go
-  away. Note that mitmproxy's "Limit" option is often the better alternative here, as it is
-  not affected by the limitations listed below.
-
-If you want to peek into (SSL-protected) non-HTTP connections, check out the :ref:`tcpproxy`
-feature.
-If you want to ignore traffic from mitmproxy's processing because of large response bodies,
-take a look at the :ref:`responsestreaming` feature.
-
-How it works
-------------
-
-================== ======================
-command-line       ``--ignore regex``
-mitmproxy shortcut :kbd:`o` then :kbd:`I`
-================== ======================
-
-
-mitmproxy allows you to specify a regex which is matched against a ``host:port`` string
-(e.g. "example.com:443") to determine hosts that should be excluded.
-
-Limitations
------------
-
-There are two important quirks to consider:
-
-- **In transparent mode, the ignore pattern is matched against the IP and ClientHello SNI host.** While we usually infer the
-  hostname from the Host header if the ``--host`` argument is passed to mitmproxy, we do not
-  have access to this information before the SSL handshake. If the client uses SNI however, then we treat the SNI host as an ignore target.
-- **In regular mode, explicit HTTP requests are never ignored.** [#explicithttp]_ The ignore pattern is
-  applied on CONNECT requests, which initiate HTTPS or clear-text WebSocket connections.
-
-Tutorial
---------
-
-If you just want to ignore one specific domain, there's usually a bulletproof method to do so:
-
-1. Run mitmproxy or mitmdump in verbose mode (``-v``) and observe the ``host:port``
-   information in the serverconnect messages. mitmproxy will filter on these.
-2. Take the ``host:port`` string, surround it with ^ and $, escape all dots (. becomes \\.)
-   and use this as your ignore pattern:
-
-.. code-block:: none
-    :emphasize-lines: 6,7,9
-
-    >>> mitmdump -v
-    127.0.0.1:50588: clientconnect
-    127.0.0.1:50588: request
-      -> CONNECT example.com:443 HTTP/1.1
-    127.0.0.1:50588: Set new server address: example.com:443
-    127.0.0.1:50588: serverconnect
-      -> example.com:443
-    ^C
-    >>> mitmproxy --ignore ^example\.com:443$
-
-
-Here are some other examples for ignore patterns:
-
-.. code-block:: none
-
-    # Exempt traffic from the iOS App Store (the regex is lax, but usually just works):
-    --ignore apple.com:443
-    # "Correct" version without false-positives:
-    --ignore '^(.+\.)?apple\.com:443$'
-
-    # Ignore example.com, but not its subdomains:
-    --ignore '^example.com:'
-
-    # Ignore everything but example.com and mitmproxy.org:
-    --ignore '^(?!example\.com)(?!mitmproxy\.org)'
-
-    # Transparent mode:
-    --ignore 17\.178\.96\.59:443
-    # IP address range:
-    --ignore 17\.178\.\d+\.\d+:443
-
-
-.. seealso::
-
-    - :ref:`tcpproxy`
-    - :ref:`responsestreaming`
-    - mitmproxy's "Limit" feature
-
-.. rubric:: Footnotes
-
-.. [#explicithttp] This stems from an limitation of explicit HTTP proxying:
-    A single connection can be re-used for multiple target domains - a
-    ``GET http://example.com/`` request may be followed by a ``GET http://evil.com/`` request on the
-    same connection. If we start to ignore the connection after the first request,
-    we would miss the relevant second one.
-.. _Certificate Pinning: https://security.stackexchange.com/questions/29988/what-is-certificate-pinning

docs/features/proxyauth.rst

@@ -1,17 +0,0 @@
-.. _proxyauth:
-
-Proxy Authentication
-====================
-
-
-Asks the user for authentication before they are permitted to use the proxy.
-Authentication headers are stripped from the flows, so they are not passed to
-upstream servers. For now, only HTTP Basic authentication is supported. The
-proxy auth options are not compatible with the transparent, socks or reverse proxy
-mode.
-
-================== ======================
-command-line       ``--nonanonymous``,
-                   ``--singleuser USER``,
-                   ``--htpasswd PATH``
-================== ======================

docs/features/responsestreaming.rst

@@ -1,68 +0,0 @@
-.. _responsestreaming:
-
-Response Streaming
-==================
-
-By using mitmproxy's streaming feature, response contents can be passed to the client incrementally
-before they have been fully received by the proxy. This is especially useful for large binary files
-such as videos, where buffering the whole file slows down the client's browser.
-
-By default, mitmproxy will read the entire response, perform any indicated
-manipulations on it and then send the (possibly modified) response to
-the client. In some cases this is undesirable and you may wish to "stream"
-the response back to the client. When streaming is enabled, the response is
-not buffered on the proxy but directly sent back to the client instead.
-
-On the command-line
--------------------
-
-Streaming can be enabled on the command line for all response bodies exceeding a certain size.
-The SIZE argument understands k/m/g suffixes, e.g. 3m for 3 megabytes.
-
-================== =================
-command-line       ``--stream SIZE``
-================== =================
-
-.. warning::
-
-    When response streaming is enabled, **streamed response contents will not be
-    recorded or preserved in any way.**
-
-.. note::
-
-    When response streaming is enabled, the response body cannot be modified by the usual means.
-
-Customizing Response Streaming
-------------------------------
-
-You can also use a script to customize exactly which responses are streamed.
-
-Responses that should be tagged for streaming by setting their ``.stream``
-attribute to ``True``:
-
-.. literalinclude:: ../../examples/complex/stream.py
-   :caption: examples/complex/stream.py
-   :language: python
-
-Implementation Details
-----------------------
-
-When response streaming is enabled, portions of the code which would have otherwise performed
-changes on the response body will see an empty response body. Any modifications will be ignored.
-
-Streamed responses are usually sent in chunks of 4096 bytes. If the response is sent with a
-``Transfer-Encoding: chunked`` header, the response will be streamed one chunk at a time.
-
-Modifying streamed data
------------------------
-
-If the ``.stream`` attribute is callable, ``.stream`` will wrap the generator that yields all
-chunks.
-
-.. literalinclude:: ../../examples/complex/stream_modify.py
-   :caption: examples/complex/stream_modify.py
-   :language: python
-
-.. seealso::
-
-    - :ref:`passthrough`

docs/features/reverseproxy.rst

@@ -1,42 +0,0 @@
-.. _reverseproxy:
-
-Reverse Proxy
-=============
-
-In reverse proxy mode, mitmproxy accepts standard HTTP(S) requests and forwards
-them to the specified upstream server. This is in contrast to :ref:`upstreamproxy`, in which
-mitmproxy forwards HTTP(S) proxy requests to an upstream proxy server.
-
-================== ================================
-command-line       ``-R http[s]://hostname[:port]``
-================== ================================
-
-Here, **http[s]** signifies if the proxy should use TLS to connect to the server.
-mitmproxy always accepts both encrypted and unencrypted requests and transforms
-them to what the server expects.
-
-.. code-block:: none
-
-    >>> mitmdump -R https://httpbin.org -p 80
-    >>> curl http://localhost/
-    # requests will be transparently upgraded to TLS by mitmproxy
-
-    >>> mitmdump -R https://httpbin.org -p 443
-    >>> curl https://localhost/
-    # mitmproxy will use TLS on both ends.
-
-
-Host Header
------------
-
-In reverse proxy mode, mitmproxy automatically rewrites the Host header to match the
-upstream server. This allows mitmproxy to easily connect to existing endpoints on the
-open web (e.g. ``mitmproxy -R https://example.com``).
-
-However, keep in mind that absolute URLs within the returned document or HTTP redirects will
-NOT be rewritten by mitmproxy. This means that if you click on a link for "http://example.com"
-in the returned web page, you will be taken directly to that URL, bypassing mitmproxy.
-
-One possible way to address this is to modify the hosts file of your OS so that "example.com"
-resolves to your proxy's IP, and then access the proxy by going directly to example.com.
-Make sure that your proxy can still resolve the original IP, or specify an IP in mitmproxy.

docs/features/serverreplay.rst

@@ -1,52 +0,0 @@
-.. _serverreplay:
-
-Server-side replay
-==================
-
-Server-side replay lets us replay server responses from a saved HTTP
-conversation.
-
-Matching requests with responses
---------------------------------
-
-By default, :program:`mitmproxy` excludes request headers when matching incoming
-requests with responses from the replay file. This works in most circumstances,
-and makes it possible to replay server responses in situations where request
-headers would naturally vary, e.g. using a different user agent.
-The ``--rheader headername`` command-line option allows you to override
-this behaviour by specifying individual headers that should be included in matching.
-
-
-Response refreshing
--------------------
-
-Simply replaying server responses without modification will often result in
-unexpected behaviour. For example cookie timeouts that were in the future at
-the time a conversation was recorded might be in the past at the time it is
-replayed. By default, :program:`mitmproxy` refreshes server responses before sending
-them to the client. The **date**, **expires** and **last-modified** headers are
-all updated to have the same relative time offset as they had at the time of
-recording. So, if they were in the past at the time of recording, they will be
-in the past at the time of replay, and vice versa. Cookie expiry times are
-updated in a similar way.
-
-You can turn off response refreshing using the ``--norefresh`` argument, or using
-the :kbd:`o` options shortcut within :program:`mitmproxy`.
-
-
-Replaying a session recorded in Reverse-proxy Mode
---------------------------------------------------
-
-If you have captured the session in reverse proxy mode, in order to replay it you 
-still have to specify the server URL, otherwise you may get the error: 
-'HTTP protocol error in client request: Invalid HTTP request form (expected authority or absolute...)'.
-
-During replay, when the client's requests match previously recorded requests, then the
-respective recorded responses are simply replayed  by mitmproxy. 
-Otherwise, the unmatched requests is forwarded to the upstream server.
-If forwarding is not desired, you can use the --kill (-k) switch to prevent that.
-
-================== ===========
-command-line       ``-S path``
-mitmproxy shortcut :kbd:`R` then :kbd:`s`
-================== ===========

docs/features/setheaders.rst

@@ -1,19 +0,0 @@
-.. _setheaders:
-
-Set Headers
-===========
-
-This feature lets you specify a set of headers to be added to requests or
-responses, based on a filter pattern. You can specify these either on the
-command-line, or through an interactive editor in mitmproxy.
-
-Example: Set the **Host** header to "example.com" for all requests.
-
-.. code-block:: none
-
-    mitmdump -R http://example.com --setheader :~q:Host:example.com
-
-================== =======================
-command-line       ``--setheader PATTERN``
-mitmproxy shortcut :kbd:`o` then :kbd:`H`
-================== =======================

docs/features/socksproxy.rst

@@ -1,10 +0,0 @@
-.. _socksproxy:
-
-SOCKS Mode
-==========
-
-In this mode, mitmproxy acts as a SOCKS5 proxy server.
-
-================== ===========
-command-line       ``--socks``
-================== ===========

docs/features/tcpproxy.rst

@@ -1,31 +0,0 @@
-.. _tcpproxy:
-
-TCP Proxy
-=========
-
-In case mitmproxy does not handle a specific protocol, you can exempt
-hostnames from processing, so that mitmproxy acts as a generic TCP forwarder.
-This feature is closely related to the :ref:`passthrough` functionality,
-but differs in two important aspects:
-
-- The raw TCP messages are printed to the event log.
-- SSL connections will be intercepted.
-
-Please note that message interception or modification are not possible yet.
-If you are not interested in the raw TCP messages, you should use the ignore domains feature.
-
-How it works
-------------
-
-================== ======================
-command-line       ``--tcp HOST``
-mitmproxy shortcut :kbd:`o` then :kbd:`T`
-================== ======================
-
-For a detailed description how the hostname pattern works, please look at the :ref:`passthrough`
-feature.
-
-.. seealso::
-
-    - :ref:`passthrough`
-    - :ref:`responsestreaming`

docs/features/upstreamcerts.rst

@@ -1,23 +0,0 @@
-.. _upstreamcerts:
-
-Upstream Certificates
-=====================
-
-When mitmproxy receives a connection destined for an SSL-protected service, it
-freezes the connection before reading its request data, and makes a connection
-to the upstream server to "sniff" the contents of its SSL certificate. The
-information gained - the **Common Name** and **Subject Alternative Names** - is
-then used to generate the interception certificate, which is sent to the client
-so the connection can continue.
-
-This rather intricate little dance lets us seamlessly generate correct
-certificates even if the client has specified only an IP address rather than the
-hostname. It also means that we don't need to sniff additional data to generate
-certs in transparent mode.
-
-Upstream cert sniffing is on by default, and can optionally be turned off.
-
-================== ======================
-command-line       ``--no-upstream-cert``
-mitmproxy shortcut :kbd:`o` then :kbd:`U`
-================== ======================

docs/features/upstreamproxy.rst

@@ -1,12 +0,0 @@
-.. _upstreamproxy:
-
-Upstream proxy mode
-===================
-
-In this mode, mitmproxy accepts proxy requests and unconditionally forwards all
-requests to a specified upstream proxy server. This is in contrast to :ref:`reverseproxy`,
-in which mitmproxy forwards ordinary HTTP requests to an upstream server.
-
-================== =============================
-command-line       ``-U http://hostname[:port]``
-================== =============================

docs/howmitmproxy.rst

@@ -1,240 +0,0 @@
-How mitmproxy works
-===================
-
-Mitmproxy is an enormously flexible tool. Knowing exactly how the proxying
-process works will help you deploy it creatively, and take into account its
-fundamental assumptions and how to work around them. This document explains
-mitmproxy's proxy mechanism in detail, starting with the simplest unencrypted
-explicit proxying, and working up to the most complicated interaction -
-transparent proxying of TLS-protected traffic [#tls]_ in the presence of `Server
-Name Indication`_.
-
-Explicit HTTP
--------------
-
-Configuring the client to use mitmproxy as an explicit proxy is the simplest and
-most reliable way to intercept traffic. The proxy protocol is codified in the
-`HTTP RFC`_, so the behaviour of both the client and the server is well defined,
-and usually reliable. In the simplest possible interaction with mitmproxy, a
-client connects directly to the proxy, and makes a request that looks like this:
-
-.. code-block:: none
-
-    GET http://example.com/index.html HTTP/1.1
-
-This is a proxy GET request - an extended form of the vanilla HTTP GET request
-that includes a schema and host specification, and it includes all the
-information mitmproxy needs to proceed.
-
-.. image:: schematics/how-mitmproxy-works-explicit.png
-    :align: center
-
-1. The client connects to the proxy and makes a request.
-2. Mitmproxy connects to the upstream server and simply forwards the request on.
-
-
-Explicit HTTPS
---------------
-
-The process for an explicitly proxied HTTPS connection is quite different. The
-client connects to the proxy and makes a request that looks like this:
-
-.. code-block:: none
-
-    CONNECT example.com:443 HTTP/1.1
-
-A conventional proxy can neither view nor manipulate an TLS-encrypted data
-stream, so a CONNECT request simply asks the proxy to open a pipe between the
-client and server. The proxy here is just a facilitator - it blindly forwards
-data in both directions without knowing anything about the contents. The
-negotiation of the TLS connection happens over this pipe, and the subsequent
-flow of requests and responses are completely opaque to the proxy.
-
-The MITM in mitmproxy
-^^^^^^^^^^^^^^^^^^^^^
-
-This is where mitmproxy's fundamental trick comes into play. The MITM in its
-name stands for Man-In-The-Middle - a reference to the process we use to
-intercept and interfere with these theoretically opaque data streams. The basic
-idea is to pretend to be the server to the client, and pretend to be the client
-to the server, while we sit in the middle decoding traffic from both sides. The
-tricky part is that the `Certificate Authority`_ system is designed to prevent
-exactly this attack, by allowing a trusted third-party to cryptographically sign
-a server's certificates to verify that they are legit. If this signature doesn't
-match or is from a non-trusted party, a secure client will simply drop the
-connection and refuse to proceed. Despite the many shortcomings of the CA system
-as it exists today, this is usually fatal to attempts to MITM an TLS connection
-for analysis. Our answer to this conundrum is to become a trusted Certificate
-Authority ourselves. Mitmproxy includes a full CA implementation that generates
-interception certificates on the fly. To get the client to trust these
-certificates, we :ref:`register mitmproxy as a trusted CA with the device
-manually <certinstall>`.
-
-Complication 1: What's the remote hostname?
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-To proceed with this plan, we need to know the domain name to use in the
-interception certificate - the client will verify that the certificate is for
-the domain it's connecting to, and abort if this is not the case. At first
-blush, it seems that the CONNECT request above gives us all we need - in this
-example, both of these values are "example.com".  But what if the client had
-initiated the connection as follows:
-
-.. code-block:: none
-
-    CONNECT 10.1.1.1:443 HTTP/1.1
-
-Using the IP address is perfectly legitimate because it gives us enough
-information to initiate the pipe, even though it doesn't reveal the remote
-hostname.
-
-Mitmproxy has a cunning mechanism that smooths this over - :ref:`upstream
-certificate sniffing <upstreamcerts>`. As soon as we see the CONNECT request, we
-pause the client part of the conversation, and initiate a simultaneous
-connection to the server. We complete the TLS handshake with the server, and
-inspect the certificates it used. Now, we use the Common Name in the upstream
-certificates to generate the dummy certificate for the client. Voila, we have
-the correct hostname to present to the client, even if it was never specified.
-
-
-Complication 2: Subject Alternative Name
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-Enter the next complication. Sometimes, the certificate Common Name is not, in
-fact, the hostname that the client is connecting to. This is because of the
-optional `Subject Alternative Name`_ field in the certificate that allows an
-arbitrary number of alternative domains to be specified. If the expected domain
-matches any of these, the client will proceed, even though the domain doesn't
-match the certificate CN. The answer here is simple: when we extract the CN from
-the upstream cert, we also extract the SANs, and add them to the generated dummy
-certificate.
-
-
-Complication 3: Server Name Indication
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
-
-One of the big limitations of vanilla TLS is that each certificate requires its
-own IP address. This means that you couldn't do virtual hosting where multiple
-domains with independent certificates share the same IP address. In a world with
-a rapidly shrinking IPv4 address pool this is a problem, and we have a solution
-in the form of the `Server Name Indication`_ extension to the TLS protocols.
-This lets the client specify the remote server name at the start of the TLS
-handshake, which then lets the server select the right certificate to complete
-the process.
-
-SNI breaks our upstream certificate sniffing process, because when we connect
-without using SNI, we get served a default certificate that may have nothing to
-do with the certificate expected by the client. The solution is another tricky
-complication to the client connection process. After the client connects, we
-allow the TLS handshake to continue until just **after** the SNI value has been
-passed to us. Now we can pause the conversation, and initiate an upstream
-connection using the correct SNI value, which then serves us the correct
-upstream certificate, from which we can extract the expected CN and SANs.
-
-Putting it all together
-^^^^^^^^^^^^^^^^^^^^^^^
-
-Lets put all of this together into the complete explicitly proxied HTTPS flow.
-
-.. image:: schematics/how-mitmproxy-works-explicit-https.png
-    :align: center
-
-1. The client makes a connection to mitmproxy, and issues an HTTP CONNECT request.
-2. Mitmproxy responds with a ``200 Connection Established``, as if it has set up the CONNECT pipe.
-3. The client believes it's talking to the remote server, and initiates the TLS connection.
-   It uses SNI to indicate the hostname it is connecting to.
-4. Mitmproxy connects to the server, and establishes an TLS connection using the SNI hostname
-   indicated by the client.
-5. The server responds with the matching certificate, which contains the CN and SAN values
-   needed to generate the interception certificate.
-6. Mitmproxy generates the interception cert, and continues the
-   client TLS handshake paused in step 3.
-7. The client sends the request over the established TLS connection.
-8. Mitmproxy passes the request on to the server over the TLS connection initiated in step 4.
-
-Transparent HTTP
-----------------
-
-When a transparent proxy is used, the connection is redirected into a proxy at
-the network layer, without any client configuration being required. This makes
-transparent proxying ideal for those situations where you can't change client
-behaviour - proxy-oblivious Android applications being a common example.
-
-To achieve this, we need to introduce two extra components. The first is a
-redirection mechanism that transparently reroutes a TCP connection destined for
-a server on the Internet to a listening proxy server. This usually takes the
-form of a firewall on the same host as the proxy server - `iptables`_ on Linux
-or pf_ on OSX. Once the client has initiated the connection, it makes a vanilla
-HTTP request, which might look something like this:
-
-.. code-block:: none
-
-    GET /index.html HTTP/1.1
-
-Note that this request differs from the explicit proxy variation, in that it
-omits the scheme and hostname. How, then, do we know which upstream host to
-forward the request to? The routing mechanism that has performed the redirection
-keeps track of the original destination for us.  Each routing mechanism has a
-different way of exposing this data, so this introduces the second component
-required for working transparent proxying: a host module that knows how to
-retrieve the original destination address from the router. In mitmproxy, this
-takes the form of a built-in set of modules_ that know how to talk to each
-platform's redirection mechanism. Once we have this information, the process is
-fairly straight-forward.
-
-.. image:: schematics/how-mitmproxy-works-transparent.png
-    :align: center
-
-1. The client makes a connection to the server.
-2. The router redirects the connection to mitmproxy, which is typically
-   listening on a local port of the same host. Mitmproxy then consults the
-   routing mechanism to establish what the original destination was.
-3. Now, we simply read the client's request...
-4. ... and forward it upstream.
-
-Transparent HTTPS
------------------
-
-The first step is to determine whether we should treat an incoming connection as
-HTTPS. The mechanism for doing this is simple - we use the routing mechanism to
-find out what the original destination port is. All incoming connections pass
-through different layers which can determin the actual protocol to use.
-Automatic TLS detection works for SSLv3, TLS 1.0, TLS 1.1, and TLS 1.2 by
-looking for a *ClientHello* message at the beginning of each connection. This
-works independently of the used TCP port.
-
-From here, the process is a merger of the methods we've described for
-transparently proxying HTTP, and explicitly proxying HTTPS. We use the routing
-mechanism to establish the upstream server address, and then proceed as for
-explicit HTTPS connections to establish the CN and SANs, and cope with SNI.
-
-.. image:: schematics/how-mitmproxy-works-transparent-https.png
-    :align: center
-
-1. The client makes a connection to the server.
-2. The router redirects the connection to mitmproxy, which is typically listening on a local port
-   of the same host. Mitmproxy then consults the routing mechanism to establish what the original
-   destination was.
-3. The client believes it's talking to the remote server, and initiates the TLS connection.
-   It uses SNI to indicate the hostname it is connecting to.
-4. Mitmproxy connects to the server, and establishes an TLS connection using the SNI hostname
-   indicated by the client.
-5. The server responds with the matching certificate, which contains the CN and SAN values
-   needed to generate the interception certificate.
-6. Mitmproxy generates the interception cert, and continues the client TLS handshake paused in
-   step 3.
-7. The client sends the request over the established TLS connection.
-8. Mitmproxy passes the request on to the server over the TLS connection initiated in step 4.
-
-.. rubric:: Footnotes
-
-.. [#tls] The use of "TLS" refers to both SSL (outdated and insecure) and TLS
-          (1.0 and up) in the generic sense, unless otherwise specified.
-
-.. _Server Name Indication: https://en.wikipedia.org/wiki/Server_Name_Indication
-.. _HTTP RFC: https://tools.ietf.org/html/rfc7230
-.. _Certificate Authority: https://en.wikipedia.org/wiki/Certificate_authority
-.. _Subject Alternative Name: https://en.wikipedia.org/wiki/SubjectAltName
-.. _iptables: http://www.netfilter.org/
-.. _pf: https://en.wikipedia.org/wiki/PF_\(firewall\)
-.. _modules: https://github.com/mitmproxy/mitmproxy/tree/master/mitmproxy/platform