| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | 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 final piece: netlib -> mitproxy.net | Aldo Cortesi | 2016-10-20 | 1 | -1/+1 |
| | | |||||
| * | netlib.strutils -> mitmproxy.utils.strutils | Aldo Cortesi | 2016-10-20 | 1 | -1/+1 |
| | | |||||
| * | netlib.version -> mitmproxy.version | Aldo Cortesi | 2016-10-20 | 1 | -1/+1 |
| | | |||||
| * | Fix issue with binary content in json | Shadab Zafar | 2016-08-15 | 1 | -2/+3 |
| | | |||||
| * | Use postData field in PUT, PATCH requests too | Shadab Zafar | 2016-08-15 | 1 | -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_cookies | Shadab Zafar | 2016-08-15 | 1 | -6/+6 |
| | | |||||
| * | Support .zhar compression | Shadab Zafar | 2016-08-15 | 1 | -2/+5 |
| | | |||||
| * | Add text field to response content | Shadab Zafar | 2016-08-15 | 1 | -2/+11 |
| | | |||||
| * | Add serverIPAddress field | Shadab Zafar | 2016-08-15 | 1 | -0/+3 |
| | | |||||
| * | Add postData field | Shadab Zafar | 2016-08-15 | 1 | -2/+11 |
| | | |||||
| * | Add SSL & Connect timings | Shadab Zafar | 2016-08-15 | 1 | -6/+22 |
| | | |||||
| * | Add a ctx.log on finish | Shadab Zafar | 2016-08-15 | 1 | -2/+4 |
| | | |||||
| * | Open JSON file in text mode | Shadab Zafar | 2016-08-15 | 1 | -1/+1 |
| | | |||||
| * | Simplify name_value | Shadab Zafar | 2016-08-15 | 1 | -11/+1 |
| | | |||||
| * | Fix wrong import | Shadab Zafar | 2016-08-15 | 1 | -1/+1 |
| | | |||||
| * | Improve cookies formatting | Shadab Zafar | 2016-08-15 | 1 | -4/+19 |
| | | |||||
| * | Format Cookies according to the HAR Spec | Shadab Zafar | 2016-08-15 | 1 | -5/+29 |
| | | |||||
| * | Remove pages object | Shadab Zafar | 2016-08-15 | 1 | -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_dump | Shadab Zafar | 2016-08-15 | 1 | -0/+145 |
 |
index : cloud-email/mitmproxy | |
| clone of mitm proxy | James |
| aboutsummaryrefslogtreecommitdiffstats |