| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Fix typo in addons-overview.md
|
| |/ / / / / |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Remove custom events
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
These were always weird, and were added to support exit when processing
completed to mitmdump. We now have better ways to do this.
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Revamp dup_and_replay example
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
- Exposes view.add as a command
- Copes with cases where a view addon isn't present
- Avoids infinite loop caused by replaying replays
Fixes #3096
|
| |\ \ \ \ \ \ \
| |/ / / / / /
|/| / / / / /
| |/ / / / / |
Remove the tick event
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
Mitmproxy: the tickless wonder.
|
| |\| | | | |
| | | | | |
| | | | | | |
Redesign keepserving
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
We no longer use this anywhere, so ditch it.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
- Instead of listening for a pseudo-event, we periodically check whether client
replay, server replay or file reading is active.
- Adjust server replay not to
use tick.
- Adjust readfile to expose a command to check whether reading is in progress.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Also add a periodic refresh every 0.5 seconds for the statusbar. This is in
addition to refreshes upon event update notifications, and picks up replay
status changes not linked to flow events.
|
| | | | | | | |
|
| | | | | | | |
|
| |\| | | | |
| | | | | |
| | | | | | |
Revamp client replay
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Re-design the way client replay works. Before, we would fire up a thread,
replay, wait for the thread to complete, get the next flow, and repeat the
procedure. Now, we have one replay thread that starts when the addon starts,
which pops flows off a thread-safe queue. This is much cleaner, removes the
need for busy tick, and sets the scene for optimisations like server connection
reuse down the track.
|
| |/ / / / / |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Changed syntax of two options (from v2 to v3)
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
--client-certs = v2 syntax --> --set client_certs=value = v3 syntax
--cadir = v2 syntax --> --set cadir=value = v3 syntax
|
| |\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
[requires.io] dependency update on master branch
|
| | | | | | | |
|
| |/ / / / / |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Fix #3002. Auto-expanding for tilda.
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | | |
add SO_KEEPALIVE
|
| | | | | | | | |
|
| |\ \ \ \ \ \ \
| |_|/ / / / /
|/| | | | | | |
asyncio: shift script reloading out of the tick event
|
| | | | | | | | |
|
| | | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
The granularity of mtime is surprisingly bad. Make the tests more robust
against this, and promote has_log back to a public method, now that we have a
few legitimate examples.
|
| | |/ / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The tick event is a nasty compromise, left over from when we didn't have an
event loop. This is the first patch in a series that explores moving our
built-in addons to managing coroutines on the eventloop directly for periodic
tasks.
|
| |\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
Fix pytest invocation errors
|
| |/ / / / / |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
Fix asyncio.call_soon -> asyncio.ensure_future
|
| |/ / / / / |
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
A grab-bag of mitmweb-related fixes
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Temporarily disable config saving until we can look at this more closely.
Config saving should:
- Only happen when explicitly requested by the user
- Only save changed values
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | | |
See https://www.python.org/dev/peps/pep-0475/
|
| |/ / / / /
| | | | |
| | | | |
| | | | | |
Fixes #3067
|
| |\ \ \ \ \
| | | | | |
| | | | | | |
asyncio: fix exit behaviour for console
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
- Add a master.run_loop function. This encapsulates our run behaviour so that
it can be used by implementations that need to manage their own run loop (like urwid).
- Shift crash exit message to the common core. I'm not convinced we really need
this, but if we want it it should be centralised.
- Clean up an extra exception that can be thrown by asyncio itself on "dirty"
termination after a mitmproxy crash.
|
| |\| | | | |
| | | | | |
| | | | | | |
Ignore signal errors on windows + various fixes
|
| |/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
- Ignore the NotImplementedError raised by add_signal_handler on Windows.
- Entrypoints return an integer exit code, or None. Adjust our type annotations
and code to suit.
Fixes #3061
|