5acdd78b15
fix typo
2017-02-14 17:45:54 +01:00
c622622c59
Encoding fixes and tests
2017-02-05 18:59:01 +05:30
aaff9dfd32
Reset the host header to the correct destination
2017-01-30 23:41:47 +01:00
c2c6050df3
Store original host in flow metadata
2017-01-29 14:33:53 +01:00
0ca1916f1b
Fix host extraction
2017-01-22 15:28:14 +01:00
e8fc4af4c6
Follow PEP-8 and add comment
2017-01-22 14:59:46 +01:00
93172460aa
Add blank lines for lint
2017-01-21 09:39:34 +01:00
8aa250d679
Change class name
2017-01-20 23:48:26 +01:00
a55eba3b37
Get the the original header in requestheaders instead of request
2017-01-20 23:43:53 +01:00
95cca4ce75
update stream.py
2017-01-16 18:30:05 +08:00
eaaec4353d
update log_events.py
2017-01-16 18:11:18 +08:00
98a079aa69
rename logging.py example. this conflicted with Python's stdlib
2016-12-19 16:21:17 +01:00
c4e9000021
fix #1858
2016-12-19 01:15:10 +01:00
3e37cbd061
minor fixes
2016-12-10 12:06:33 +01:00
293b79af91
remove lxml-dependent code
2016-12-10 10:19:05 +01:00
45332006a3
mitmweb: 100% app test coverage, numerous fixes
2016-11-23 22:35:07 +01:00
40f0193dda
remove mitmweb auth
...
9b08279c7c
2016-11-22 18:27:16 +01:00
c90405253a
remove stickycookie example
...
The recommended way to do this is mitmproxy/addons/stickycookie.py
2016-11-21 02:46:25 +01:00
9af8f4bb31
organize examples
...
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.
2016-11-21 02:28:10 +01:00
d16a3753d7
Remove dead run_scripthooks example reference.
2016-11-17 16:33:51 -08:00
2a2387fb32
explain host=pretty_host assignment
2016-11-09 13:11:31 +01:00
dc44465c92
fix SNI for transparent mode - #1638
...
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.
2016-11-08 15:39:24 +01:00
4eb2b56dec
Let's not over-ride __bool__ on connection objects
...
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.
2016-11-04 10:59:41 +13:00
d56bbb95e2
rename logging .py to prevent import errors
2016-10-29 11:31:38 -07:00
f26a375560
fix #1678
2016-10-27 12:55:39 -07:00
eda1b39a74
minor fixes
2016-10-25 22:06:52 -07:00
39d7ba852c
Include `boudary=...` in mutipart postData
...
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.
2016-10-24 14:34:04 -07:00
a1a792aeac
various encoding fixes, fix #1650
2016-10-22 18:47:12 -07:00
0526d94f4a
Handle `bytes` in request parameters
2016-10-22 18:28:32 -07:00
0d0a3a51df
The first argument should be the filter, then the flow.
2016-10-21 16:47:19 -07:00
8430f857b5
The final piece: netlib -> mitproxy.net
2016-10-20 11:56:38 +13:00
f45f4e677e
netlib.strutils -> mitmproxy.utils.strutils
2016-10-20 10:11:58 +13:00
7440232f60
netlib.version -> mitmproxy.version
2016-10-20 09:20:44 +13:00
e73c7fe77e
mitmproxy.protocol -> mitmproxy.proxy.protocol
...
The protocols here are compltely proxy-specific, are only used from within the
proxy module, and are not exposed to users.
2016-10-19 23:11:56 +13:00
24cf8da27e
Move all tools into mitmproxy.tools, move models/* to top level
...
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.
2016-10-19 20:26:05 +13:00
5a68d21e8c
Remove flow module entirely, move contents to top level
...
mitmproxy.flow.io -> mitmproxy.io
mitmproxy.flow.export -> mitmproxy.export
2016-10-19 15:08:35 +13:00
7c32d4ea2a
flow.state -> addons.state
2016-10-19 14:48:42 +13:00
22eebfd574
addons.Addons -> addonmanager, builtins -> addons
2016-10-19 14:39:39 +13:00
bce387a5a0
Kill flow.master - create master.Master
...
Also extract events into .events
2016-10-19 13:22:50 +13:00
87629586ae
web app cleanups: tests and examples
2016-10-19 11:48:51 +13:00
02d3d61820
fix redirect_requests.py example
2016-10-16 23:49:54 -07:00
c774a9fec9
python3: clean up super and __future__
2016-10-17 18:03:07 +13:00
a647b30365
python3: clean up class brackets
2016-10-17 17:37:08 +13:00
fb22f2ff4f
Zap object base class
2016-10-17 17:37:08 +13:00
ce98a9219e
test & examples: zap six
2016-10-17 16:45:45 +13:00
55cb2a8547
docs: logging and the context
2016-10-16 20:26:06 +13:00
fb69c9c345
docs: overview, classes, arguments
2016-10-16 20:26:06 +13:00
bb60b76af4
use flowfilter.match
2016-10-03 11:45:54 +02:00
ba84248910
rename mitmproxy.filt -> mitmproxy.flowfilter
2016-10-03 11:45:54 +02:00
8021427ab9
Fixes - #1555 sslstrip.py flow.response.headers ( #1556 )
...
* 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
2016-09-25 19:29:26 -07:00
Maximilian Hils