aboutsummaryrefslogtreecommitdiffstats
path: root/examples
Commit message (Collapse)AuthorAgeFilesLines
...
* rename logging .py to prevent import errorsThomas Kriechbaumer2016-10-291-0/+0
|
* fix #1678Maximilian Hils2016-10-271-3/+4
|
* minor fixesMaximilian Hils2016-10-251-3/+3
|
* Include `boudary=...` in mutipart postData Slobodan Mišković2016-10-241-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 #1650Maximilian Hils2016-10-221-22/+17
|
* Handle `bytes` in request parametersSlobodan Mišković2016-10-221-2/+10
|
* The first argument should be the filter, then the flow.Brady Law2016-10-211-1/+1
|
* The final piece: netlib -> mitproxy.netAldo Cortesi2016-10-201-1/+1
|
* netlib.strutils -> mitmproxy.utils.strutilsAldo Cortesi2016-10-203-3/+3
|
* netlib.version -> mitmproxy.versionAldo Cortesi2016-10-201-1/+1
|
* mitmproxy.protocol -> mitmproxy.proxy.protocolAldo Cortesi2016-10-191-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 levelAldo Cortesi2016-10-192-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 levelAldo Cortesi2016-10-193-7/+5
| | | | | mitmproxy.flow.io -> mitmproxy.io mitmproxy.flow.export -> mitmproxy.export
* flow.state -> addons.stateAldo Cortesi2016-10-191-1/+1
|
* addons.Addons -> addonmanager, builtins -> addonsAldo Cortesi2016-10-191-1/+1
|
* Kill flow.master - create master.MasterAldo Cortesi2016-10-192-5/+5
| | | | Also extract events into .events
* web app cleanups: tests and examplesAldo Cortesi2016-10-191-5/+5
|
* fix redirect_requests.py exampleMaximilian Hils2016-10-161-2/+1
|
* python3: clean up super and __future__Aldo Cortesi2016-10-171-1/+0
|
* python3: clean up class bracketsAldo Cortesi2016-10-172-2/+2
|
* Zap object base classAldo Cortesi2016-10-172-2/+2
|
* test & examples: zap sixAldo Cortesi2016-10-172-4/+4
|
* docs: logging and the contextAldo Cortesi2016-10-161-0/+6
|
* docs: overview, classes, argumentsAldo Cortesi2016-10-163-21/+24
|
* use flowfilter.matchThomas Kriechbaumer2016-10-031-4/+5
|
* rename mitmproxy.filt -> mitmproxy.flowfilterThomas Kriechbaumer2016-10-031-3/+3
|
* Fixes - #1555 sslstrip.py flow.response.headers (#1556)phackt2016-09-251-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.smill2016-09-141-0/+8
|
* Improved error-handling / supplemented documention.smill2016-09-041-0/+79
|
* Improve the way we handle upstream errorsAldo Cortesi2016-09-011-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 changesAldo Cortesi2016-09-011-11/+13
|
* introduce Response.make for simple response creationMaximilian Hils2016-08-231-6/+1
|
* Fix issue with binary content in jsonShadab Zafar2016-08-151-2/+3
|
* Use postData field in PUT, PATCH requests tooShadab Zafar2016-08-151-1/+1
| | | | | The HAR spec isn't really clear on whether this should be the case, but Google Chrome does this, so I think we should too.
* Refactor format_cookiesShadab Zafar2016-08-151-6/+6
|
* Support .zhar compressionShadab Zafar2016-08-151-2/+5
|
* Add text field to response contentShadab Zafar2016-08-151-2/+11
|
* Add serverIPAddress fieldShadab Zafar2016-08-151-0/+3
|
* Add postData fieldShadab Zafar2016-08-151-2/+11
|
* Add SSL & Connect timingsShadab Zafar2016-08-151-6/+22
|
* Add a ctx.log on finishShadab Zafar2016-08-151-2/+4
|
* Open JSON file in text modeShadab Zafar2016-08-151-1/+1
|
* Simplify name_valueShadab Zafar2016-08-151-11/+1
|
* Fix wrong importShadab Zafar2016-08-151-1/+1
|
* Improve cookies formattingShadab Zafar2016-08-151-4/+19
|
* Format Cookies according to the HAR SpecShadab Zafar2016-08-151-5/+29
|
* Remove pages objectShadab Zafar2016-08-151-1/+0
| | | | | | | The HAR Spec says that the field can be left out by applications that don't group by pages. http://www.softwareishard.com/blog/har-12-spec/#log
* Welcome har_dumpShadab Zafar2016-08-151-0/+145
|
* Goodbye har_extractorShadab Zafar2016-08-151-264/+0
|
* make the linter happyMaximilian Hils2016-07-231-1/+1
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-20 10:10:52 +0000