Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Fix host extraction | Ammonite | 2017-01-22 | 1 | -1/+1 |
| | |||||
* | Follow PEP-8 and add comment | Ammonite | 2017-01-22 | 1 | -5/+8 |
| | |||||
* | Add blank lines for lint | Ammonite | 2017-01-21 | 1 | -0/+2 |
| | |||||
* | Change class name | Ammonite | 2017-01-20 | 1 | -2/+2 |
| | |||||
* | Get the the original header in requestheaders instead of request | Ammonite | 2017-01-20 | 1 | -19/+28 |
| | |||||
* | update stream.py | Feei | 2017-01-16 | 1 | -2/+2 |
| | |||||
* | update log_events.py | Feei | 2017-01-16 | 1 | -2/+2 |
| | |||||
* | rename logging.py example. this conflicted with Python's stdlib | Maximilian Hils | 2016-12-19 | 1 | -0/+0 |
| | |||||
* | fix #1858 | Maximilian Hils | 2016-12-19 | 1 | -1/+1 |
| | |||||
* | minor fixes | Maximilian Hils | 2016-12-10 | 1 | -1/+1 |
| | |||||
* | remove lxml-dependent code | Maximilian Hils | 2016-12-10 | 1 | -1/+1 |
| | |||||
* | mitmweb: 100% app test coverage, numerous fixes | Maximilian Hils | 2016-11-23 | 1 | -1/+2 |
| | |||||
* | remove mitmweb auth | Maximilian Hils | 2016-11-22 | 1 | -1/+1 |
| | | | | | 9b08279c7c3384f716b66329fefbe97a368189a2 removed the actual functionality. we should not have a command line switch that does nothing. :) | ||||
* | remove stickycookie example | Maximilian Hils | 2016-11-21 | 2 | -43/+0 |
| | | | | The recommended way to do this is mitmproxy/addons/stickycookie.py | ||||
* | organize examples | Maximilian Hils | 2016-11-21 | 40 | -236/+159 |
| | | | | | | | This commit is largely based on work by Thiago Arrais (@thiagoarrais) and Shane Bradfield (@l33tLumberjack). I wasn't really able to get their PR reasonably merged onto the latest master, so I reapplied their changes manually here and did some further improvements on that. | ||||
* | Remove dead run_scripthooks example reference. | Mike Fotinakis | 2016-11-17 | 1 | -1/+1 |
| | |||||
* | explain host=pretty_host assignment | Maximilian Hils | 2016-11-09 | 1 | -0/+4 |
| | |||||
* | fix SNI for transparent mode - #1638 | phackt | 2016-11-08 | 1 | -0/+1 |
| | | | | | | In transparent mode host is set with the target server ip. Attribute flow.request.host is used as SNI while mitmproxy is initiating TLS handshake, so it should be set with the pretty_host. | ||||
* | Let's not over-ride __bool__ on connection objects | Aldo Cortesi | 2016-11-04 | 1 | -1/+1 |
| | | | | | If I had a thousand years and every thesaurus in the world, I still couldn't adequately express how much I dislike this piece of interface design. | ||||
* | rename logging .py to prevent import errors | Thomas Kriechbaumer | 2016-10-29 | 1 | -0/+0 |
| | |||||
* | fix #1678 | Maximilian Hils | 2016-10-27 | 1 | -3/+4 |
| | |||||
* | minor fixes | Maximilian Hils | 2016-10-25 | 1 | -3/+3 |
| | |||||
* | Include `boudary=...` in mutipart postData | Slobodan Mišković | 2016-10-24 | 1 | -1/+1 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | While the HAR spec is not very explicit and their example shows just this one example: ```json "postData": { "mimeType": "multipart/form-data" } ``` Would it not make sense to include all the information necessary to parse out the post data `text`. Eg. ```json "postData": { "text": "--xYzZY\r\nContent-Disposition: form-data; name=\"sort1\"\r\n\r\noldest date first\r\n--xYzZY--\r\n", "mimeType": "multipart/form-data; boundary=xYzZY" }, ``` Currently, full mimeType is included only in `content-type` request header. Elsewhere in HAR spec they include the 'extras', eg ```json "content": { "mimeType": "text/html; charset=utf-8" } ``` So one could argue that `mimeType` should include all information necessary to interpret the data. In case of `multipart/form-data`, as per RFC2046 http://www.ietf.org/rfc/rfc2046.txt ``` The Content-Type field for multipart entities requires one parameter, "boundary". ``` I believe that earlier incarnations, eg `har_exporter.py` included it in the mimeType. | ||||
* | various encoding fixes, fix #1650 | Maximilian Hils | 2016-10-22 | 1 | -22/+17 |
| | |||||
* | Handle `bytes` in request parameters | Slobodan Mišković | 2016-10-22 | 1 | -2/+10 |
| | |||||
* | The first argument should be the filter, then the flow. | Brady Law | 2016-10-21 | 1 | -1/+1 |
| | |||||
* | The final piece: netlib -> mitproxy.net | Aldo Cortesi | 2016-10-20 | 1 | -1/+1 |
| | |||||
* | netlib.strutils -> mitmproxy.utils.strutils | Aldo Cortesi | 2016-10-20 | 3 | -3/+3 |
| | |||||
* | netlib.version -> mitmproxy.version | Aldo Cortesi | 2016-10-20 | 1 | -1/+1 |
| | |||||
* | mitmproxy.protocol -> mitmproxy.proxy.protocol | Aldo Cortesi | 2016-10-19 | 1 | -1/+1 |
| | | | | | The protocols here are compltely proxy-specific, are only used from within the proxy module, and are not exposed to users. | ||||
* | Move all tools into mitmproxy.tools, move models/* to top level | Aldo Cortesi | 2016-10-19 | 2 | -3/+3 |
| | | | | | | The primary motivation here (and for all the other moving around) is to present a clean "front of house" to library users, and to migrate primary objects to the top of the module hierarchy. | ||||
* | Remove flow module entirely, move contents to top level | Aldo Cortesi | 2016-10-19 | 3 | -7/+5 |
| | | | | | mitmproxy.flow.io -> mitmproxy.io mitmproxy.flow.export -> mitmproxy.export | ||||
* | flow.state -> addons.state | Aldo Cortesi | 2016-10-19 | 1 | -1/+1 |
| | |||||
* | addons.Addons -> addonmanager, builtins -> addons | Aldo Cortesi | 2016-10-19 | 1 | -1/+1 |
| | |||||
* | Kill flow.master - create master.Master | Aldo Cortesi | 2016-10-19 | 2 | -5/+5 |
| | | | | Also extract events into .events | ||||
* | web app cleanups: tests and examples | Aldo Cortesi | 2016-10-19 | 1 | -5/+5 |
| | |||||
* | fix redirect_requests.py example | Maximilian Hils | 2016-10-16 | 1 | -2/+1 |
| | |||||
* | python3: clean up super and __future__ | Aldo Cortesi | 2016-10-17 | 1 | -1/+0 |
| | |||||
* | python3: clean up class brackets | Aldo Cortesi | 2016-10-17 | 2 | -2/+2 |
| | |||||
* | Zap object base class | Aldo Cortesi | 2016-10-17 | 2 | -2/+2 |
| | |||||
* | test & examples: zap six | Aldo Cortesi | 2016-10-17 | 2 | -4/+4 |
| | |||||
* | docs: logging and the context | Aldo Cortesi | 2016-10-16 | 1 | -0/+6 |
| | |||||
* | docs: overview, classes, arguments | Aldo Cortesi | 2016-10-16 | 3 | -21/+24 |
| | |||||
* | use flowfilter.match | Thomas Kriechbaumer | 2016-10-03 | 1 | -4/+5 |
| | |||||
* | rename mitmproxy.filt -> mitmproxy.flowfilter | Thomas Kriechbaumer | 2016-10-03 | 1 | -3/+3 |
| | |||||
* | Fixes - #1555 sslstrip.py flow.response.headers (#1556) | phackt | 2016-09-25 | 1 | -2/+14 |
| | | | | | | | | | | * Fixes - #1555 sslstrip.py flow.response.headers * #1557 - add enhancements in inline script sslstrip.py with upgrade-insecure-requests stripping * #1557 - update to match python style guide * #1555, #1556, update to a bytes pattern | ||||
* | Added a description to the shim loader, and renamed it. | smill | 2016-09-14 | 1 | -0/+8 |
| | |||||
* | Improved error-handling / supplemented documention. | smill | 2016-09-04 | 1 | -0/+79 |
| | |||||
* | Improve the way we handle upstream errors | Aldo Cortesi | 2016-09-01 | 1 | -2/+2 |
| | | | | | | | - Don't log a traceback for either HTTP or HTTPS DNS resolution or TCP connection errors. These are "ordinary" errors, not mitmproxy issues. - Ensure that the error handler is correctly called for SSL-related protocol errors. | ||||
* | Adjust flowbasic example for Options API changes | Aldo Cortesi | 2016-09-01 | 1 | -11/+13 |
| |